How to host WordPress on your own server
WordPress runs well on a server you pay for. Zefily installs the PHP site and its database, updates every site with a snapshot taken first, and can clone a live site to staging. This guide covers the first install and the settings that keep it fast and safe.
Before you start
- A server connected to Zefily with a PHP web stack, or a starter stack such as High-traffic WooCommerce.
- A domain whose DNS record points to the server IP address, so the certificate can be issued.
- At least 1 GB of memory; the pre-flight check warns below that.
Steps
-
1. Connect the server
Add the server with the one-line installer and choose a PHP web stack, or the High-traffic WooCommerce starter stack, which adds a page cache and a Valkey object cache.
-
2. Point the domain at the server
Create an A record for your domain, and for www if you use it, pointing to the server IPv4 address. The certificate request needs the name to resolve to the server and port 80 to be open.
-
3. Open the WordPress page
In the main menu choose WordPress, then New WordPress site. Pick the server, enter the domain and keep HTTPS on.
-
4. Choose the language and a blueprint
Pick the language WordPress installs in. A blueprint lists wordpress.org plugins and a theme to install right after WordPress. A plugin that cannot be installed is reported, and the site still works.
-
5. Let Zefily finish the install
Zefily creates a PHP site on the newest installed PHP, a MariaDB database with its own user, installs the latest WordPress and requests the certificate. The site is ready when WordPress answers.
-
6. Sign in with a one-time link
On the site's WordPress pane, use Log in as admin. It opens wp-admin with a one-time link, so you never send a password. New installs start with four security filters on: no PHP in uploads, hidden sensitive files, blocked author scans and no file editing in wp-admin.
-
7. Turn on the cache
On the General pane, turn on the Page cache. Logged-in visitors, carts and checkouts skip it automatically. Turn on the Object cache too for the database queries WordPress repeats.
-
8. Add the site to a backup plan
Add the site and its database to a backup plan. Every update from the panel takes a snapshot first and restores it if the site stops answering.
Verify it works
Open https://your-domain: the site loads over HTTPS with a valid certificate. Open wp-admin with Log in as admin, then look at the WordPress page: the site is listed with its version and either No updates or a count of updates.
Troubleshooting
- The certificate is not issued
- The domain does not yet point to the server, or port 80 is closed. Fix the A record, wait for DNS to update, then retry the certificate on the site page.
- An update broke the site
- The panel restores the snapshot taken before the update when the site stops answering or shows a critical error. Check the site logs on its Logs pane before you update again.
- Visitors see PHP errors
- Turn Debug mode on under Settings, users and staging only while you investigate. It writes to a log in the site user's home folder, not to your pages. Turn it off afterwards.
Questions
Can WordPress run on a small VPS?
It needs at least 1 GB of memory. The pre-flight check blocks servers under 512 MB and warns under 1 GB.
Are updates applied automatically?
Minor core releases can be applied by WordPress itself. The WordPress page checks every site once a day and marks the updates; you start them from the panel, and each update takes a snapshot first.
Can I test an update before the live site gets it?
Yes. Clone the site to a staging copy, update and test it there, then push the changed files or tables back. Search engines are discouraged from the staging copy.
Read next
Start on a server you own
Create your account, connect a server and follow the guide. The server stays yours: you pay your provider.