We set up the followning status site:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
    <head>
        <title>
               STATUS
        </title>
        <meta http-equiv="X-UA-Compatible" content="IE=8" />
        <META HTTP-EQUIV="Content-Type" content="text/html; charset=UTF-8">
        <link rel="stylesheet" href="/home/Css/login.css" type="text/css">
    </head>
    <body>
    
        <div style="display:none">[100][99]</div>
    </body>
</html>

The sensor connects to the web page via HTTPS with two integer values. When executing the request, I get the error Request returned not enough values. (0/2) (code: PE174)

Article Comments

Please go to the sensor settings and take a look at the setting "Number of channels". This setting must in your case not be higher than 2, because you only provide two different values in []. If there are more channels, then values, you will get the error message, that you posted.


Jun, 2013 - Permalink

I did some testing and found out that the sensor does work when I check the system on the same network/without a proxy.

But when I want to monitor the "WAN side" and therefore have to use the reverse proxy it does not work. - The error code PE174 arises.

The number of channels is 2


Jun, 2013 - Permalink

Does it work, if you use the same proxy but another website?

Does it work, if yo use the proxy with your browser and then open the url, that is used for the sensor?

Does your proxy require authentication? What authentication type is required?


Jun, 2013 - Permalink

It seems as if it does not work at all when I use the proxy. No authentication is required and when I open the website in my browser everything works as expected.


Jun, 2013 - Permalink

It would be really helpful, if we could take a look at the proxy. Could you please send an email with the proxy settings to our support team? Please mention the url to this article, so we know, what to do with the proxy.


Jun, 2013 - Permalink

This article applies as of PRTG 22

JavaScript redirects

The URL that you want to monitor returned JavaScript, which redirected the browser to another URL. The HTTP sensors (except the HTTP Full Web Page sensor) are not capable of following JavaScript redirects.

Either use HTTP-based redirects (302 temporarily not available) or use the URL that the redirection points to for the sensor.


Jun, 2013 - Permalink

Thanks for this very useful information!


Jun, 2013 - Permalink

We're glad, we could help!


Jun, 2013 - Permalink