A check run is done, but some pages are marked as failed. Or the screenshot shows a password prompt, a “403 Forbidden” page or a “checking your browser” screen instead of your site. In most cases WebChange Detector is not broken: the server, a firewall or a protection service kept us out. This guide shows where to find out what happened and which setting fixes which cause.
A lot happens automatically before you ever see a failure. When a site blocks or slows us down, we try again on a different path, and we remember what worked for that website so the next run starts there. Bot checks that clear themselves after a few seconds are waited out. So when a page still fails, it usually needs a setting from you.
Step 1: Find Out What Failed
In the Web App
Two places tell you what went wrong: the run itself and the Logs tab.
- Checks tab: open the run. If pages failed, a Failed checks section sits at the top. Click it to see every failed page with its device and the error message.
- Logs tab: lists every screenshot of your account, including the ones still running, with the device, the page, the type of screenshot, the status (Open, Processing, Done or Failed) and when it was added and last changed. Use it to see whether something is still in progress or really stuck.
In the plugin for WordPress
- While an On-Demand Check runs: a Failed tile appears next to the progress counters as soon as a page fails. Click it to open Failed Items with the error for each page.
- WebChange Detector → Logs → Queue: every screenshot with its page, whether it belongs to Monitoring or On-Demand Checks, its type, its status and its times. Finished screenshots have a Show button.
- Debug Logs: for deeper digging, switch on Enable Debug Logging under WebChange Detector → Settings. The entries appear in the Debug Logs tab of the Logs page and can be exported with Export to CSV. Older entries are cleaned up automatically after 30 days. Switch it off again when you are done.
In MainWP
- Checks tab of the add-on: a run with pages that could not be captured carries a Failed label with the number of failed screenshots.
- The reason: the add-on does not show the error message. Log in to the Web App with the same account, where your MainWP sites are listed and marked MainWP. Open the run on the Checks tab and click Failed checks, as described above.
Monitoring alert emails also list failed pages under Failed URLs, so you hear about a failing page without opening anything.
Step 2: Read the Reason
The error message is either an HTTP status from your server or the browser’s own error code. The most common ones:
| You see | What it usually means | Fix |
|---|---|---|
| HTTP 401, or a password prompt in the screenshot | The site is protected by a server password, typical for staging | Basic Authentication |
| HTTP 403, or a firewall or “verify you are human” page | A firewall or security plugin blocks unknown visitors | Static IP Proxy, then allow that IP in the firewall |
| HTTP 429, or failures only when many pages run at once | The server limits how many requests it answers | Increase the screenshot delay |
| net::ERR_NAME_NOT_RESOLVED | The domain cannot be found: a typo, an expired domain or a DNS problem | Check the address of the page |
| net::ERR_CONNECTION_REFUSED or a timeout | The server is down or refuses the connection | Check the server; if it works for you, check the firewall |
| Unsupported content type, or unsupported file extension | The address is a file, like a PDF or an image, not a web page | Remove that address from your checks |
Error pages such as a 404 or a server error usually still give you a screenshot, with the error reason attached. That way you see exactly what a visitor would have seen.
Fix: A Staging or Password-Protected Site (Basic Authentication)
Made for: staging sites and other pages behind a server password, the kind where the browser asks for a username and password before anything loads. It does not log into a WordPress login form or a members area that uses its own login page.
- Web App: Monitoring or On-Demand tab → ⋯ on the website → Website Settings → Advanced Settings → Basic Authentication. Enter Username and Password and click Save.
- plugin for WordPress: WebChange Detector → Monitoring or On-Demand Checks → Basic Authentication, then Save Settings.
- MainWP: the Settings tab of the add-on → Settings next to the site → Advanced settings → Basic Auth username and Basic Auth password, then Save settings.
The credentials apply to both Monitoring and On-Demand Checks of that website. The password is stored encrypted and never shown again; to remove it, clear the field and save.
Fix: A Firewall Blocks Us (Static IP Proxy)
Made for: hosting firewalls, security plugins and protection rules that only let in known IP addresses. With the static IP proxy switched on, all screenshots of that website come from one fixed IP address, which you can add to the allowlist.
- Open the settings as above: Website Settings → Advanced Settings → Proxy Configuration in the dashboard, or Static IP Proxy on the Monitoring or On-Demand Checks page in the plugin.
- Switch on Enable Static IP Proxy and save.
- Copy the IP address shown next to the switch and add it to the allowlist of your firewall, security plugin or hosting panel.
In MainWP the switch is called Use static IP proxy: the Settings tab of the add-on → Settings next to the site → Advanced settings, then Save settings. The add-on does not show the IP address. Copy it from the Website Settings of the same site in the Web App, where your MainWP sites are listed too.
Step-by-step guides for common firewalls are in How to Stop Firewalls From Blocking Your Screenshots.
Fix: Wrong Language, Currency or Banner (Screenshot Region)
Made for: sites that show different content depending on where the visitor comes from, like a different language, currency or consent banner for Europe. If the screenshot shows the version your customers do not see, set the region.
Find Screenshot Region in the dashboard’s Website Settings or on the plugin’s Monitoring and On-Demand Checks pages. Auto-detect picks the closest region for the site and then locks it to US or Europe. Choose United States or Europe to set it yourself. Monitoring and On-Demand Checks of a website always share one region. In MainWP it is Screenshot region in the On-Demand check settings of the site.
Fix: The Server Struggles When Many Pages Run (Screenshot Delay)
Made for: hosting that limits requests or slows down when many pages of the same site are captured one after another. The screenshot delay sets how many seconds pass between the start of one screenshot and the next on your site. The default is 10 seconds; raise it step by step.
Find it under Website Settings → Advanced Settings → Screenshot Timing in the dashboard, or as Screenshot Delay on the plugin’s Monitoring and On-Demand Checks pages. In MainWP it is Screenshot delay (seconds) under Advanced settings of the site.
Pages That Keep Failing Are Switched Off Automatically
If a page fails again and again in a row, WebChange Detector switches its checks off, so you do not keep spending checks on a page that is broken or no longer exists. You get an email with the subject “URL(s) Disabled After Multiple Failures” that lists the affected pages.
Fix the cause first, using the steps above. Then switch the page back on: turn on Desktop and Mobile again for that page in the website’s page list in the dashboard, or in the page selection on the plugin’s Monitoring or On-Demand Checks page. If the page was removed for good, leave it off.