REST-API through Proxyserver

Hi Dominic

To test if your proxyserver could be the issue, try creating a simple http sensor and use the same url as above. Proxy can be configured in Setup - System Administration - Core&Probes (first entry "use proxy server)

I created a HTTP XML/REST Wert sensor in my PRTG installation with URL: http://www.pegelonline.wsv.de/webservices/rest-api/v2/stations/5990020/W/currentmeasurement.json XMLNode: value

And I get back 574 (the same as when I browse your URL)

regards Thomas

Hi Dominic,

It seems that the proxy server & credentials are not parsed to the sensor. They should show in the debug text file as -ps=proxyserver -pu=proxyuser -pp=proxypassword

Hi,

I tried using the normal HTTP sensor type, but also there I do not get positive results (this sensor gives a connection time-out). So it looks as the Proxy is not used for sensors ... it is configured as it should, loading the PRTG system patches and license-checking works perfectly.

So I guess PRTG has to answer this ...

Oh, looks you wrote in the same minute.

So we know the proxy isn't passed - is there any way for a workarround for the time until Paessler might give us the option passing the sets into the sensors settings? As far as I can see the parameters are directly given to the XMLValue.exe, no script or batch to be modified ...

Br Dominic

Hi Dominic

Hmm thats strange, because: https://www.paessler.com/manuals/prtg/probes_settings

If the Autoupdate works, but the sensor isn't, please configure the proxy again in the HTTP Sensor setting itself and try again, instead of using the global proxy settings.

regards Thomas

Dear Dominic

To use a proxy server, please create the HTTP sensor as Custom Exe/Script sensor. This way you can use additional parameters not available through the sensor UI and provide a proxy server address as well.

To do this, please open your PRTG installation folder and copy the file "Sensor System\XMLValue.exe" into the "Custom Sensors\EXE" path. Then create an Exe/Script sensor.

Hi Thomas - that was a good hint. I added the proxy to the http sensor and it worked. Then I realized without setting it it uses the inherited settings from "obove", and I did not set the proxy in any group or the root (main group). So I entered it there instead of the system settings dialogue and it run.

But unfortunately it did not work for the REST sensor, as it also do not have a settings section for the proxy (and therefore not the standard behaviour of inheriting the settings from overlaying group).

So it still looks as it might be an PRTG issue?!

Hi Arne,

thanks a lot, that way it runs smoothly!!

Br Dominic