QryptoPay health monitoring
The BeAdmin cloud can monitor whether your QryptoPay server is working correctly. If the server goes down, it usually can't report that itself — but the cloud will notice: it shows the status with an outage history in your cloud account, and emails you both when there's an outage and when service is restored.
ℹ️ Why this matters
An outage on your QryptoPay server also goes unnoticed for payments: customers simply won't be able to pay, and you won't know unless you check yourself. Monitoring reports the problem almost right away — you get a chance to react before customers notice.
How it works
When you connect the option on your QryptoPay server, you choose which merchants to watch. From there the cloud checks the server on its own, with no input from you: the server, the panel, the module itself, and merchants' payment pages — every minute, payment processing — every 2 minutes. You can't change how often it checks, but you can choose what it reacts to and how fast it reports a problem (see below).
Monitoring can detect the following:
- the server is unreachable;
- the panel isn't responding;
- internal services of the QryptoPay module have failed;
- a merchant's payment page isn't working;
- payment processing issues — more on this in the next section.
A check can fail in different ways: the server may not have answered at all (usually a network problem), or it may have answered with an error. Monitoring tells these cases apart, but it doesn't raise the alarm over a single failed check — the status only switches to "Down" once the problem is confirmed.
If failed checks become noticeably more frequent but haven't turned into a full outage yet, the cloud shows an intermediate "Unstable" status. You set the threshold for this yourself, in the sensitivity settings.
A service doesn't leave "Down" after just one successful check either — the cloud first makes sure the server is reliably responding again, and only then sends a recovery email. That way you won't get a false "all clear" in the middle of ongoing problems.
Each service in your cloud account shows a strip with its recent check history — hover over any square (or move keyboard focus to it) to see the result of that particular check.
Because of these delays, the status shown in your cloud account can lag slightly behind reality, and the "Check now" button in your cloud account lets you send a check manually, ahead of schedule. This is handy if you've already restored the server and don't want to wait for the next scheduled check to confirm everything's working.
If you turn monitoring off or its licence expires, the outage history isn't lost — it stays available in your cloud account. It's kept for 90 days, then deleted.
If payment processing is having trouble
In your cloud account, payment processing can show the "Scanner catching up" status. Usually this is not a failure: payment processing is catching up on what it missed, and new payments confirm with a delay in the meantime — no action needed. If the gap is not shrinking, your cloud account and the email will suggest contacting support.
In other situations your cloud account and the email will tell you what to do — for example:
- Payment processing has stalled: new payments aren't being confirmed. Restart the module in the panel, and if that doesn't help, contact support.
- The node isn't returning fresh blocks: check the node in the module settings, or temporarily switch to a public one.
💡 Monero: when the public node doesn't help
For Monero, the module settings hold the address of the network node — start there. But if fresh blocks still don't arrive after switching to the public node, the cause isn't in the settings: restart the module in the panel, and if that doesn't help, contact support.
Sensitivity and notifications
Both in the panel and in your cloud account — on the same settings page — you can set parameters that apply to the whole server:
- Sensitivity — how noticeable the rise in outages needs to be before the cloud shows an "Unstable" status: "High" (10%), "Medium" (20%, default), or "Low" (40%). The higher the sensitivity, the sooner you'll hear about a problem, but also the more often you'll get notified about less serious hiccups.
- Notification category — whether to get emails only about outages, or also about unstable service.
💡 Which sensitivity to pick
Watch it for a week or two and decide which option suits you. As a rule, the more payments you process per day, the higher you should set the sensitivity — missing a problem costs more than reading one extra notification about it.
You can set up these parameters in the panel — QryptoPay → "Settings" → "Monitoring" → "Probe settings" — or in your cloud account, on the server page, "Monitoring" tab. The value is shared: a change in one place shows up in the other right away.
Notifications
An email arrives by the following rules:
- about an outage — we tell you right away;
- one-off blips don't trigger anything — only sustained problems do;
- if a problem drags on, you'll get an occasional status-update email;
- about recovery — we always tell you, including partial recovery: if some services are back and others aren't yet, the email lists both.
⚠️ Don't confuse this with other notifications
Licence-expiry notifications are sent separately — monitoring isn't involved there, though the licence expiry date is visible both on the monitoring page in your cloud account and in the corresponding module settings section on the server.
An outage notification goes to the email address of the cloud account owner whose licence covers monitoring. That address can differ from the one set up in the module's own notifications (see Set up email notifications in QryptoPay).
You won't get a notification in the following cases:
- during a scheduled panel update;
- if the merchant's payment page is intentionally disabled or the merchant itself is excluded from checks;
- if the module doesn't have any networks configured for accepting payments yet;
- if you've turned monitoring off yourself.
How to connect monitoring
Monitoring is a paid licence option. It's purchased separately for each server, but within that server you can monitor several merchants at once (for how to add a licence option, see How to get a licence).
💡 The option stays paid for
Turning monitoring off stops the checks themselves, but it doesn't cancel the licence option you bought — it stays active and paid for until the end of its term.
You can add monitoring to your licence in one of these ways:
- in your cloud account — on the server page, "Monitoring" tab;
- in the panel — QryptoPay → "Settings" → "Monitoring".
After paying for the licence, go to QryptoPay → "Settings" → "Monitoring" on the server, check that monitoring is turned on, select the merchants you want to watch, and set the sensitivity and notification category to your liking.