DNS could not be resolved (socket error # 11004) using cloud http sensor

Modified on 2025-06-10 16:36:25 +0200

Hi Team

I use windows 10 and prtg 17; my application is easily accessible from the outside.

I want to test the availability of my application from the outside using the http cloud sensor. But still get the error DNS could not be resolved (socket error # 11004).

what to do?

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.

Hello,

The Cloud HTTP and Cloud Ping sensors are deprecated and are being replaced by the Cloud HTTP v2 and Cloud Ping v2 sensors. So we are going to shut down the servers that the old (v1) sensors use. Because of this we can no longer provide support for the old sensors. I can only suggest that you update PRTG to a newer version and try out the v2 Cloud sensors.

Kind regards,
Sasa Ignjatovic, Tech Support Team

Jun, 2023 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

DNS could not be resolved (socket error # 11004) using cloud http sensor

Article CommentsAttention: 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.

Search

Attention

Related Articles

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.