There may be various reasons why a page fails to open. This guide describes the most common problems and suggests solutions to help you overcome these issues.
Timeout
A timeout occurs when the page takes too long to respond. This may be a temporary issue with the page, or the page may be loading very slowly. Timeout limits vary depending on your plan:
- Free plan: 45 seconds
- Standard plan: 90 seconds
- Enterprise plan: 180 seconds
- Ultimate plan: 180 seconds
To avoid timeouts please consider subscribing to a paid plan or upgrading your plan.
Selector not found
This error will be shown if the page has changed significantly and element with configured XPath/CSS selector could not be found. In this case, you should review the page and update selector if needed.
Page blocked
For business monitoring, we recommend Enterprise or Ultimate and their included managed Residential connection options. For personal monitoring on a budget, try PageCrawl Relay if the public page opens through your own connection but fails in PageCrawl. Relay requires a computer you keep online.
Relay has no PageCrawl fee on any plan, including Free. You supply the bandwidth, and your normal monitoring limits still apply.
Relay does not provide access to private intranets or local-network pages, and it does not reuse your browser's signed-in session. Check these common causes before choosing a connection:
Access Restricted to Specific Countries Page may be configured to only allow visitors from a specific country.
- Solution: Try an included Location in a country the site accepts. For personal monitoring, Relay may help if your own computer is in that country. If neither option covers it, consider Web Unblocker on Enterprise or Ultimate, or custom proxy pools from your own provider.
Proxy Location blocked The website may block the IP address of the proxy server PageCrawl is using.
- Solution: For business monitoring, try the Residential locations included with Enterprise or Ultimate at no extra cost. For personal monitoring, try Relay if the page works through your own connection. Web Unblocker is a separate option on those plans that uses paid bandwidth. No connection option guarantees access to every site; contact support before buying traffic if you are unsure.
401 or 403 Error
A 401 usually means the website requires authentication. A 403 means access was refused, which can involve account permissions or site protection. Check whether the page opens in a private browser window without signing in. Changing the connection does not provide a login or grant access to a restricted account.
If the page requires sign-in, follow the website login guide for paid plans and check that the account can access the page. Relay does not copy your browser's login session. For a public page that fails to load, we recommend Enterprise or Ultimate's included connection options for business monitoring. For personal monitoring, PageCrawl Relay may help if the page works through your connection. See Monitoring Pages Behind Bot Protection for the next steps.
404 Page Not Found
In most cases this error indicates that page is no longer available to view. You should check and update the page URL.
500 Series error
500, 502, 503, 504 indicates that website server is not responsive, overloaded, currently in maintenance or experiencing server issues. If such error occurs, our bots will retry page check later.
Page Unreachable
The page can't be opened. In most cases website is down or the website in only reachable from a specific country
Site Protected with CAPTCHA
A CAPTCHA is a website challenge, and changing Location or using Relay does not guarantee it will disappear. First check the captured page to confirm what the site is asking for. PageCrawl offers a separate CAPTCHA integration on Enterprise and Ultimate; it needs its own setup.
See Monitoring Pages That Show CAPTCHA for the integration and its separate provider charges. Contact support if you are unsure whether the page shows a CAPTCHA or another type of access restriction.
Unknown Error
In some cases there could be an unexpected error that causes the PageCrawl bot to fail to check the page for changes. In case this error does not go away after a while, please contact support to notify us about the problem so we could prioritize the issue.