NexraOne Agent

NexraOne Agent connects your WordPress site to NexraOne for WordPress uptime monitoring and alerts. NexraOne checks the site's URL from outside WordPress, so a stopped site can still be detected when WordPress itself cannot send a heartbeat. If a check fails or returns an HTTP 5xx response, NexraOne records the failure and sends an email alert after the configured number of consecutive failures. You can also see when the site recovers. Install the Agent on each site to combine this external availability check with WordPress health data in one dashboard. As a WordPress monitoring and maintenance tool, NexraOne also shows alerts and pending plugin, theme, and core updates across the sites you manage. Check whether your WordPress site is up

• Check the registered site URL from NexraOne's servers at the interval set for that site (5 minutes by default)
• Detect connection failures and HTTP 5xx responses; HTTP 4xx responses are tracked separately because the server responded
• Set how many consecutive failed checks trigger a downtime alert (3 by default)
• Receive downtime and recovery notifications by email, and review the site's uptime history in NexraOne

The external uptime check runs from NexraOne, not from WP-Cron on the monitored site. A NexraOne account is required. External uptime monitoring can continue without the Agent; installing the Agent adds the internal WordPress checks described below. Manage multiple WordPress sites from one dashboard Install NexraOne Agent on each site you manage to view their status together. The NexraOne dashboard helps you find sites that need attention without opening every WordPress admin screen.

• View site status, health scores, WordPress versions, PHP versions, and pending updates
• Filter sites by status, category, WordPress version, PHP version, or installed plugin
• Track SSL certificate and domain expiry dates
• Review alerts and update history

Monitor WordPress from the inside After the site is connected, the plugin reports periodic heartbeats and configured events to NexraOne. Depending on the enabled checks, you can monitor:

• WP-Cron health
• Fatal errors
• Failed login activity and administrator account changes
• Email delivery failures reported by WordPress
• WordPress core, plugin, and theme versions
• Disk usage and basic WordPress configuration diagnostics

Alerts can be sent by email. Paid plans also support Slack, Chatwork, and webhook notifications. Update with a backup and post-update checks Safe Update can update WordPress core, plugins, and themes from the NexraOne dashboard. Before changing the site, it saves the database and files belonging to the update targets. It applies updates one at a time, then checks the home page and WordPress REST API from outside the site. If an update fails, NexraOne can attempt to restore the backup. The backup Safe Update keeps on the site is limited to the update targets and the database, and its checks do not cover site-specific flows such as forms, checkout, bookings, or member login. For a copy of the whole site outside your server, use the external backup described below. Remote update commands are disabled by default. A site administrator must explicitly enable them in the plugin settings before NexraOne can run an update. Back up the whole site to storage outside your server External backups send the database and the files in wp-content to storage you choose in NexraOne, so a copy survives even if the server itself is lost. This is optional and off by default.

• Choose your own S3-compatible storage (for example AWS S3, Cloudflare R2, Wasabi, Backblaze B2, or MinIO), or the storage NexraOne provides on Cloudflare R2
• Set how often files and the database are backed up and how many copies to keep, or run a backup by hand from the NexraOne dashboard
• Optionally send an external backup before each Safe Update. If it fails, the update does not start
• The backup is uploaded from your server straight to the storage, not through the NexraOne API, and wp-config.php is never included
• Restore the database and the files you choose from an external backup, started from the NexraOne dashboard. The backup is downloaded from the storage, checked, and prepared beside the live site; the site is switched over only at the end, and switched back automatically if it does not load afterwards. wp-config.php and this plugin's own folder are never replaced. Restoring needs both "Allow external backups" and remote updates to be turned on, and the administrator email address is notified when a restore starts

A site administrator must turn on "Allow external backups" on the plugin's settings page before anything is sent. Using your own storage is included in paid plans; NexraOne-provided storage is a paid add-on. See the NexraOne pricing page for current terms. Start with up to 3 sites free A NexraOne account is required. The Free plan supports monitoring for up to 3 sites, requires no credit card, and includes email alerts. Safe Update and additional notification channels require an eligible paid plan. Create a NexraOne account and connect your first site. Service and privacy NexraOne Agent is the official WordPress connector for NexraOne, operated by Solgeo Inc. The plugin does not transmit monitoring data until a site administrator connects the site to a NexraOne account. See the External services section below for the destination, timing, and types of data sent.

• Service website
• Support
• Terms of use
• Privacy policy

Plugin source is GPLv2 or later. Use of the hosted service is governed by the NexraOne terms.

0.7.0

