I recently upgraded my PRTG monitoring environment from version 9.2.1.2280 to version 12.2.2.2157. After the upgrade and fixing the documented changes (such as VMware sensors, etc.), I have a HTTP Transaction Sensor that is now failing. This was working perfectly before the upgrade.

This is for an internal only website using https.

It performs a GET to the homepage and then a POST to login and checks the page for a particular string. I have "Store latest HTML results" enabled and it looks like the POST data (username and password) aren't being passed.

I see that in version 12.2.1.1923/1924 there was a bugfix for what appears to be the same issue.

I tried creating a new sensor with the same parameters as the upgraded sensor and it fails as well.

Any help is appreciated. Thank you.

Article Comments

Hi,
is the website doing the authentication somehow cookie based? If so, we have implemented another fix for the sensor. But I'm afraid that is only implemented in the canary build of PRTG yet.
Best regards


Jun, 2012 - Permalink

Yes, it is using cookies.

Any idea when that fix will hit mainstream releases?


Jun, 2012 - Permalink

Hi,
the change has also be merged to the preview version already and we hope to release the new stable version sometime next week.
Best regards


Jun, 2012 - Permalink