Chapter 8 of 8

When something isn’t working

The most common issues with signing up, checks, alerts, and connecting the plugin.

For all users

The verification email didn’t arrive

Check the address and your spam folder. If the app offers to resend it, do so and open the newest message. If you reach the limit, wait until the time shown on the screen. A message that was sent successfully isn’t yet confirmation that it was delivered to the inbox.

The website is added, but the chart is empty

Check the status and the time of the last check. The first history is still being collected. For blocked, paused, or out-of-date checks, open the reason in the details; a gap in the chart alone doesn’t confirm an outage.

No alert arrived

Check that the event actually led to a confirmed incident or alert.
Check that the alert contact is turned on and verified, and that it’s assigned to the website.
Look at quiet hours and scheduled maintenance.
Run Test for the alert contact, check the Alert delivery section in Settings → Alerts and delivery (visible to the account owner), and the target inbox including spam.

The WordPress agent isn’t communicating

Check that the plugin is activated, the website address is correct, and the connection code is saved. Read the details of the last error. Only renew the token when you need to replace it; replacing the token won’t fix a blanket block on communication. The full procedure is in the Connecting WordPress chapter.

The hosting blocks digiWatcher’s checks

An outage cause can end with “Another monitoring location can see the site — the hosting or a firewall is probably blocking digiWatcher’s address.” This means at least one monitoring location opened the website and the others couldn’t reach it while establishing the connection. The website is most likely up for people, and the hosting or a firewall is rejecting checks from digiWatcher’s address. This concerns the uptime check, not the WordPress agent. Two locations confirmed the outage, so it is still reported; the addition shows its likely cause.

Ask your hosting to allow digiWatcher’s addresses. digiWatcher checks over IPv4 only:

main server: 187.126.9.178
Sofia location: 217.217.234.185
Los Angeles location: 45.59.102.204

Some hosting providers only unblock an address and don’t offer a permanent allowlist; the block may then happen again.

I need help from a person

Use Contact support in the app if that option is available. Otherwise, contact your account owner or the digiWatcher provider using the contact details on the digiWatcher website.

Include the address of the affected website, when the problem happened, and what you were trying to do.
Attach the exact wording of the message and a screenshot without sensitive data.
Don’t send passwords, tokens, connection codes, or backup login codes.