Errors that are specific to DNS monitors, as well as DNS-related errors for other monitor types
For most monitor types we try to make a TCP connection to the host and port specified in the monitor before we perform any actual checks. We do this to verify whether we can make a low-level connection to your server. In order to do this, we first need to know an IP address that corresponds to that domain name.
To translate a domain name to an IP address (in other words: to resolve the domain) we use the DNS servers available to us at the checkpoint location performing the check. Depending on the location, this could be a DNS service provided by our local service provider, or a public DNS service such as Google DNS.
If the DNS service cannot find the domain you specified, we cannot continue the monitor check. In that case, we will show this DNS lookup error to indicate that your domain could not be resolved.
Possible causes:
a misconfiguration in the DNS records for your domain;
a problem at the provider that handles the DNS registration for your domain;
a possible interruption in the DNS service we are using. Please contact Support so we can investigate this when you've verified any possible issues at your end.
Similar to error 1000 (DNS lookup error), we were unable to resolve your domain to an IP address. In this case, we did not receive any response from our DNS service regarding your domain name. Please verify that your DNS records are correct, or contact Support.
Your DNS monitor is configured to execute an A record query on the DNS service available at the checkpoint location, or on the DNS server you specified. This error indicates that the DNS service could not find an A record for the domain you specified in the Test value field.
Your DNS monitor is configured to execute a CNAME record query on the DNS service available at the checkpoint location, or on the DNS server you specified. This error indicates that the DNS service could not find a CNAME record for the domain you specified in the Test value field.
Your DNS monitor is configured to execute an MX record query on the DNS service available at the checkpoint location, or on the DNS server you specified. This error indicates that the DNS service could not find an MX record for the domain you specified in the Test value field.
Your DNS monitor is configured to execute an NS record query on the DNS service available at the checkpoint location, or on the DNS server you specified. This error indicates that the DNS service could not find an NS record for the domain you specified in the Test value field.
Your DNS monitor is configured to execute a TXT record query on the DNS service available at the checkpoint location, or on the DNS server you specified. This error indicates that the DNS service could not find a TXT record for the domain you specified in the Test value field.
Your DNS monitor is configured to execute a SOA record query on the DNS service available at the checkpoint location, or on the DNS server you specified. This error indicates that the DNS service could not find a SOA record for the domain you specified in the Test value field.
During the execution of your DNS monitor, we received a correctly formatted but unexpected result from the remote DNS server. The DNS monitor tested for a specific result that was not found. Review the monitor check details to see the exact contents of the result.
This error may occur temporarily when you have recently changed the DNS entries for your domain, if the remote DNS server has not renewed its cache yet.
Your DNS monitor is configured to execute an AAAA record query on the DNS service available at the checkpoint location, or on the DNS server you specified. This error indicates that the DNS service could not find an AAAA record for the domain you specified in the Test value field.
During the execution of your DNS monitor, we received a correctly formatted but unexpected result from the remote DNS server. In particular, the DNS monitor tested for a specific result that should not be present. Such a result was found in the response from the specified DNS server. Review the monitor check details to see the exact contents of the result.
This error may occur temporarily when you have recently changed the DNS entries for your domain, if the remote DNS server has not renewed its cache yet.
We sent multiple DNS queries to the specified DNS server, but we never received any response. The DNS server is unavailable or not accepting DNS queries.
If this error occurs only in checks from a certain geographical location, this might indicate that your DNS server is not correctly handling queries from that specific region.
Errors that pertain to the underlying TCP/IP network connections used to monitor your systems
Our checkpoint server did not get any response while trying to make a connection to your website or host.
At the start of most monitor checks, we try to make a TCP connection to the host and port specified in the monitor. The host did not respond to our attempts in a timely fashion. This could indicate that:
there is a problem with your website or host, such as:
your server is down
there is a network outage at your hosting provider
your website is overloaded with traffic, rendering it unable to respond
there is a problem with the connectivity between our checkpoint location and your server
For more detailed diagnostic information, users of Uptrends Professional and up can check the traceroute information included in the Check Details of the first confirmed error (not always available).
If this error is reported only by checkpoints in a particular geographical region, this may indicate that your website is not reachable from that region.
For ongoing connectivity issues, you may also use the Uptrends Tools to get a global overview of reachability of your website.
If your host or website is not publicly accessible by design, please check if you have added all our checkpoint servers to your whitelist - see our list of checkpoints for more information. You can also use our API to retrieve the list in a machine-readable format.
This indicates that the checkpoint server was not able to connect to your website.
This is a test on the lowest level, trying to make a connection to the TCP address and port defined in the monitor. The website responded, but we were not able to establish a connection.
If you experience this error immediately after setting up a monitor, please check if you need to add our checkpoint servers to your whitelisting.
Errors on the HTTP protocol level, both for basic HTTP(S) checks and for other monitor types that use the HTTP protocol
The browser simulator on the checkpoint server was not able to connect to your website.
This usually indicates some kind of infrastructure problem between the test server and your website.
The browser on the checkpoint was not able to resolve the domain name to an IP address.
This indicates an error in the DNS server of your domain or your domain or the IP address of your website does not respond.
This error happens when the HTTP response code we received from the web server indicates an error. Typically, this could be a 404 Not Found, a 500 Internal Server Error, 503 Service Not Available, or any other HTTP error code that represents an error situation. HTTP(S) monitors want to ensure that the response we receive is in the 20x range, i.e. 200 OK, 201 Created, etc.
The fact that we received an unexpected error code does imply that we could contact the web server correctly in terms of connectivity and authentication (if applicable) and that we received a response in a reasonable amount of time. The generic problem is that the web server did not return the response we expected to see, but what the actual problem was depends on the HTTP response code.
In some cases, the HTTP response code we found is actually what you want to verify. For example, you may be interested to monitor that requesting a non-existing page (https://www.mysite.com/does-not-exist) correctly returns a 404 error. In that case, change the 'Check HTTP status' option in your monitor to the HTTP status code you expect to see. Please see this blog post about expected HTTP status codes for more information.
This indicates an error during the download of the HTTP response from your website.
The checkpoint server tries to establish an SSL channel to the webserver, but the negotiation failed.
The checkpoint uses:
the TLS version(s) defined in the monitor
the ciphersuites provided by the platform of the checkpoint server (either Windows Server 2008 R2, Windows Server 2012 R2 or Windows Server 2016)
Server Name Indication (SNI) where relevant
Session Resumption where relevant
This could indicate a problem with:
the certificate that is being used by the webserver
the ciphersuites the webserver allows for connections
another configuration issue
As a first step, it's suggested to check your website with SSLLabs. For the handshake simulation, please check IE11 with Win 7, 8.1 and 10.
This indicates that the checkpoint server could not deliver a complete HTTP request to your web server.
This indicates that the checkpoint server was waiting for the response of your website server and timed out.
This means that the Uptrends service succeeded in contacting the web server, but did not receive a response in a timely fashion when posting a request or waiting for a response.
This means that we could start an SSL negotiation with your web server, but that there was an issue with the certificate returned. It was invalid, or we were not able to validate the certificate. Please check the certificate, and check that the revocation status of the certificate can be checked.
Your monitor has an active value for the 'Page content match' setting. This means that we'll scan the content we've received back from your server to verify that the content contains the phrase you've specified. This phrase (can be a word, sentence or a more complex pattern) should be indicative of a successful request.
However, this error indicates that we could not find the content we were expecting to see. Contacting your server and executing the request went well, but the content of the web page we loaded did not contain that crucial piece of text.
Possible causes to look out for:
Perhaps the content of your web page simply changed, and the content match value should be changed accordingly.
If the page should have contained the content, this error could indicate that we found a problem in your web application at the time this check was executed. We don't know what caused the error - we only noticed that the page behaved differently. Perhaps there was an error message on the page instead of the regular content, or perhaps only part of the page was missing.
This error is basically the reverse of 'Content not found'. Your monitor has an active value for the 'Page content match' setting, and it was set up to verify that particular content is NOT present on the page by preceding it with an exclamation point. You can use this approach to scan for particular cases that are indicative of a problem on your website.
However, this error points out that we did detect the offending content. Your web page is available, but its behavior is unexpected. Possible causes to look out for:
You've explicitly specified one or more phrases that point to a problem situation on your side. Check whether any of those problem situations did in fact occur at the time.
Perhaps the content you specified also appears at a different place in the content of your web page (possibly as part of a different word). Try adjusting the content value so it uniquely identifies the problem situation you are trying to detect.
This indicates that the checkpoint server was waiting for the response of your website server and timed out. This means that the Uptrends service succeeded in contacting the web server (and POST data, if relevant), but did not receive a full response in a timely fashion.
The 'Page content match' option is generally used to verify that a web page contains a particular word or phrase, or that a particular word is absent. Using some advanced options, it also allows you to check the content for date and/or time values. In fact, we can verify that those dates and times are recent enough. For example, this approach lets you verify that a phrase like 'Page last updated on 3/23/2017 09:00' is present on the page and represents a date that is not older than, say, one hour. Or a day, whatever you need.
This particular message tells you that we found that date, but that it was too old (or maybe even too new). This may indicate that the process that updates your web page didn't run according to your usual time schedule.
This error is the reverse of 'No recent date/time found'. Instead of looking for a recent date/time, we can also check that a recent date/time is NOT present, and alert you if it is. For example, consider a web page that lists a number of incident reports, with a time and date for each incident. There may be some older entries that are not bothering you, but you want to be notified as soon as a recent entry shows up.
This message tells you that we did detect a date that is within the time frame you specified. It indicates that the content on the website contains some entries that need your attention.
The 'Page content match' option allows you to specify some advanced pattern searches using Regular Expression notation. Due to the nature of regular expressions, it is possible that executing the content check takes a very long time. Most checks take less than a second, but it could take much longer.
In some extreme cases, we may have to abort the content check if it takes too long. Please contact Support so we can work with you to specify a more efficient content check.
The 'Page content match' option allows you to specify some advanced pattern searches using Regular Expression notation. This means that certain characters have a special meaning, and not using them correctly could cause unwanted situations.
The content you specify in the 'Page content match' field is always interpreted as a regular expression. If the content you are looking for contains special characters and they are not used correctly, you could end up using an invalid expression.
The following characters are considered special:\ ^ $ { } [ ] ( ) . * + ? | < > - &
If any of these characters are just part of the plain content you are looking to monitor, please precede that character by a backslash \ character.
By default, HTTP(S) monitors expect a HTTP 200 status code (or at least a code in the 20x range) when the request finishes. If it doesn't, we'll generate error code 3009. Please read that entry for more information.
Sometimes, however, you actually want to monitor error situations corresponding to HTTP status codes other than 200. In that case, you can use the 'Check HTTP status' option to specify a particular status code. This approach is illustrated in this blog post about expected HTTP status codes.
This error code indicates that even though we received a response from your server, we got a different HTTP response code; not the one you specified. The response code we received can be seen in the details for that particular check.
Errors that are specific to Ping monitors
The ping request failed because the destination host was unreachable. This error is most likely caused by a network infrastructure problem at your hosting provider.
The ping request failed because the destination network was unreachable. This error is most likely caused by a network infrastructure problem at your hosting provider, or by an issue at one of the intermediate backbone providers.
The ping request did not finish within the specified timeout. This error can occur when we cannot reach the destination host.
Errors related to FTP (File Transfer Protocol) and SFTP (secure FTP) monitors
There was no response from the FTP server during the FTP test.
Errors that occur while establishing (and maintaining) secure connections using the TLS protocol
There was no certificate present for the website.
Please check your website configuration, and verify that the certificate has been installed correctly and that it is valid for the domain name you specified.
An SSL certificate was found for your website. However, the fingerprint of the website does not match the fingerprint value specified in the monitor. Please check the setup of your monitor for the correct fingerprint value.
The monitor executed successfully, but took too long according to the Performance Limit 1 you've set in the monitor.
The monitor executed successfully, but took too long according to the Performance Limit 2 you've set in the monitor.
Errors that occur during the execution of transaction monitor checks
As part of a transaction, the browser navigates to a URL. This error indicates that this navigate operation has failed.
Possible issues:
The checkpoint could not resolve the URL in the DNS to an IP address.
The browser could not connect to the web site.
The page, or the page we're being redirected to, returns an HTTP status code of 400 or up (for example 404 Not Found, 500 Internal Server Error, 401 Authorization Required).
When you see this error from one checkpoint, this could indicate an infrastructure issue. When you see this issue from multiple checkpoints, it is a strong indication that your website is unavailable.
More insights about the availability of the URL may be obtained by creating an HTTP(S) monitor.
At the specified location in the transaction, we search for content. This test can be positive (the content should be there), or negative (the content should not be there).
This error indicates that the content is not as expected. This can be caused e.g. by:
a change of the content
a problem in a previous step getting here.
Perhaps the screenshot with the transaction gives you some extra insights.
The HTML element required to execute this step in the transaction cannot be found. This could for example be a button or link to click on, or an item in a select list to select.
This error indicates that the content of the current page is not as expected. This can be caused e.g. by:
a change of the content of the page
a problem in a previous step getting here.
Perhaps the screenshot with the transaction gives you some extra insights
The Select option required to execute this step in the transaction cannot be found in the current page.
This can be caused e.g. by:
a change of the content of the page
a problem in a previous step getting here.
Errors specific to the Full Page Check monitor type
As part of a Full Page Check, the browser navigates to the URL you specified. Similar to what was described for error 7001, this error indicates that this navigate operation has failed. Please see the entry for 7001 to review possible causes.
It took too long to fully load the requested page in the browser. In general, this issue may be caused by:
limited bandwidth between the checkpoint and the website
a slow website
slow 3rd party elements that have not been loaded asynchronous
Please check the waterfall to see what may be causing the issue.