HTTP/1.1 500 Internal Server Error on HTTP Advanced Sensor

Modified on 2025-06-10 13:23:03 +0200

Hi I have added a new sensor to an existing single installation of PRTG. It has over 100 sensors on this single probe. None have caused an issue like this before. The sensor does a POST every 60 seconds to a specified URL. The URL is correct and can be accessed and has been used several other times on this probe for different sensors. The postdata is correct and has been verified in SOAPUI. The custom content type is text/xml; charset=utf-8 Everything else is set to default apart from a response which never changes and is again verified in SOAPUI. The error on the sensor is HTTP/1.1 500 Internal Server Error which does not really direct me to what the problem can be. On the probe itself I can access the specified URL just fine. Anyone have any ideas?

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hi,
the error code 500 means something is going wrong on the target server. Are you able to check the web server error logs there?

Dec, 2014 - Permalink

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.

HTTP/1.1 500 Internal Server Error on HTTP Advanced Sensor

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.