Title: NexraOne Agent
Author: Solgeo Corp.
Published: <strong>2026-05-25</strong>
Last modified: 2026-08-28

---

Szukaj wtyczek

![](https://ps.w.org/nexraone-agent/assets/banner-772x250.png?rev=3546789)

![](https://ps.w.org/nexraone-agent/assets/icon-256x256.png?rev=3546789)

# NexraOne Agent

 Autor: [Solgeo Corp.](https://profiles.wordpress.org/solgeo3960/)

[Pobierz](https://downloads.wordpress.org/plugin/nexraone-agent.0.4.16.zip)

 * [Szczegóły](https://pl.wordpress.org/plugins/nexraone-agent/#description)
 * [Recenzje](https://pl.wordpress.org/plugins/nexraone-agent/#reviews)
 *  [Instalacja](https://pl.wordpress.org/plugins/nexraone-agent/#installation)
 * [Rozwój](https://pl.wordpress.org/plugins/nexraone-agent/#developers)

 [Wsparcie](https://wordpress.org/support/plugin/nexraone-agent/)

## Opis

NexraOne Agent is a **connector plugin** for [NexraOne](https://nexraone.app/) —
a hosted monitoring and operations service. After you connect this site to your 
NexraOne account, the plugin sends periodic heartbeats and optional telemetry so
you can monitor cron health, email delivery, fatal errors, and login-related events
from the NexraOne dashboard.

#### Service & legal

This plugin is the official WordPress connector for NexraOne, operated by Solgeo
Inc. (https://solgeo.co.jp/).

 * **Service website:** https://nexraone.app/
 * **Plugin page & support:** https://nexraone.app/support/
 * **Terms of use:** https://nexraone.app/terms
 * **Privacy policy:** https://nexraone.app/privacy

You are responsible for ensuring that use of NexraOne complies with your own policies
and applicable law.

#### Data & privacy (summary)

By connecting the plugin (pairing or manual connect token), you authorize this site
to communicate with NexraOne servers. Depending on configuration and events, data
sent may include (without limitation): site URL, site title, WordPress environment
type, WordPress and PHP versions, plugin and theme inventory, disk usage summaries,
cron heartbeat timestamps, login failure counts, fatal error metadata (including
file paths and message excerpts), and the administrator email address used during
connection. See the privacy policy linked above for how NexraOne processes data.

#### Remote updates (disabled by default)

When connected, NexraOne may instruct this plugin to run **WordPress core, plugin,
or theme updates** using WordPress’s built-in updaters (downloads from WordPress.
org or official theme/plugin sources as configured on the site), but only if a site
administrator explicitly enables remote updates in the plugin settings.

Remote updates are disabled by default. When enabled, commands are issued from the
NexraOne account that is paired to this site. The plugin does **not** show an extra
on-site confirmation prompt before executing queued update commands received from
the service.

If you use this feature, ensure that only trusted administrators can pair/disconnect
the site and that your team’s change-management policy allows service-driven maintenance
actions.

#### Open source

Plugin source is GPLv2 (or later), consistent with WordPress. Third-party service
APIs are governed by NexraOne’s terms.

### External services

This plugin connects to the NexraOne API (https://api.nexraone.app) to provide site
monitoring and management functionality. This service is operated by Solgeo Inc.(
https://solgeo.co.jp/).

**What the service is and what it is used for:**
 NexraOne is a hosted monitoring
and operations service. This plugin acts as the connector between your WordPress
site and the NexraOne dashboard, enabling heartbeat monitoring, cron health checks,
login event tracking, fatal error reporting, and remote update execution.

**What data is sent and when:**

 * _During pairing/connection:_ site URL, site title, WordPress version, PHP version,
   and the administrator email address used to initiate the connection.
 * _Periodic heartbeats (when connected):_ site URL, WordPress environment type,
   WordPress and PHP versions, plugin and theme inventory (names and versions), 
   disk usage summary, cron heartbeat timestamps, login failure counts, lightweight
   WordPress configuration diagnostics, and fatal error metadata (file paths and
   message excerpts).
 * Data is only transmitted after the site administrator has actively connected 
   the site to a NexraOne account via the plugin settings page.

**Service provider:** NexraOne, operated by Solgeo Inc.

 * Service website: https://nexraone.app/
 * Terms of use: https://nexraone.app/terms
 * Privacy policy: https://nexraone.app/privacy

## Instalacja

 1. Upload the plugin folder to `wp-content/plugins/` or install the zip from the WordPress
    admin.
 2. Activate the plugin through the **Plugins** screen.
 3. Go to **Settings  NexraOne** and complete pairing or enter a connect token from
    your NexraOne dashboard.

## Najczęściej zadawane pytania

### Does this plugin work without a NexraOne account?

No. It is a connector for the NexraOne service.

### Where can I change the API or app URL?

Advanced users can define `NEXRAONE_DEFAULT_API_BASE_URL` and `NEXRAONE_DEFAULT_WEB_BASE_URL`
in `wp-config.php` (see the main plugin file for details).

## Recenzje

Wtyczka nie ma jeszcze żadnej recenzji.

## Kontrybutorzy i deweloperzy

„NexraOne Agent” jest oprogramowaniem open source. Poniższe osoby miały wkład w 
rozwój wtyczki.

Zaangażowani

 *   [ Solgeo Corp. ](https://profiles.wordpress.org/solgeo3960/)

Wtyczka „NexraOne Agent” została przetłumaczona na 1 język. Podziękuj [tłumaczom](https://translate.wordpress.org/projects/wp-plugins/nexraone-agent/contributors)
za ich wkład.

[Przetłumacz wtyczkę “NexraOne Agent” na swój język.](https://translate.wordpress.org/projects/wp-plugins/nexraone-agent)

### Interesuje cię rozwój wtyczki?

[Przeglądaj kod](https://plugins.trac.wordpress.org/browser/nexraone-agent/), sprawdź
[repozytorium SVN](https://plugins.svn.wordpress.org/nexraone-agent/) lub czytaj
[dziennik rozwoju](https://plugins.trac.wordpress.org/log/nexraone-agent/) przez
[RSS](https://plugins.trac.wordpress.org/log/nexraone-agent/?limit=100&mode=stop_on_copy&format=rss).

## Rejestr zmian

#### 0.4.16

 * Fix: Safe Update core updates now read the target version from a new `coreTargetVersion`
   field sent by the server, instead of blindly applying the first available core
   update offer. This prevents an unintended core version from being installed when
   multiple update offers are present.
 * Fix: after a core update, the agent now re-reads the installed version directly
   from disk instead of relying on a stale in-memory value, so the reported „to 
   version” accurately reflects what was actually installed.
 * Fix: if the server-specified core version is not available as an update offer,
   the agent now skips the core update without rolling back the site (previously
   this case was not distinguished from a real update failure).

#### 0.4.15

 * Report the WordPress environment type so NexraOne can suggest the site’s operational
   environment.

#### 0.4.14

 * Report lightweight WordPress configuration diagnostics for search engine visibility,
   debug display, and file editor restriction constants.

#### 0.4.13

 * Fix: the agent no longer ignores the server’s „job already terminal” response
   while a Safe Update is running. If the update job has already finished, failed,
   or been cancelled on the NexraOne dashboard by the time the agent reports a step,
   the agent now stops before taking the next site-changing action (database backup,
   file backup, or plugin/theme/core update) instead of continuing to completion
   regardless.
 * A backup created but left unused because the job was stopped this way is now 
   removed automatically, unless a backup for the same job already existed beforehand(
   in which case it is always preserved) or at least one update had already started(
   backups are always kept once updates are underway, for manual recovery).

#### 0.4.12

 * Fix: `includes/class-db-version-parser.php` was missing from the 0.4.11 release
   package (not added to the SVN tag), causing a fatal error on activation. No code
   changes since 0.4.11; this release re-packages the same source correctly.

#### 0.4.11

 * Report the connected database product (MySQL / MariaDB) and version alongside
   the existing WordPress/PHP version reporting, so the NexraOne dashboard can display
   it on the site detail page.
 * MariaDB servers that report a legacy `5.5.5-` compatibility prefix (for old MySQL
   clients) are now correctly parsed to the actual MariaDB version instead of the
   meaningless prefix value.

#### 0.4.10

 * Report a disk usage acquisition status (available / unavailable / unreliable)
   alongside the existing free/total byte values, so the NexraOne dashboard can 
   distinguish „monitoring disabled”, „unable to retrieve”, and shared-hosting environments
   from an actual disk usage anomaly.
 * Fix: `disk_total_space()` returning a float `0` was not reliably detected as „
   unavailable” (strict `=== 0` comparison could miss it).
 * Fix: a disk info cache written by an older plugin version (without the new status
   field) could be served as-is for up to 5 minutes after updating; it is now detected
   and refreshed immediately.

#### 0.4.9

 * Detect Basic Auth / IP restriction / WAF blocking the WP-Cron loopback request
   immediately when a Safe Update command is received, instead of waiting for the
   15-minute timeout with no explanation.

#### 0.4.8

 * Clarify that checking „Allow remote update commands from NexraOne” does not perform
   an update by itself; it only permits NexraOne to run automated updates (e.g. 
   Safe Update) on your behalf.
 * Fix: the WordPress core version restore notice included in backup ZIPs was hardcoded
   in Japanese instead of using the plugin’s translation source strings.

#### 0.4.7

 * Fix: large backup downloads could be silently emptied by an active output buffer(
   e.g. from a caching/CDN plugin) hitting PHP’s memory limit while streaming through
   readfile(). Output buffers are now explicitly flushed before streaming a backup
   file.

#### 0.4.6

 * Report the WP REST API base URL (rest_url()) in heartbeats so backup download/
   rollback requests reach the site correctly even when the site address and WordPress
   address differ.
 * Add a link from the connected plugin settings screen to the site’s NexraOne dashboard.

#### 0.4.5

 * Fix: large database backups could time out and download as an empty file. The
   download handler now removes the PHP execution time limit, matching the backup/
   rollback handlers.
 * Report backup size (bytes) so the dashboard can warn when a backup is large enough
   that a browser download may be unreliable.

#### 0.4.4

 * Report the WordPress admin URL (admin_url()) in heartbeats so the dashboard can
   link to the correct admin path even when WordPress is installed in a subdirectory.

#### 0.4.3

 * Simplify the remote update setting description.

#### 0.4.2

 * Fix: Safe Update no longer rolls back when the file backup step itself fails 
   before any files were changed (previously showed a misleading „rolled back” message).

#### 0.4.1

 * Report the NexraOne settings URL so the dashboard can link directly to the site’s
   remote update setting.

#### 0.4.0

 * Report the „Remote updates” setting state to NexraOne so the dashboard can warn
   when Safe Update cannot run.
 * Add an admin notice when remote updates are disabled, since Safe Update (automatic
   and manual) will not run in that state.

#### 0.3.0

 * Add backup download/delete: securely download or delete Safe Update backups from
   the NexraOne dashboard.

#### 0.2.0

 * Add Safe Update: automated WordPress core, plugin, and theme updates with backup
   and auto-rollback on fatal error.
 * Add manual rollback UI: select backup and restore files and database from the
   NexraOne dashboard.
 * Fix theme update slug to use stylesheet slug instead of display name.
 * Fix copy_dir_overwrite to detect file copy failures instead of silently ignoring
   them.

#### 0.1.3

 * Add email delivery failure detection via wp_mail_failed hook (MAIL_FAIL event).
 * Fix mail_ok heartbeat flag to reflect actual transient state instead of hardcoded
   true.

#### 0.1.2

 * Require explicit opt-in before executing remote update commands from NexraOne.
 * Require HTTPS for API URLs saved through pairing or manual connection.
 * Make the setup notice dismissible per administrator.

#### 0.1.1

 * WordPress.org guidelines: readme (service, privacy, remote updates), text domain/
   i18n, renamed plugin constants, production API defaults, minor cleanup.

#### 0.1.0

 * Initial release.

## Meta

 *  Wersja **0.4.16**
 *  Ostatnia aktualizacja **7 dni temu**
 *  Włączone instalacje **40+**
 *  Wersja WordPressa ** 5.8 lub nowszej **
 *  Testowano do **7.1**
 *  Wersja PHP ** 7.4 lub nowszej **
 *  Języki
 * [English (US)](https://wordpress.org/plugins/nexraone-agent/) i [Japanese](https://ja.wordpress.org/plugins/nexraone-agent/).
 *  [Przetłumacz na swój język](https://translate.wordpress.org/projects/wp-plugins/nexraone-agent)
 * Tagi
 * [heartbeat](https://pl.wordpress.org/plugins/tags/heartbeat/)[monitoring](https://pl.wordpress.org/plugins/tags/monitoring/)
   [saas](https://pl.wordpress.org/plugins/tags/saas/)[security](https://pl.wordpress.org/plugins/tags/security/)
 *  [Widok zaawansowany](https://pl.wordpress.org/plugins/nexraone-agent/advanced/)

## Oceny

Nie przesłano jeszcze żadnych recenzji.

[Twoja opinia](https://wordpress.org/support/plugin/nexraone-agent/reviews/#new-post)

[Zobacz wszystkierecenzje.](https://wordpress.org/support/plugin/nexraone-agent/reviews/)

## Zaangażowani

 *   [ Solgeo Corp. ](https://profiles.wordpress.org/solgeo3960/)

## Wsparcie

Masz coś do dodania? Potrzebujesz pomocy?

 [Zobacz forum wsparcia](https://wordpress.org/support/plugin/nexraone-agent/)

## Złóż datek

Czy chcesz wesprzeć rozwój wtyczki?

 [ Wspomóż wtyczkę ](https://nexraone.app/)