Overview This error indicates that the SSL/TLS connection failed because the server is using Diffie-Hellman (DH) parameters that are considered too small by modern security standards. It is most commonly encountered when connecting to servers that still use weak or outdated cryptographic configurations. What causes this error? The error occurs when: Modern OpenSSL versions (1.1.1+ […]
Category: 17 Common Errors
Error 35: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
Cause This error occurs when the monitoring server fails to complete the SSL/TLS handshake with the target website. In most real-world cases, this is not caused by outdated SSL protocols, but by an inconsistent or broken server-side TLS configuration. A common scenario is when the domain resolves to multiple IP addresses, with at least one […]
Error 0: keyword not found
Cause This error can be found in your Location Fail Log for the website uptime monitors that you have configured keyword monitoring for and the specified keyword that you configured our system to look for is not found on the monitored target page. Our system will look for the specified keyword only in the HTML source […]
HTTP Code [403] Error 0: (Xms)
Cause These errors can be encountered in your Location Fail Log for website uptime monitors when the monitored website is answering with a 403 Forbidden response towards our monitoring locations. This HTTP code basically means that the website is denying access for these web requests, so the website is not considered UP/healthy by our monitoring […]
Error 28: Connection timed out after X milliseconds (Xms)
Similar errors Cause These errors can appear in your Location Fail Log when the monitored target fails to respond within the configured timeout time frame. For example: if your website uptime monitor has a configured timeout of 10 seconds, a timeout error happens if your website fails to load within 10 seconds. These errors are […]
Error 7: Failed to connect to <target>: Connection refused
Similar errors Cause You can get this Uptime Monitoring error in your Location Fail Log if the monitored target is refusing to allow our uptime monitoring nodes to connect to it. This can be caused by any number of reasons, among which: Fix We recommend looking on your server or network to see what exactly is it […]
Error 0: Name or service not known
Similar errors Cause You can get this Uptime Monitoring error in your Location Fail Log if the monitored hostname is not resolved properly. Our monitoring locations do not cache DNS results, so they perform fresh DNS queries on every new uptime check of your monitored target. Fix It is advised to check up on your nameservers to […]
Error 92: HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR
You can get this Uptime Monitoring error in your Location Fail Log if your web server uses HTTP/2 and responds with a connection-specific header field. What is the issue? RFC 7540 indicates that the HTTP/2 response MUST NOT include connection-specific header fields, and if such headers exist, the response is considered malformed. How to find […]
Error 35: error:0A000152:SSL routines::unsafe legacy renegotiation disabled
Cause You can get this Uptime Monitoring error in your Location Fail Log if your web server does not support SSL Secure Renegotiation. This is a severe SSL vulnerability (CVE-2009-3555) that could allow an attacker to insert data into secured HTTPS sessions. Fix It is advisable to upgrade your server and use the current SSL […]
Error 35: error:0A000102:SSL routines::unsupported protocol
Overview This error indicates that the SSL/TLS connection failed because the server and client could not agree on a supported protocol version. It typically occurs when the server only supports outdated SSL/TLS versions that are no longer accepted by modern clients. What causes this error? The error occurs when: Modern OpenSSL versions (especially 1.1.1+ and […]