Trouble with using Docker CLI to launch OpenEMR on ReadyNas unit

Support
#1

Situation
I cannot access OpenEMR from the browser. Using shell in a box and entering
‘docker run openemr/openemr’ from the command line in the admin setting yields:

Generating a RSA private key

…++++

…++++

writing new private key to ‘/etc/ssl/private/selfsigned.key.pem’

Love OpenEMR? You can now support the project via the open collective:

https://opencollective.com/openemr/donate

Starting cron daemon!

Starting apache!

AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using 172.17.0.3. Set the ‘ServerName’ directive globally to suppress this message

  • I attempted to open http://localhost/openemr in a new tab of google chrome browser with no success. I am fairly lost at this point. Ultimately, the goal is to is for multiple instances of openemr to be accessed.

OpenEMR Version
I’m using OpenEMR version 6.0.0 as a pull from the Official OpenEMR Docker Image Repository
Docker image ID: 51453dcdd9bd
Openemr/openemr image ID: 12692af8ad70

Browser:
I’m using:Google Chrome Version 92.0.4515.159 (Official Build) (64-bit)

Operating System
I’m using: ReadyNASOS 6.10.5 using shell in a box invoking ‘docker run openemr/openemr’

#2

hi @sophisticated_acquis, check out the docker guides

#3

After running ‘docker-compose up’ in the same directory as docker-compose.yml this appeared:

Creating admin_mysql_1 … done
Recreating admin_openemr_1 …
Recreating admin_openemr_1 … error

ERROR: for admin_openemr_1 Cannot start service openemr: driver failed programming external connectivity on endpoint admin_openemr_1 (b61380ec3b010460
94a103e0d16a1ff7f7ff4f45095835a4bb2b757ad9786e4b): Error starting userland proxy: listen tcp 0.0.0.0:443: listen: address already in use

ERROR: for openemr Cannot start service openemr: driver failed programming external connectivity on endpoint admin_openemr_1 (b61380ec3b01046094a103e0
d16a1ff7f7ff4f45095835a4bb2b757ad9786e4b): Error starting userland proxy: listen tcp 0.0.0.0:443: listen: address already in use
ERROR: Encountered errors while bringing up the project.

Any thoughts on how to resolve this?

#4

Something else is using the SSL port. Check if it’s another container with docker ps. More likely it’s the OS itself, perhaps Netgear’s web management interface? Could try restarting to see if it clears out, but you may be left changing which port OpenEMR binds to.

#5

I think apache is likely the cause, which would likely be a headache to attempt to change the default ports. I know that SSL and TLS (1.2 in openemr) are typically connected to port 443. 1. Would I be able to secure connections to openemr without using port 443 (https:)? 2. If I desire to change the openemr port, would I just change it in docker-compose.yml?

#6

I ended up changing Apache’s listening ports, saving, and then restarted. I proceed to enter docker-compose up to build and here is what I have:

Creating admin_mysql_1 … done
Recreating admin_openemr_1 … done
Attaching to admin_mysql_1, admin_openemr_1
mysql_1 | 2021-08-26 22:43:23+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.12+maria~focal started.
mysql_1 | 2021-08-26 22:43:23+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
mysql_1 | 2021-08-26 22:43:23+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.12+maria~focal started.
mysql_1 | 2021-08-26 22:43:23 0 [Note] mysqld (mysqld 10.5.12-MariaDB-1:10.5.12+maria~focal) starting as process 1 …
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: Uses event mutexes
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
openemr_1 | Generating a RSA private key
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: Number of pools: 1
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
mysql_1 | 2021-08-26 22:43:23 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: Using Linux native AIO
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: Completed initialization of buffer pool
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: 128 rollback segments are active.
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: Creating shared tablespace for temporary tables
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: File ‘./ibtmp1’ size is now 12 MB.
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: 10.5.12 started; log sequence number 45154; transaction id 20
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysql_1 | 2021-08-26 22:43:23 0 [Note] Plugin ‘FEEDBACK’ is disabled.
mysql_1 | 2021-08-26 22:43:23 0 [Note] InnoDB: Buffer pool(s) load completed at 210826 22:43:23
mysql_1 | 2021-08-26 22:43:23 0 [Note] Server socket created on IP: ‘::’.
mysql_1 | 2021-08-26 22:43:23 0 [Warning] ‘proxies_priv’ entry ‘@% root@e230244f4d31’ ignored in --skip-name-resolve mode.
mysql_1 | 2021-08-26 22:43:23 0 [Note] Reading of all Master_info entries succeeded
mysql_1 | 2021-08-26 22:43:23 0 [Note] Added new Master_info ‘’ to hash table
mysql_1 | 2021-08-26 22:43:23 0 [Note] mysqld: ready for connections.
mysql_1 | Version: ‘10.5.12-MariaDB-1:10.5.12+maria~focal’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 mariadb.org binary distribution
openemr_1 | …++++
openemr_1 | …++++
openemr_1 | writing new private key to ‘/etc/ssl/private/selfsigned.key.pem’
openemr_1 | -----
openemr_1 | Running quick setup!
mysql_1 | 2021-08-26 22:43:26 4 [Warning] Access denied for user ‘openemr’@‘172.18.0.3’ (using password: YES)
openemr_1 |
openemr_1 | OpenEMR configured.
openemr_1 | Setup Complete!
openemr_1 | Setting user ‘www’ as owner of openemr/ and setting file/dir permissions to 400/500
openemr_1 | Default file permissions and ownership set, allowing writing to specific directories
openemr_1 | Removing remaining setup scripts
openemr_1 | Setup scripts removed, we should be ready to go now!
openemr_1 |
openemr_1 | Love OpenEMR? You can now support the project via the open collective:
openemr_1 | > https://opencollective.com/openemr/donate
openemr_1 |
openemr_1 | Starting cron daemon!
openemr_1 | Starting apache!
openemr_1 | AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using 172.18.0.3. Set the ‘ServerName’ directive gl
obally to suppress this message

*Unfortunately, even with openemr using the default ports 80 & 443, it is not opening up in the browser (chrome) . Between docker and mariadb, there is activity on port 443 and port 3306 respectively. Moreover, both a mariadb and an openemr container are running. not sure why it isn’t spinning up. Any thoughts?

#7

I assume you’re using the ReadyNAS IP address in the browser (i.e. not localhost) and that the ReadyNAS is configured to allow HTTPS access? (It’s been a decade since I’ve messed with a ReadyNAS, but it used to disable HTTPS access to shares by default, which had the effect of disabling it globally. It was configurable.)

#8

No. I actually continued to use localhost/openemr as I really was not thinking. Both http and https are enabled. However, when I changed the listnening ports, I got booted out of the admin GUI and could not re-enter so I had to boot back to the default ports. How do I change the ports for openemr? Do I just change the ports in docker-compose.yml?

#9

Yes, you can change the port binding in docker-compose. See how that is done for the development package: openemr/docker-compose.yml at master · openemr/openemr · GitHub. In that example port 443 in the openEMR container is bound to 9300 on the host (i.e. ReadyNAS OS).

1 Like
#10

I am in there. Thank you for your help, Jason!