On 05/07/2018 10:12 PM, Blake Henderson wrote: > That behavior usually means that the browser cannot connect to the > server on port 7682. Check to make sure that your browser can talk to > the server on that port by using this special URL: > > https://yourservername.org:7682
I am going to add that the above is necessary with Firefox if you use a self-signed certificate. Firefox seems to track certificates by server name and port number. So, you'll have to go to that URL and make the security exception for its certificate, too. You will also have to do this every time you change certificates on the server as well. I have not had to do the above with Chromium, and I hear it is not necessary with Chrome, either. You can also avoid the whole mess by setting up a proxy server, which may be overkill for a test installation, but is a good idea for production. Jason
