Hi Team,

I am having trouble with the HTTP sensor on a local device. I am using it to ensure we can log into a power system or switch but I periodically get error on the sensor. Sometimes it will be fine and sometimes it will error. If i reset the device it will work for a while before the error occurs again. My device is http:
10.96.70.134 I have looked at the description of SNI etc but can't work it out. Please can you help with the settings?

Cheers

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 there,

Please let me know which certain error message is displayed.


Aug, 2020 - Permalink

Thanks for the quick reply. The error I am seeing is:

Failed to establish secure connection [Step 0] Error connecting with SSL. EOF was observed that violates the protocol [Step 1] Error connecting with SSL. EOF was observed that violates the protocol [Step 2] Error connecting with SSL. EOF was observed that violates the protocol [Step 3] Error connecting with SSL. EOF was observed that violates the protocol [Step 4] Error connecting with SSL. EOF was observed that violates the protocol [Step 5] Error connecting with SSL. EOF was observed that violates the protocol [Unsecure] IOHandler value is not valid


Aug, 2020 - Permalink

Hi

I have several of these devices and have looked at another one that was paused. I am also seeing error:

Connection reset by peer (socket error # 10054)

Thanks


Aug, 2020 - Permalink

Hi Hayden,

Thank you for the update.

Please enter as SNI the address of your target device without "HTTP:/ /" and check whether this works.

In addition, please note that the error Connection reset by peer (socket error # 10054) occurs when another device or the target device refuses the connection. Therefore, please check if a firewall or the target device blocks the traffic.


Aug, 2020 - Permalink

Hi, I do not know what the SNI is for this device. To log into it i simply browse to the IP address of the device. I do not need to add HTTP to connect. PLease can you provide more information? I can see when I log into the device that the connection is not secure. I have 12 of these in total and 8 out of 12 are currently OK with 4 in error. After a long period of time some of these that are currently working will error and I have to reset the controller for it to work again.

Thanks


Aug, 2020 - Permalink

Please enter simply the address which you use in the browser as SNI (without HTTPS:/ /). We made the experience that this helps in many cases.


Aug, 2020 - Permalink

Hi again,

Without changing anything some of these sensors are no longer reporting an error state. Please can you tell me from above where I put the SNI into the sensor configuration?


Aug, 2020 - Permalink

The SNI is entered in the Sensor settings.


Aug, 2020 - Permalink

Ok. Because this sensor works for some of the time and then fails I don't believe it is this.

I suspect the HTTP sensor is opening an HTTP session every time it scans the device. Because the we interface on this type of device is not commonly used I suspect there are a limited number of times a single device can open these sessions. I have been scanning every 30 seconds but I believe this is too often. Once this sensor fails I believe there is a timeout where it resets the sessions and then comes alive again. Then the sensor can be turned back on again and it will work for a while longer.

I have changed by scan time to 1 hour and will monitor to see if this fixes the issue.


Aug, 2020 - Permalink