New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


downstate after redirect

Votes:

0

Your Vote:

Up

Down

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

http https redirect

Created on Jan 19, 2016 8:55:52 AM by  Wim Caudenbergh (60) 1 1



4 Replies

Votes:

0

Your Vote:

Up

Down

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?

Created on Jan 20, 2016 3:58:00 PM by  Konstantin Wolff [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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.

Created on Jan 20, 2016 4:07:09 PM by  Wim Caudenbergh (60) 1 1



Votes:

0

Your Vote:

Up

Down

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.

Created on Jan 21, 2016 2:26:23 PM by  Konstantin Wolff [Paessler Support]



Votes:

0

Your Vote:

Up

Down

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.

Created on Jan 21, 2016 3:48:14 PM by  Wim Caudenbergh (60) 1 1



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.