I was prompted with an option to enable HTTPS on my existing installation of PRTG. I said 'yes' and it said give it a few minutes and try loging in again with https: etc. However, now I can't get to the site either with HTTP or HTTPS.
Thoughts?
Article Comments
Hi there,
There was probably some issue binding to the selected socket (443 by default) when setting up the webserver for https. That's usually an issue when there's other software (Apache, IIS) installed on the server.
You may want to refer to this:
It's also important to double-check that the PRTG Core Server Service service is still running. This can be done with the Administration Tool or via services.msc.
To find out what's going on in the background, review your PRTG Core Server Log (x).log which you'll locate in this path by default:
| C:\ProgramData\Paessler\PRTG Network Monitor\Logs (System)\ |
Go directly to the end of the file, then locate the following:
11.09.2017 06:09:39 Startup: Starting webserver for IPs:Ports 0.0.0.0:80,127.0.0.1:8085 (URL: http://127.0.0.1)
11.09.2017 06:09:39 Port Mode: Expert - Port Security: SpecPorts - IP Mode: AllIPs
These entries will tell you how the webserver is configured and on what sockets it binded. If it failed to use a port because it was already in use, it will be noted in the log as well.
If you're unable to get it working, please don't hesitate to contact us via a Support Ticket and we'll be more than glad to assist you further.
Best Regards,
Luciano Lingnau [Paessler Support]
Sep, 2017 - Permalink
Thanks... that lead me to the answer, or at least a work around. I just needed to use the port in the URL along with https://
Thanks for the assistance!
Sep, 2017 - Permalink
Hi there,
There was probably some issue binding to the selected socket (443 by default) when setting up the webserver for https. That's usually an issue when there's other software (Apache, IIS) installed on the server.
You may want to refer to this:
It's also important to double-check that the PRTG Core Server Service service is still running. This can be done with the Administration Tool or via services.msc.
To find out what's going on in the background, review your PRTG Core Server Log (x).log which you'll locate in this path by default:
Go directly to the end of the file, then locate the following:
These entries will tell you how the webserver is configured and on what sockets it binded. If it failed to use a port because it was already in use, it will be noted in the log as well.
If you're unable to get it working, please don't hesitate to contact us via a Support Ticket and we'll be more than glad to assist you further.
Best Regards,
Luciano Lingnau [Paessler Support]
Sep, 2017 - Permalink