I recently went from the latest stable build to the latest prerelease.  This stopped my letsencrypt docker from working.  So I checked in with the docker support thread for that docker and it was suggested that i turn off ssl for the webui.  So i did and for whatever reason it didnt work.  So I thought since I wouldnt be using the SSL on the webui that I would just change the port.  Well I changed the SSL port to 445 and restarted.  Now I cannot reach the webui either from my laptop or from the gui mode on the server itself.  I also tried safe mode with no luck.

 

I am able to access all my dockers at the moment and all of my shares are visible.  Sadly I didnt think to share the USB drive.

 

So is there any way to fix this through the command line?  If so how would I go about this? If not what should my next step be?

 

I realize this was completely my fault but I am still unsure of why changing the SSL port after setting the ui to use plain http would cause this error.

 

Thank you guys for your help.  It will be most appreciated.

Just an update.  I was able to set the port back to 443 and the use SSL to auto through the ident.cfg file on the flash drive which I had to take out of the server to edit.  I cant tell you how grateful I am that the devs decided to use simple plain text .cfg files for the settings.  This probably would have been a nightmare otherwise.  I still am curious as to why changing the ssl port which wasnt even being used caused such a problem.

 

Anyway I hope this helps if anyone else runs into the same problem. 

It looks like Samba already uses port 445:

  https://www.grc.com/port_445.htm

so that conflict probably prevented the gui's webserver from loading. Try something like 8443 instead.

It looks like Samba already uses port 445:
  https://www.grc.com/port_445.htm
so that conflict probably prevented the gui's webserver from loading. Try something like 8443 instead.

I switched it back to 443 and then I tried to set https to no. Same deal. No webui. Had to pull the USB stick and manually edit the config again.

Sent from my SM-G930V using Tapatalk

If I were to guess, I would say the problem is that your browser is caching old redirect information. 

 

 

If you want SSL on a non-standard port:

• clear your browser's cache
• set SSL to auto and port to 8443

You should be able to go to http://<ip> and it will redirect to https://<servername>:8443.  

 

 

If you don't want SSL at all:

• clear your browser's cache
• set SSL to NO and port to 8443 (port 443 may also work. Your earlier issues may have been due to your browser's cache)

In theory, you should now be able to access http://<ip>

 

 

If you want to continue tweaking the port and/or ssl settings, I'd recommend clearing your cache each time. The reason is that your browser is probably caching the previous redirect information.

If I were to guess, I would say the problem is that your browser is caching old redirect information. 
 
 
If you want SSL on a non-standard port:

• clear your browser's cache
• set SSL to auto and port to 8443

You should be able to go to http:// and it will redirect to https://:8443.  
 
 
If you don't want SSL at all:

• clear your browser's cache
• set SSL to NO and port to 8443 (port 443 may also work. Your earlier issues may have been due to your browser's cache)

In theory, you should now be able to access http://
 
 
If you want to continue tweaking the port and/or ssl settings, I'd recommend clearing your cache each time. The reason is that your browser is probably caching the previous redirect information.

This was 100% spot on. Changing the port and setting it to not use https worked just fine after I cleared my cache. Wish I had thought of that before.

Sent from my SM-G930V using Tapatalk