digiWatcher — user manual

1. Confirm your account

1. After signing up, open the verification email from digiWatcher. If it hasn’t arrived, check your spam folder too.
2. Open the link and confirm your account with the password you entered when signing up.
3. Once verification succeeds, Overview opens. It’s empty for now—start with the Add your first website button.

2. Add your first website

1. Enter the full website address, for example https://example.com, and the name you want to see it under in the overview.
2. Choose the platform. For uptime checks alone, Other platform is enough, even if the site runs on WordPress. For WordPress data, choose WordPress if your plan includes it.
3. Continue with the wizard. For WordPress, connect the plugin as described in the next chapter. You can also finish connecting later in the website details.
4. Wait for the first result. “Connection verified” means digiWatcher actually received a response. For WordPress, this confirms the connection to the plugin; track the site’s uptime separately in the overview.

3. Test your alerts

Adding a website doesn’t by itself confirm that an outage alert will reach you.

1. In the sidebar, open More tools → Alert contacts.
2. Add an alert contact, complete email verification if required, and use Test.
3. In the website settings, check the selected alert contacts. If no specific alert contacts are selected, all enabled alert contacts on the account are used.

Where to find things

• Overview summarizes the status of your websites and the events that need attention.
• Websites is where you browse and manage the list. Click a website to open its details.
• In the details, you’ll find check history, incidents, site care, and settings. WordPress data appears once the agent is connected.
• Search in the top bar takes you to a website or page. On a phone, open the main navigation with the menu button.
• The bell in the top bar shows recent incidents. The circle with your initial next to it opens the account menu: My account, language, theme, and log out.

What each status means

• Up: the latest evaluation confirmed the site is available.
• Down: the outage has been confirmed. Open the incident and its details.
• Waiting for first check: there’s no first result yet. This isn’t a confirmed outage.
• Checks blocked: the check couldn’t get a result, for example because of the site’s protection. Review the reason shown.
• Data out of date: the latest result is too old for a reliable conclusion about the current status.
• Paused: checks are paused. Check the website settings or any account restrictions.

Uptime, response time, and history

Uptime shows what share of the monitored time the site had no confirmed outage. Response time is how long the response to a check took; it isn’t the time a browser needs to fully load the page.

A newly added website has a short history. A dash or a gap in the chart means missing data, not automatically 0% or 100%. When comparing numbers, make sure the period and the age of the checks are the same.

An alert about a certificate, domain, or slow response may need action even when the site is currently up.

Setting up an alert contact

1. In More tools → Alert contacts, choose Add alert contact and select a delivery method.
2. Fill in the details following the help for the chosen channel and save the alert contact.
3. For email, complete the required verification. While an alert contact is waiting for verification, it receives neither alerts nor tests.
4. Use Test and check delivery in the target inbox or app.
5. In each website’s settings, select the recipients. An empty selection means all enabled alert contacts on the account.

When an outage alert arrives

A single failed check doesn’t necessarily become an incident. digiWatcher confirms an outage with repeated checks; you set on the website how many must fail in a row. If the digiWatcher provider has enabled additional monitoring locations, a majority of them must confirm the outage, always at least two. A result that no one else has confirmed stays unconfirmed; follow its explanation.

1. Open Incidents or the details of the affected website. Read the time, cause, and current status.
2. Check the site and contact whoever manages it or the hosting provider, depending on the cause found. digiWatcher tracks the outage; monitoring alone doesn’t fix it.
3. Write a note on the resolution. Use a public note only for text meant for clients on the status page.
4. After recovery, check the end of the incident and any follow-up alert.

Quiet hours and scheduled maintenance

The account owner sets quiet hours in Settings → Alerts and delivery. They postpone alerts; checks and event logging continue. You can allow an exception for important websites.

Before planned work, set up a window in More tools → Maintenance and choose the right websites and time. When it ends, check their actual status.

What you’ll need

Administrator access to WordPress and a plan that includes the WordPress agent. Website uptime can be checked without the plugin too; data about plugins, themes, and health needs it connected.

Connecting step by step

1. In the Add website wizard, choose WordPress. For a website you’ve already added without the plugin, use the Connect WordPress button in its details; for a website with the plugin, you’ll find the data in its details under WordPress → Connection and environment.
2. Download digiWatcher Agent (formerly Hlídač Agent) with the button in the app. In WordPress, open Plugins → Add New Plugin → Upload Plugin, choose the downloaded ZIP, then install and activate it.
3. Copy the connection code for this website. In the WordPress admin, open Settings → digiWatcher Agent (formerly Hlídač Agent), paste it into the Code from digiWatcher field, and save. The agent code from the website details (WordPress → Connection and environment) goes into the same field.
4. Go back to digiWatcher and verify the connection. Wait for an actual response from the plugin and check when the data was last loaded.

