Troubleshoot Cloud Monitor site monitoring issues using these protocol-specific error codes and standard HTTP status codes.
Always check Cloud Monitor error codes first. If detection fails due to DNS or network errors, no server response is returned and no HTTP status code is available.
Cloud Monitor error codes
|
Protocol |
Error code |
Description |
|
HTTP |
610 |
Detection or request timed out, including TCP and SSL connection timeouts. Default timeout: 30 seconds. |
|
613 |
DNS resolution error. |
|
|
615 |
Response content does not match the specified content. |
|
|
616 |
Authentication failed. |
|
|
611 |
Monitoring failed. |
|
|
617 |
Maximum redirections exceeded.
|
|
|
618 |
Detection assertion failed. Check detection details. |
|
|
703 |
The error code returned because the server cannot be monitored over a private network. For more information about how to monitor servers over a private network, see Create an availability monitoring task. |
|
|
PING |
550 |
Network connection failed. |
|
610 |
No packets received within 2 seconds. |
|
|
613 |
Hostname cannot be resolved to an IP address. |
|
|
615 |
Packet loss exceeded 10%. |
|
|
617 |
IP address of the monitored object is unreachable. |
|
|
618 |
Detection assertion failed. Check detection details. |
|
|
703 |
The error code returned because the server cannot be monitored over a private network. For more information about how to monitor servers over a private network, see Create an availability monitoring task. |
|
|
TCP |
550 |
Socket cannot be opened. All system resources are depleted. |
|
610 |
No response returned or response timed out. |
|
|
611 |
Connection timed out or rejected. |
|
|
615 |
Response content does not match the specified content. |
|
|
618 |
Detection assertion failed. Check detection details. |
|
|
703 |
The error code returned because the server cannot be monitored over a private network. For more information about how to monitor servers over a private network, see Create an availability monitoring task. |
|
|
UDP |
550 |
Socket cannot be opened. All system resources are depleted. |
|
611 |
Hostname cannot be resolved and connection failed. |
|
|
610 |
Failed to send request or receive response. |
|
|
615 |
Required content not found in the response. |
|
|
618 |
Detection assertion failed. Check detection details. |
|
|
703 |
Private network monitoring not supported. Use PCs to monitor sites. |
|
|
DNS |
610 |
DNS resolution error. |
|
613 |
DNS query failed. |
|
|
614 |
DNS hijacking detected. |
|
|
615 |
Required content not found in the response. |
|
|
618 |
Detection assertion failed. Check detection details. |
|
|
703 |
The error code returned because the server cannot be monitored over a private network. For more information about how to monitor servers over a private network, see Create an availability monitoring task. |
|
|
SMTP |
610 |
Connection timed out. |
|
611 |
Site unreachable due to DNS resolution failure, invalid email address, or SMTP client initialization failure. |
|
|
616 |
Logon request rejected. |
|
|
703 |
The error code returned because the server cannot be monitored over a private network. For more information about how to monitor servers over a private network, see Create an availability monitoring task. |
|
|
POP3 |
611 |
Site unreachable. |
|
703 |
The error code returned because the server cannot be monitored over a private network. For more information about how to monitor servers over a private network, see Create an availability monitoring task. |
|
|
FTP |
610 |
FTP transmission failed. |
|
611 |
DNS resolution or TCP connection failed. |
|
|
616 |
Logon failed. |
|
|
703 |
The error code returned because the server cannot be monitored over a private network. For more information about how to monitor servers over a private network, see Create an availability monitoring task. |
Common HTTP status codes
|
Status code |
Message |
Description |
|
200 |
OK |
Request succeeded. All 2XX status codes indicate success. |
|
300 |
Multiple Choices |
Multiple options available. The server selects one based on the user agent or provides a choice list. |
|
301 |
Moved Permanently |
Resource permanently moved. GET/HEAD requests redirect to the new URL. Signals search engines to update. |
|
302 |
Found |
Page temporarily moved. The client must continue using the original URL. Similar to 301 for GET/HEAD requests. |
|
303 |
See Other |
User agent must send a GET request to a different URL. The server redirects all non-HEAD requests to the new URL. |
|
304 |
Not Modified |
Resource unchanged since the last request. No content returned. |
|
305 |
Use Proxy |
Requested resource must be accessed through a proxy specified in the response. |
|
307 |
Temporary Redirect |
Similar to 302. Resource temporarily moved to the URL in the Location header. |
|
308 |
Permanent Redirect |
Resource permanently moved to the URL in the Location header. |
|
400 |
Bad Request |
Server cannot process the request due to invalid syntax. |
|
401 |
Unauthorized |
Authentication required. |
|
403 |
Forbidden |
Server rejected the request. |
|
404 |
Not Found |
Requested page not found on the server. |
|
405 |
Method Not Allowed |
Request method not supported. |
|
406 |
Not Acceptable |
Request content not acceptable. |
|
407 |
Proxy Authentication Required |
Proxy authentication required. Similar to 401, but the server specifies the proxy in the response. |
|
408 |
Request Timeout |
Server did not receive a request within the timeout period. |
|
409 |
Conflict |
Request conflicts with the current resource state. Response includes conflict details, such as differences between conflicting PUT requests. |
|
411 |
Length Required |
Server requires a Content-Length header. Request denied. |
|
412 |
Precondition Failed |
Server cannot meet a precondition specified in the request. |
|
413 |
Request Entity Too Large |
Request size exceeds the server's processing capacity. |
|
414 |
Request-URL Too Long |
URL too long for the server to process. |
|
415 |
Unsupported Media Type |
Request contains a media type not supported by the server. |
|
416 |
Requested Range Not Satisfiable |
Invalid Range header in the request. |
|
417 |
Expectation Failed |
Server cannot meet the Expect header requirements. |
|
499 |
Client Closed Request |
Client closed the request before the server sent a response. |
|
500 |
Internal Server Error |
Internal server error. Contact the system administrator. |
|
501 |
Not Implemented |
Server does not support a feature required by the request, such as an unrecognized request method. |
|
502 |
Bad Gateway |
Gateway or proxy received an invalid upstream response, such as from the monitored site. |
|
503 |
Service Unavailable |
Server temporarily unavailable due to overload or maintenance. Usually resolves quickly. |
|
504 |
Gateway Timeout |
Gateway or proxy timed out waiting for an upstream response, such as from the monitored site. |
|
505 |
HTTP Version Not Supported |
Server does not support the HTTP protocol version used in the request. |