Uptime monitoring for every site on your Plesk server
Install a small script once. Every ten minutes it reports your domains, and every site gets a monitor, added and removed as sites come and go. No Plesk password or API key ever leaves your server. One alert when a server dies, not one per site.
650,000 free checks every month. No card, no seats, no subscription.
Connect a Plesk server in three steps.
Paste the install commands
In PingWise, open Integrations → Connect Plesk. The page shows the commands once, with a key for that server. Run them as root: they write a config file readable by root only, the script (shown in full on the page) and a cron entry.
See what we found
The first report waits on the page as “Found on your-server: N sites”, with the monthly cost at each interval. Nothing is created yet.
Import and keep in sync
One click creates the monitors. From then on every report syncs: new sites start, suspended subscriptions pause, removed domains pause at once and are deleted after 24 hours.
Why a script and not an API key
A Plesk API key acts with the full rights of the administrator who created it, and Plesk has no read-only key. So we don’t ask for one.
- Read only, on your server. The script reads Plesk’s own list of domains with one
plesk dbquery and posts it to us over HTTPS. It changes nothing, and you can read every line before you install it. - A key for one server, kept as a hash. The key is shown once on the install page and sits in a root-only file on your server, never on a command line. We store only its hash. “New key and install commands” replaces it, and the old one stops working at once.
- Runs from cron, as root, under your control. The script runs every ten minutes. You review, install and remove it, and you keep the server’s key secret. No Plesk API key is ever created for us.
- Only what the sync needs. For each domain: its name, Plesk’s numeric id, its hosting type, its status (active, suspended or disabled) and the ids of its subscription and parent domain, plus the server’s hostname and the Plesk version. It sends no usernames, customer names or contact details, no paths, addresses, mail or database details, and does not read domain aliases.
- Easy to remove. Remove the cron entry, the script and its config file; the command is in the docs. That stops the sync; existing monitors stay until you delete them in PingWise.
- Written down. Our Privacy Policy, Terms and DPA describe this processing.
What the Plesk integration does for a server full of other people’s sites.
One alert per server
Monitors are grouped by server. When a server with eighty sites goes down you get one grouped alert, not eighty emails, and only after probes on three continents agree.
Main, additional and subdomains
Each domain with hosting gets an HTTPS monitor. Forwarding-only domains, aliases and wildcards are skipped, so nothing is checked twice.
Suspended means paused
A suspended or disabled subscription’s sites have their monitors paused, and resume when it is turned on again.
Mistakes don’t wipe history
A domain that disappears is paused at once and removed after 24 hours. If one report would pause or remove more than a fifth of a server’s sites, it changes nothing and the integration asks you to check.
Blocked, not down
A Cloudflare challenge on a customer’s site shows as “blocked”, a warning, not an outage. Our probe addresses are public, so you can let them through.
An account for each customer
Resellers can tick one box for one customer account per Plesk subscription, named after its main domain, under your brand: its own login, alerts and status page, only its sites. All of it uses your credits.
Quiet servers change nothing
If a server stops reporting, its monitors keep running as they are. After about 35 minutes without a report, the integration page tells you.
Confirmed before you’re paged
Every check runs from several cities, and a site is marked down only when two thirds of the probes, on three continents and three networks, agree twice in a row.
Per check, not per site or per seat.
One credit is one scheduled check of one monitor; confirmation rounds are free. Every account gets 650,000 credits a month for free, enough for about 75 sites every 5 minutes. Above that, you buy prepaid packs, valid 24 months.
Monthly figures use the rate of the credit pack a year of that usage would use up, before VAT. Hosting companies: see the launch offer.
Plesk monitoring: common questions
Does the script change anything on my server?
No. It only reads Plesk’s list of domains with one query and posts it. It is shown in full before you install it.
Which Plesk versions?
Plesk Obsidian on Linux, with root on the server. One connection per server; add one for each Plesk server.
What if the server stops reporting?
Nothing changes: the monitors keep running. After about 35 minutes without a report, the integration page tells you. A new key replaces the old one at once.
How do I remove it?
Remove the cron entry, the script and its config file; the command is in the docs. That stops the sync; existing monitors stay until you delete them in PingWise.
Do you read my customers’ details?
No. Only each domain’s name, Plesk id, hosting type and status, the ids of its subscription and parent domain, the server’s hostname and the Plesk version. No usernames or contact details, and aliases aren’t read.
Which other panels do you support?
Enhance and cPanel/WHM, see the Enhance and cPanel/WHM integrations. For any other panel, you can create monitors through the API or import a CSV.
Is PingWise affiliated with Plesk?
No. PingWise is an independent service. Plesk is a trademark of WebPros International GmbH, used here only to say what we connect to.
Monitor every site on your Plesk server.
Install once; nothing is created until you press Import. 650,000 free checks a month, no card.
Plesk is a trademark of WebPros International GmbH, used here only to identify the control panel. PingWise is not affiliated with or endorsed by WebPros.