WordPress
Launch a managed WordPress site with private MySQL and persistent site content.
WordPress#
Choose WordPress when you want NexHost to run the WordPress application for you. The service creates a public WordPress container, a private MySQL database, and persistent storage for wp-content. Uploads, themes, and plugins therefore remain when the WordPress container is replaced during a restart or deployment.
What NexHost creates#
- A maintained WordPress Apache image with automatic listener discovery and isolated public ingress.
- A dedicated MySQL database on the service's private workspace network.
- Generated database credentials and WordPress security keys. These values are encrypted by the control plane and are not displayed in deployment logs.
- A persistent Docker volume mounted at
wp-contentfor customer-managed uploads, themes, and plugins.
NexHost assigns the external route. There is no customer-facing port field and no user-configured health-check URL: the worker confirms that the container has opened a reachable TCP listener before the release is activated.
First launch#
- In New Project, choose WordPress.
- Give the site a stable name and choose the region and instance profile.
- Review the managed MySQL and persistent content settings, then deploy.
- Open the generated platform URL and complete WordPress's first-run administrator setup.
- Attach a verified custom domain from the service's Domains settings when the site is ready.
The first browser visit completes WordPress's normal installer. Keep the administrator account and password in your own password manager; NexHost does not create or retain the WordPress administrator password.
What is deliberately not promised yet#
This first managed WordPress service does not include automatic WordPress updates, scheduled database backups, staging environments, multisite management, or a NexHost plugin-management console. Configure WordPress, themes, and plugins through its administrator interface, and make an external, verified backup before any destructive content or database operation.
Operations#
- Restarting WordPress recreates the application container with the same private database and persistent
wp-contentstorage. - Suspending the service stops the WordPress and MySQL containers while retaining their managed volumes for recovery.
- Deleting the service removes its containers. Treat deletion as destructive and ensure you have a verified backup of any content you must keep.
Troubleshooting#
| Symptom | Likely cause | Fix |
|---|---|---|
| Deployment stops before WordPress starts | The selected worker cannot pull the maintained WordPress or MySQL image, or MySQL did not become ready | Open the deployment log and retry after the worker's network/image issue is resolved. Credentials are kept out of the log. |
| WordPress cannot reach the database | The managed MySQL container is stopped or its initial bootstrap failed | Restart the WordPress service. NexHost verifies and starts the managed MySQL resource before starting WordPress. |
| Uploads or themes are missing | The files were stored outside wp-content, or a previous deployment was created before persistent content storage was available | Store mutable WordPress files in wp-content and restore any needed content from a verified backup. |
Related documentation#
- Custom Domains — connect a production hostname after domain verification.
- Deployments — follow the managed provision log and release status.
- Logs — understand customer-safe deployment output.