As a relic from when we started with PRTG we still have our core server set to HTTP instead of HTTPS. I'd like to change that - however I do not want to break compatibility. Is there a way to have any HTTP requests redirected / remapped to HTTPS on the instead?

We use a custom port which should remain the same ...

Article Comments

Hello, switching to https should not be a problem unless you have PRTG API calls which you use to manipulate PRTG. These calls have to be changed of course. Another point would be external links to PRTG maps where you have to use then the https connection.

For all other things PRTG should work without problems.


Apr, 2015 - Permalink

Hey,

yeah that's my point exactly. I want maps etc. to remain intact even with HTTP links because there are numerous public dashboards. At least for a "cutover" period I'd like those to work without manual intervention ( = change the links).

On an apache for example I could use mod_rewrite to force all HTTP calls to be rewritten to HTTPS instead. I know that's not really suggested - but possible nonetheless.

Is anything like that possible with PRTG? Or can PRTG listen on multiple ports maybe, one HTTP one HTTPS?

Regards


Apr, 2015 - Permalink

I'm afraid this is not possible. PRTG listens on port 80 if you have switched to https on port 443 and does a redirect but for map links this won't work. You have to change the links to https and your custom port as well.


May, 2015 - Permalink