• Support sites protected by HTTP Basic authentication, such as staging sites. When you register the Basic authentication user name and password for a site in the NexraOne dashboard, the plugin receives them and adds them to the requests WordPress sends to its own site (WP-Cron and the plugin's loopback requests), so scheduled events, heartbeats and Safe Update keep working. The credentials are sent only to the site's own address and redirects are not followed.
• REST requests to the plugin's own routes are no longer checked as application passwords, so a Basic authentication header does not block them.

0.6.0

• Add restoring from an external backup. When a restore is started from the NexraOne dashboard, the plugin downloads the database and the chosen files from your storage, checks each file against the backup's checksums, and imports the database into temporary tables and unpacks the files into a temporary folder. Nothing on the live site changes until everything is ready.
• The switch-over shows WordPress's maintenance message for a few seconds while the tables are renamed in one step and the files are moved folder by folder. The plugin then loads the home page and the login page; if either shows a fatal error, or the check from NexraOne fails, the site is switched back to how it was before the restore.
• NexraOne's own connection settings stay as they are on the site, so the site stays connected after a restore. wp-config.php, this plugin's folder, and the folders and file types left out of the backup are never replaced.
• Restoring needs both "Allow external backups" and remote updates to be allowed on the settings page. Turning either off, or disconnecting, cancels a restore that has not started switching over yet. The administrator email address is notified when a restore starts.
• Only statements written by this plugin's database export are imported; anything else stops the restore before the live site is touched.
• A restore starts within seconds instead of waiting for the next five-minute status report. NexraOne sends a signed request to a new endpoint (nexraone-agent/v1/wake) that only makes the plugin send its status report right away, at most once every 30 seconds; it accepts no instructions. The plugin also sends the report right away when its own backup before a restore finishes.
• If the site could not reach itself (loopback request) when it was last checked, the check is retried after an hour instead of a day, and every restore checks again, so a temporary failure no longer slows a restore down.

0.5.2

• External backups now check each archive right after it is written. A database file is decompressed again to the end and its size compared with the original, and a zip file is opened again with a consistency check and its file count compared. If a check fails, for example because the server ran out of disk space while writing, the file is made again instead of being sent.
• A file that disappears or cannot be read between choosing it and adding it to a zip is now listed among the files that were not backed up, instead of being left out without notice.
• When an administrator sends a test submission with form test mode, the result (which form, from which page, and whether the emails could be sent) is reported to the NexraOne dashboard, so you can show that forms were checked after an update. The test recipients and the submitted content are not sent. Visitors' submissions are not reported.

0.5.1

• Add external backups. When a site administrator turns on "Allow external backups" on the settings page (off by default), NexraOne can back up the database and the files in wp-content to the storage you chose in NexraOne. The backup runs in small steps so it works within the server's time limits, resumes after interruptions, and splits large sites into several files. If the backup destination changes after you allowed it, nothing is sent until an administrator approves the new destination, and the administrator email address is notified.
• Add an optional external backup before Safe Update. When it is turned on for a Safe Update in NexraOne and external backups are allowed, the full backup is sent to your storage first, then the rollback backup is made on the site and the updates start. If the external backup fails, the updates are not started. This needs no new permission beyond "Allow external backups".
• The database export leaves out NexraOne's own connection settings and transients, and wp-config.php is never included in a backup.
• The settings page can report the folder sizes under wp-content when NexraOne asks for them, so you can choose folders to exclude from backups.

0.5.0

• Add a form test mode for Contact Form 7, MW WP Form, WPForms, and Snow Monkey Forms. While test send is on for an administrator, a checkbox (ticked by default) next to the submit button sends that one submission, and its auto-reply, to the administrator's test recipients instead of the address set in the form. Visitors' submissions are not changed. If the checkbox is unticked, the form says the submission goes to the recipients set in the form.
• Test send is set for each administrator (off, 1 hour, 3 hours, 24 hours, or unlimited) with up to 5 test recipients each (the account's email address by default). Form test mode tells administrators when a form does not support test send.
• The settings page now has two tabs, Settings and Form test mode.
• Plugin update information now matches what the WordPress Plugins screen shows. The update versions WordPress already knows about are included in the site status sent to the dashboard, so a newly released plugin version is detected even before the WordPress.org plugin information API reflects it.

0.4.27

• A fatal error that occurs while an update is being applied is no longer treated as an ongoing site error. It is still reported to the dashboard, marked as having happened during the update.
• Fix a "translation loading was triggered too early" notice that WordPress 6.7 and later wrote to the debug log on every page load.

0.4.26

• Safe Update now estimates the required free disk space more carefully: the database size is always included, and temporary space for downloading and unpacking update packages is reserved. When space is insufficient, the exact required and available amounts are reported to the dashboard.
• On servers where free disk space cannot be read, Safe Update continues as before and reports this to the dashboard so it can be shown in the update history.
• Free disk space is checked again after the database backup, before backing up plugin and theme files.

0.4.25

• Site-wide 404 error detection is now off by default. Enable it from the plugin's settings page ("404 error detection") if you want 404 errors to be recorded and surfaced in the dashboard.
• Improve how login-failure counts are written internally to reduce database load under heavy failed-login traffic. No change in behavior visible to users.

0.4.24

• Add passive detection of site-wide 404 errors (no registration needed) and display aggregated path/referrer data in the dashboard. No new alerts or notifications are generated.

0.4.23

• Explain external WordPress uptime monitoring, downtime alerts, and recovery in the WordPress.org listing. Plugin behavior is unchanged.

0.4.22

• Align the Japanese WordPress.org translation source with the WordPress Japanese translation style guide. Plugin behavior is unchanged.

0.4.21

• Rewrite the WordPress.org listing to explain multiple-site monitoring, WordPress maintenance, Safe Update, service requirements, and data handling more clearly.
• Add screenshot captions and expand the FAQ for installation decisions.
• Replace generic directory tags with tags that describe the plugin's current monitoring and maintenance functions.

0.4.20

• Fix a white-label-only update-cache path. This does not affect the official NexraOne Agent build. For older release notes, see the plugin's Development Log.