Solid Central plugin review and common issues

Solid Central connects to sites via the Solid Central Worker plugin installed on each managed site. Verify: (1) the Solid Central Worker plugin is installed and active on the child site; (2) the site URL in the Solid Central dashboard exactly matches the site’s actual URL (including https://); (3) a firewall or security plugin on the child site may be blocking Solid Central’s servers — whitelist SolidWP’s server IP range; (4) from the child site’s Solid Central Worker settings, verify the connection key matches the dashboard entry; (5) re-sync from the child site by clicking “Sync Now” in the Solid Central Worker plugin settings.

Solid Central syncs data from connected sites on a schedule. To force an immediate refresh: (1) in Solid Central dashboard, select the site and click “Sync” or “Refresh Data”; (2) from the child site itself, open the Solid Central Worker plugin and trigger a manual sync; (3) verify the child site’s WordPress installation can reach SolidWP’s sync endpoint — outbound HTTPS requests to central.solidwp.com must be allowed; (4) the plugin update data on WordPress.org takes 12-24 hours to propagate after a new version release — the plugin may genuinely be up to date.

Uptime monitoring false positives typically occur when: (1) the monitoring check hits a temporarily slow server response — increase the monitoring check timeout threshold; (2) the monitoring check is blocked by a rate-limiting rule that treats repeated automated requests as suspicious — whitelist Solid Central’s monitoring IP range in your firewall; (3) the site uses maintenance mode during updates — configure Solid Central to pause monitoring during scheduled maintenance windows; (4) check if the false-positive sites share a hosting environment — a host-level intermittent issue may affect specific sites.

In the Solid Central dashboard, go to the Updates section. View all pending updates across all connected sites in one consolidated list. Filter by update type (plugins, themes, WordPress core) or by specific sites. Select the updates you want to apply — you can select all updates for one plugin across all sites, or all updates for one site. Click “Update Selected.” Solid Central coordinates the updates to connected sites sequentially or in parallel based on your configuration. Review the update results for each site after completion.

In Solid Central → Reports → Generate Report, select the site and reporting period. Configure the report contents: updates applied (plugins, themes, core), uptime statistics, security events from Solid Security, backup activity from Solid Backups. Add your agency branding (logo, name, contact) in Reports → Settings. Click Generate to create a PDF report. Schedule automatic monthly reports in Reports → Scheduled to deliver client reports automatically at the configured frequency without manual generation.

Solid Central is better for agencies already using Solid Security and Solid Backups who want unified SolidWP ecosystem management. MainWP is better for agencies prioritizing data privacy (self-hosted), managing very large site counts where flat-rate pricing is more economical, or those who need MainWP’s broader extension ecosystem. Solid Central’s cloud-based simplicity reduces infrastructure overhead but at the cost of data control. Both have robust core features — the choice depends primarily on existing tool ecosystem and data privacy preferences.

Yes — Solid Central manages WordPress sites on any hosting provider, not just SolidWP-affiliated hosting. The Solid Central Worker plugin creates the connection regardless of where the site is hosted. This means you can centrally manage sites distributed across different hosts (WP Engine, Kinsta, SiteGround, shared hosting) from a single Solid Central dashboard.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.