When the plugin doesn’t respond

An old report isn’t proof of the current status. Always check how old the data is and the error from the last load.

• Check that the plugin is active and that you’re connecting the right website, including its address.
• Read the specific reason in the check details. Check that the code or token is saved.
• If a security plugin or the hosting blocks access, work with whoever manages the site to allow communication for digiWatcher Agent. Don’t turn off the site’s protection across the board.
• If the plugin or theme inventory is missing, check that it’s turned on in the digiWatcher Agent (formerly Hlídač Agent) settings and load the data again.

Before every update

• Make sure you have a current backup of the site and can restore it with your hosting or backup provider.
• Check that digiWatcher Agent is communicating and its data is up to date.
• Read any warnings and choose a suitable time for the work. For a sensitive site, test the change on a staging copy first.

How to do it in digiWatcher

The agent uses the updates that WordPress itself offers. digiWatcher isn’t meant for installing new plugins or editing their files. If the core details only show information about a new version, update directly in WordPress following the on-screen instructions.

1. Open Updates in the main navigation, or WordPress → Updates in the website details.
2. Choose the website and the offered update. Running updates must be allowed for that website; connecting the agent alone doesn’t confirm that every action can be performed.
3. Follow the allowed actions and the confirmation dialog. If an action isn’t available, first resolve the reason shown in the app.
4. When it finishes, check the job result, the site’s uptime, and important features, for example a form or an order. If something fails, assess the state first; don’t run another batch blindly.

Record the care you’ve done

In the website details, record the work done under History → Care history. Note what changed and with what result. Before sharing with a client, check the record’s visibility; internal notes are for your team only.

Creating client access

1. In the main navigation, open Clients and create new client access.
2. Select only the websites that client should see. Check the selection before saving.
3. Give the client the offered link for setting a password, or use the available sending option. The client sets their own password.
4. The client logs in to the client portal. They see the selected websites, shared site care, and reports; they can’t change your websites’ settings.

Preparing a report

Give the share link only to its intended recipient. If it should no longer be available, revoke it where sharing is managed.

1. Open Reports and choose the period you need.
2. Check uptime, incidents, and the monitored period. A new website has no data from before it was added.
3. For further processing, download the CSV. For the client, use the client report option and check its scope and preview before sharing.
4. To save the report as a PDF, open its print version and choose Save as PDF in the print dialog.

Public status page

In More tools → Status pages, the account owner selects the websites to show on a shared page. They can set password protection. Before publishing, open the resulting address and check the visible websites and the public incident notes.

Agency

Agency in the main navigation brings together your team’s work on outages and a record of the services you renew for clients.

1. Work queue shows incidents with their priority, work status, and assignee. Choose a status, search by website, client, or assignee, or turn on My incidents.
2. Open an incident. On the Resolution tab, you set the priority, work status, and assigned person; in Time you log minutes worked, in Communication internal messages, and in Changes a link to a change on the same website.
3. Service and license renewals come from the manual records in the website details (History → Services and licenses). You can show services before and after expiry, or those missing a date.
4. Below that, the account owner sees Economics: retainers from clients against costs for hosting, domains, and licenses, converted to a monthly amount, excluding VAT and without currency conversion.

Owner, operator, and client

What the app offers depends on your permissions and plan. If you’re missing an action you need for your work, contact your account owner.

• The account owner adds websites and manages alert contacts, team members, client access, and the subscription.
• Operators work with the overview, incidents, and other permitted tools. They don’t have access to account management or paid terms.
• Clients use a separate portal with the selected websites and shared data.

Login and personal settings

• In Settings → My account and security, check your profile and email. Confirm a new address with the link in the message.
• Use your own login details; don’t share passwords between team members.
• In security, set up the available two-factor authentication following the on-screen instructions. Store your backup codes in a safe place.
• If you lose your password, use Forgot password on the login page. If you don’t have access to the verified inbox, contact your account owner or support.

Plan and billing

The account owner finds the current plan, its validity, and the account’s limits in More tools → Subscription. Before a change, check the number of websites and users and whether the WordPress agent is available.

The terms and amount shown for your account when ordering are what count. This guide doesn’t list prices so that it stays useful after the offer changes.

If the app restricts checks or a feature because of the subscription, open the explanation next to the plan. Operators pass this on to the account owner.

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

1. Check that the event actually led to a confirmed incident or alert.
2. Check that the alert contact is turned on and verified, and that it’s assigned to the website.
3. Look at quiet hours and scheduled maintenance.
4. 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

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.