Checking For Errored URLs
URLs that won't capture in the archive go into either an Inaccessible status or an Error status.
-
Inaccessible: We are unable to find your page. It has either been moved, has blocked our IP address, or does not exist.
- Our IP addresses must be whitelisted. They are:
- 52.23.29.34
- 54.235.88.205
- 54.84.64.101
- Our IP addresses must be whitelisted. They are:
-
Error: Our system knows your page exists, but there is an issue preventing us from capturing it.
Please follow the steps below to find additional information on the source of these errors for Inaccessible and Error statuses.
Article Navigation
Finding the Source of Errors Instructions
- Log in to your archive
- Click the Configure tab.
- Select the Web Snapshots tab on the left.
- In the Site URLs section, click the dropdown and select All Errors, or select a specific Error Status.
- You can also hover over any Error status to see the specific error message for that URL.
- In the Site URLs section, click the dropdown and select Inaccessible.
- Hover over any Inaccessible status to see the specific error message for that URL.
Error Codes And Recommended Actions
301 Moved Permanently
Description: Indicates that the requested resource has been definitively moved to the URL given by the location headers. A browser redirects to the new URL and search engines update their links to the resource. This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived.
- If you determine that the URL (s) should not be archived, disable them.
- Reach out to our support team to get more information on the status of your URL(s)
302 Found
Description: Indicates that the resource requested has been temporarily moved to the URL given by the Location header. A browser redirects to this page but search engines don't update their links to the resource (in 'SEO-speak', it is said that the 'link-juice' is not sent to the new URL). This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Determine Whether the Redirects Are Valid
- Check Your Plugins
- Ensure That Your WordPress URL Settings Are Configured Correctly
- Check Your Server Configuration
- Speak to Your Web Host
400 Bad Request
Description: The server could not understand the request due to invalid syntax. This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived.
- If you determine that the URL (s) should not be archived, disable them.
- Reach out to our support team to get more information on the status of your URL(s).
401 Unauthorized
Description: Indicates that the client request has not been completed because it lacks valid authentication credentials for the requested resource. This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived.
- If you determine that the URL(s) should not be archived, disable them.
- If the URLs do exist or you believe the URLs should exist, report the URLs to your web host.
- Sometimes this error can indicate that the content is password protected.
403 Forbidden
Description: The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the client’s identity is known to the server. This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived. This error could indicate that a web host is blocking our servers from accessing the URL.
- If you determine that the URL (s) should not be archived, disable them.
- If the URLs do exist or you believe the URLs should exist, report the URLs to your web host. Please ensure your web host allows the following IP addresses:
- 52.23.29.34
- 54.235.88.205
- 54.84.64.101
- Re-enable the URLs.
404 Not Found
Description: The server can not find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 to hide the existence of a resource from an unauthorized client. This response code is probably the most famous one due to its frequent occurrence on the web. This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived. This error could indicate that a web host is blocking our servers from accessing the URL.
- If you determine that the URL (s) should not be archived, disable them.
- If the URLs do exist or you believe the URLs should exist, report the URLs to your web host. Please ensure your web host allows the following IP addresses:
- 52.23.29.34,
- 54.235.88.205
- 54.84.64.101
- Re-enable the URLs.
410 Gone
Description: This response is sent when the requested content has been permanently deleted from the server, with no forwarding address. Clients are expected to remove their caches and links to the resource. The HTTP specification intends this status code to be used for “limited-time, promotional services”. APIs should not feel compelled to indicate resources that have been deleted with this status code. This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived. This error could indicate that a web host is blocking our servers from accessing the URL.
- If you determine that the URL (s) should not be archived, disable them.
- If the URLs do exist or you believe the URLs should exist, report the URLs to your web host. Please ensure your web host allows the following IP addresses:
- 52.23.29.34,
- 54.235.88.205
- 54.84.64.101
- Re-enable the URLs.
429 Too Many Requests
Description: Indicates the user has sent too many requests in a given amount of time ("rate limiting"). This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived.
- If you determine that the URL (s) should not be archived, disable them.
- Reach out to our support team to get more information on the status of your URL(s).
500 Internal Server Error
Description: Indicates that the server encountered an unexpected condition that prevented it from fulfilling the request. This error response is a generic catch-all response. Usually, this indicates the server cannot find a better 5xx error code to respond. Sometimes, server administrators log error responses like the 500 status code with more details about the request to prevent the error from happening again in the future. This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived. This error could indicate that the content for the URL no longer exists and therefore does not need to be archived.
- If you determine that the URL (s) should not be archived, disable them.
- If the URLs do exist or you believe the URLs should exist, report the URLs to your web host.
502 Bad Gateway
Description: Indicates that the server, while acting as a gateway or proxy, received an invalid response from the upstream server. This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived. This error could indicate that the content for the URL no longer exists and therefore does not need to be archived.
- If you determine that the URL (s) should not be archived, disable them.
- If the URLs do exist or you believe the URLs should exist, report the URLs to your web host.
503 Service Unavailable
Description: The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This response should be used for temporary conditions and the Retry-After: HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care of the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached. This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived. This error could indicate that a web host is blocking our servers from accessing the URL.
- If you determine that the URL (s) should not be archived, disable them.
- If the URLs do exist or you believe the URLs should exist, report the URLs to your web host. Please ensure your web host allows the following IP addresses:
- 52.23.29.34
- 54.235.88.205
- 54.84.64.101
- Re-enable the URLs.
504 Gateway Timeout
Description: Indicates that the server, while acting as a gateway or proxy, did not get a response in time from the upstream server that it needed in order to complete the request. This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived. This error could indicate that the content for the URL no longer exists and therefore does not need to be archived.
- If you determine that the URL (s) should not be archived, disable them.
- If the URLs do exist or you believe the URLs should exist, report the URLs to your web host.
508 Loop Detected
Description: It indicates that the server terminated an operation because it encountered an infinite loop while processing a request with "Depth: infinity". This status indicates that the entire operation failed. This response code is probably the most famous one due to its frequent occurrence on the web. (Source: MDN Web Docs)
Recommended Actions
- Confirm that these URLs should be archived. This error could indicate that the content for the URL no longer exists and therefore does not need to be archived.
- If you determine that the URL (s) should not be archived, disable them.
- If the URLs do exist or you believe the URLs should exist, report the URLs to your web host.
Comments
Let us know what was helpful or not helpful about the article.0 comments
Please sign in to leave a comment.