Hi,

There is a HTTPS redirect we would like to monitor with PRTG but those Always seem to fail with a "500 internal" error. We tried a basic http sensors and an advanced one and tried to change some settings. (http 1.0/1.1, alternative, ...)

SSL Cert Check on this domain does work. For some reason a simple check if the site is up doesn't.

redirect is like this: http(s):eloket.customer.be -> https://login.othersite.be

Article Comments

Hi, The error code returned (500) indicates that something is going wrong on the server side here. Do you have access to said webserver? Especially the error logs? If so, could you check what is going wrong here?


Jan, 2016 - Permalink

Hi,

Thanks for the reply. I don't really have access to the server logs per se but the website is available and can be accessed without any errors when I browse it. I'm not sure why PRTG thinks it cannot access it.


Jan, 2016 - Permalink

Hi,
unfortunately an error 500 delivered by a webserver, means that the server cannot handle the request because it is causing an error in the running application itself. Without access to the error logs there is basically 0 chance debugging why this happens and adjust the requests accordingly. You might try another sensor here. Especially the HTTP Full Page Sensor and see if this helps as this sensor uses another requesting method.


Jan, 2016 - Permalink

Hi,

I tried some of the different sensors. Some of them gave the same error. But the HTTP Full Page Sensor seems to work.

This is all I need at the moment.

Thanks.


Jan, 2016 - Permalink