Just a quick warning to anyone, before you reboot to this release.  Make sure any containers using port 443 on the host side are prevented from autostarting....

 

It seems the docker containers start before nginx comes up, so if port 443 is in use, it throws a bit of a spanner into the works.

Edited June 4, 20179 yr by CHBMB

5 minutes ago, CHBMB said:

Just a quick warning to anyone, before you reboot to this container.  Make sure any containers using port 443 on the host side are prevented from autostarting....

 

nginx starts default with ports 80 and 443, but these can be reassigned using the 'emhttp' statement in the go file. Some examples:

 

/usr/local/sbin/emhttp &                              # starts nginx on ports 80 (http) and 443 (https)

/usr/local/sbin/emhttp -p 8080 &                 # starts nginx on ports 8080 (http) and 443 (https)

/usr/local/sbin/emhttp -p 8080,8443 &        # starts nginx on ports 8080 (http) and 8443 (https)

 

Edited June 4, 20179 yr by bonienl

Yeah, I know that, but I forgot before I restarted. So docker came up and nginx wasn't happy. SSH in and fixed it though.

Sent from my LG-H815 using Tapatalk

How did you fix this issue??

 

I just updated and cannot get to the GUI....I have letsencrypt autostarting but cannot figure out how to stop it from starting up with the server...

 

Any help would be appreciated!!

 

Edit:  

 

Got it to boot by adding:

 

# Start the Management Utility
/usr/local/sbin/emhttp -p 8686,6443 &

 

to my go file...

Edited June 6, 20179 yr by airbillion

Have a read of this topic - subject may not look right but keep reading