We have two machines behind firewalls so we use the HTTP Push Data Advanced sensor to monitor them; HTTP1 and HTTP2. Both sensors are on one device. They have worked for many months.

After upgrading PRTG to 17.1.30.1719 HTTP1 stopped working. It connects but receives { "status": "Ok", "Matching Sensors": "0" } HTTP2 continued to work fine.

After creating a new sensor HTTP3 and restarting PRTG; HTTP3 works but HTTP2 stopped working with same symptoms.

Have now upgraded PRTG to 17.1.31.1691+ [Preview] but no improvement.

Article Comments

Hi Javpaul,

Please update to the latest stable version. The issue should be fixed within version 17.1.30.1719 and above as mentioned on our release notes:

APRIL 4TH 2017 – VERSION 17.1.30.1719

FIXEDSENSORSHTTP PUSH SENSORSFixed a regression that broke multiple HTTP Push based sensors running on the same listening port.

Best regards, Felix


Apr, 2017 - Permalink

Thanks. Installing 17.1.30.1719 caused the problem. Update to 17.2.30.1767 resolved the issue.


Apr, 2017 - Permalink

Has there been another regression with this bug in: Version 17.3.33.2830? We're seeing the same behavior for new HTTP push sensors we're attempting to create.


Sep, 2017 - Permalink

Hi,

Could you please elaborate what exactly happens? Is the behavior similar to Javpaul's explanation and do newly created sensors work correctly?

Best regards, Felix


Sep, 2017 - Permalink