Has anyone had this problem, please follow the settings and the problem (CORE configured for SSL):

Same network
Call API by HTTP is received at 80 and is directed to 443 and it works:

Another network
Calling API by HTTP is received at 80 but is not directed to 443 and does not work, and when the call is with https nor appears in the logs.

Can someone give a light?

Article Comments

Why not calling HTTPS directly instead of relying on the redirect?

PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team


Oct, 2018 - Permalink

Hello stephan, because:

"when the call is with https nor appears in the logs"

That not works both.

Only work in my network, the other side is a service OTRS.


Oct, 2018 - Permalink

Ah okay - webinterface not listening on all IPs as per PRTG Administration Tool's Webserver tab?

PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team


Oct, 2018 - Permalink

444/5000 in fact, works on the local network only. Either using http or https.

It does not work at all:

When the kernel is configured for ssl:

- call http - in the log is the call - call https - no log no call

It used to work on 80, but it does not work any more.

My configuration is HTTP by 443 and only 1 ip specified, which is the webserver itself.

What I do not understand, is because it works not local and external.


Oct, 2018 - Permalink