iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
The most reliable way to run WordPress on OpenLiteSpeed is to start with a clean VPS using a supported operating-system image, point your domain to the server, then choose one of three deployment routes: install OpenLiteSpeed and LSPHP from the LiteSpeed repository, run the OpenLiteSpeed one-click script, or use the OpenLiteSpeed CLI. WordPress still needs a PHP runtime with its database extension and a MySQL-compatible database such as MariaDB.
Use the one-click or CLI route when you want a repeatable, bundled deployment. Use the repository route when you need tighter control over PHP, database, virtual-host, or security settings. The steps below cover DNS, ports, PHP and database checks, virtual-host mapping, HTTPS, browser setup, hardening, and recovery when a stage fails.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →
Choose a supported VPS operating system
Provision a new VPS rather than layering this installation onto an existing web stack. OpenLiteSpeed documentation lists Debian 11 through 13, Ubuntu 22, 24, and 26, and CentOS 8, 9, and 10, along with compatible derivatives. Treat that list as a support boundary: select an image that is still supported by your VPS provider and by the OpenLiteSpeed documentation on the day you deploy.
| Operating-system family | Documented releases | What to check before provisioning |
|---|---|---|
| Debian | 11, 12, 13 | Confirm the selected release is not at end of life and that the repository bootstrap supports it. |
| Ubuntu | 22, 24, 26 | Use the provider’s standard server image and verify the release is supported by the current OpenLiteSpeed packages. |
| CentOS | 8, 9, 10 | Check repository and package availability for the exact CentOS-compatible derivative you selected. |
Do not infer performance from the version number. The available LSPHP and MariaDB package choices are configuration options, not benchmark results.
Prepare DNS, ports, and a clean server
- Provision the VPS. Choose a supported image, a public IPv4 address, and IPv6 if you intend to publish an AAAA record. Log in with an administrative account that can use the distribution’s package manager and service manager.
- Point DNS to the VPS. Create an A record for the site name at the server’s IPv4 address. Add an AAAA record only when IPv6 is configured and reachable on the VPS. DNS changes may take time to propagate, so complete this step before requesting a certificate.
- Check the required ports. Ports 80 (HTTP), 443 (HTTPS), and 7080 (OpenLiteSpeed WebAdmin) must be available or deliberately handled by an existing firewall or service. The OpenLiteSpeed CLI specifically requires you to account for these ports before creating a site.
- Remove conflicting web stacks. A preinstalled Apache, Nginx, control-panel proxy, or another process listening on 80 or 443 can prevent OpenLiteSpeed from binding its listeners. Stop or reconfigure such services before installation.
- Record the domain and server address. You will use the exact fully qualified domain name when creating the virtual host, requesting ACME/Let’s Encrypt, and opening the WordPress installer.
Using the domain before DNS resolves to the VPS commonly causes certificate validation and browser tests to fail even when OpenLiteSpeed itself is configured correctly.
Pick the installation route
All three routes install the same essential layers: OpenLiteSpeed, an LSPHP runtime, a PHP database connector, and a MySQL-compatible database. They differ in how much configuration the installer performs for you.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Route | Repeatability | PHP and database control | Certificate automation | Security flags | Best fit |
|---|---|---|---|---|---|
| Repository/manual | High when scripted by you; every setting is explicit | Highest; select the available LSPHP version and connector packages yourself | You configure ACME or certificates in the virtual host | Enable OWASP rules, Fail2Ban, HSTS, reCAPTCHA, or namespace isolation individually | Administrators who need control over a clean VPS |
One-click with -W |
High for standard WordPress deployments | The script presents supported database and PHP choices | Available through the script’s ACME options | Script options expose OWASP, Fail2Ban, and related controls | Fast installation followed by browser-based WordPress setup |
One-click with --wordpressplus |
High for a named site | Bundled site configuration with the script’s supported choices | Available through the script’s ACME options | Security options can be selected during the run | A configured site that also enables LiteSpeed Cache |
| OpenLiteSpeed CLI | Very high for repeated site creation | Uses the CLI’s supported site and package options | --le requests Let’s Encrypt during site creation |
Use the CLI’s security flags where applicable, then review the result | Operators managing multiple clean VPS deployments |
For a first site, the one-click workflow is the shortest path. Choose the manual route when you must pin a particular PHP runtime, inspect every package, or build a custom virtual-host layout. Choose the CLI when you want a documented command that can be repeated for additional domains.
Route A: install from the repository and configure manually
1. Bootstrap the LiteSpeed repository
Run the repository bootstrap procedure documented for your exact Debian, Ubuntu, CentOS, or compatible derivative. The bootstrap adds the package source and signing configuration needed to install OpenLiteSpeed and LSPHP. Do not copy a command intended for a different distribution family; package names and package managers vary.
2. Install OpenLiteSpeed
Install the package named openlitespeed with the operating system’s package manager. After installation, use the distribution service manager to start OpenLiteSpeed and confirm that no other process has claimed ports 80, 443, or 7080.
3. Install LSPHP and its database connector
Select an LSPHP version that the repository exposes for your operating-system release. Install that runtime together with the matching MySQL connector package. WordPress cannot communicate with MariaDB or another MySQL-compatible server unless the selected PHP runtime has the required database extension.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Available LSPHP and MariaDB options are OS-dependent. Treat the package list shown by your repository as authoritative instead of assuming that a version available on one release is available on another. If you change the PHP version later, install the connector for the new runtime as well.
4. Retrieve the WebAdmin credentials
The randomly generated WebAdmin Console password is stored in /usr/local/lsws/adminpasswd. Read that file on the VPS and keep the password in a secure password manager. Open the WebAdmin console at https://server-address:7080 after allowing port 7080 from your administration network.
5. Create the virtual host and listener
In WebAdmin, create a virtual host for the exact domain, assign its document root, and map the domain to an HTTP listener. Add an HTTPS listener or the HTTPS configuration supplied by your chosen deployment method. Save and apply the configuration, then verify that the listener points to the intended virtual host rather than a default site.
Route B: use the OpenLiteSpeed one-click script
The OpenLiteSpeed One-Click Script supports all supported operating systems and exposes options for WordPress, PHP, databases, ACME certificates, OWASP rules, and Fail2Ban. It is useful when you want the components installed together without manually assembling package and virtual-host settings.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Standard WordPress mode
- Start the documented OLS one-click script on the clean VPS.
- Select the WordPress option by supplying
-W. - When prompted, choose from the PHP and database versions offered for that operating system.
- Review any ACME, OWASP, and Fail2Ban choices before allowing the script to apply them.
- Wait for the script to finish, then open the domain in a browser. The
-Wworkflow requires you to complete WordPress setup in the browser; it does not replace the web installer.
WordPress Plus mode
Use the documented --wordpressplus <site-domain> option when you want a named site configured with WordPress and LiteSpeed Cache. Replace the example value with the real fully qualified domain that already resolves to the VPS. Because the script can also request ACME and enable security controls, read each prompt rather than accepting settings blindly.
When one-click is the better choice
- You are deploying a standard site on a clean server.
- You prefer a guided choice of supported PHP and database versions.
- You want ACME, OWASP, or Fail2Ban exposed during the same run.
- You do not need a hand-built virtual-host hierarchy before WordPress is online.
Route C: create the site with the OpenLiteSpeed CLI
Install the OpenLiteSpeed CLI according to its documentation, then create the site with the WordPress and Let’s Encrypt switches:
ols site create example.com --wp --leThe command creates a WordPress site for the supplied domain and requests Let’s Encrypt through --le. Replace example.com with the domain that resolves to this VPS. Before running it, make sure ports 80, 443, and 7080 are free or intentionally accounted for; otherwise the CLI may fail to bind listeners or complete validation.
After the command returns, inspect the generated virtual-host and listener settings, open the site in a browser, and complete the WordPress database and administrator screens. CLI automation reduces repeated manual work, but it does not remove the need to verify DNS, certificate status, and the resulting site configuration.
Recommended Free Tools
Verify PHP, MariaDB, and the WordPress prerequisites
Before troubleshooting WordPress, verify the lower layers in order:
- OpenLiteSpeed responds. Request the server over HTTP and confirm that the response comes from the intended virtual host.
- LSPHP is selected. In the OpenLiteSpeed configuration, confirm that the virtual host uses the LSPHP version you installed, not a missing or older runtime.
- The MySQL connector is present. Check the selected LSPHP package set for its MySQL database extension. A PHP runtime without that connector can load pages but fail when WordPress tries to connect to MariaDB.
- MariaDB or another MySQL-compatible server is running. Confirm the database service is installed and reachable locally by the credentials you plan to enter in WordPress.
- File ownership and document root match. The virtual host must point to the directory containing the WordPress files, and the web server must be able to read them and write only where WordPress requires it.
If the LSPHP version offered by the repository differs from the version you expected, use the version the operating system supports or switch to a supported image before continuing. Mixing packages from unrelated releases is more likely to create a broken runtime than to solve a version mismatch.
Map the domain and configure HTTPS
Virtual-host mapping
Set the domain name on the virtual host and map that host to the HTTP and HTTPS listeners. Test the bare domain and the www name separately if you intend to publish both; each name must be included in the virtual-host mapping and certificate request.
ACME and Let’s Encrypt
ACME automation is available in the one-click and CLI workflows. For a successful certificate request, DNS must resolve to the VPS and port 80 must be reachable for the validation flow used by the installer. If validation fails, correct DNS or firewall problems first and then request the certificate again rather than repeatedly changing WordPress settings.
Manual certificate settings
For a manually managed certificate, set the private-key and certificate paths in the virtual host’s SSL settings. Keep the HTTPS listener’s SSL settings configured as well: virtual-host SSL values override listener values, so leaving the listener incomplete can create confusing results when a different host or fallback listener is selected.
Test HTTP-to-HTTPS behavior
- Open the HTTP URL and confirm that it reaches the intended virtual host.
- Open the HTTPS URL and inspect the certificate name and validity in the browser.
- Test both the bare domain and any
wwwalias you configured. - Only after HTTPS works should you enforce an HTTP-to-HTTPS redirect or enable HSTS.
Finish WordPress in the browser
Browse to the domain after OpenLiteSpeed, PHP, the database, and HTTPS are ready. The WordPress installer asks for the database host, database name, database user, database password, site title, administrator username, administrator password, and administrator email. Use the database account created for this site rather than a server-wide administrative account.
If the one-click script created the database, use the credentials it displayed or stored during installation. If you created MariaDB manually, enter the matching database name, user, password, and local host value. A database connection error at this stage usually indicates an incorrect credential, a missing PHP MySQL connector, or a database service that is not running; it is not fixed by changing the WordPress site URL.
After the installer completes, sign in to the WordPress dashboard, load the home page, open an administration page, and test a media upload. These checks exercise PHP execution, database writes, URL generation, and the document-root permissions in one pass.
Apply security controls deliberately
OWASP rules
Enable the Open Web Application Security Project rules when they fit your application. Web-application-firewall rules can block malicious requests, but they can also flag legitimate plugin or API traffic. Review the logs after activation and create narrowly scoped exceptions instead of disabling the entire ruleset for one false positive.
Fail2Ban
Fail2Ban can respond to repeated authentication failures when its filters and jail settings match your logs. Confirm that the ban action cannot lock out your administrative address, and verify that log rotation does not stop the filter from seeing new events.
HSTS
Enable HTTP Strict Transport Security only after every required hostname works over HTTPS. HSTS tells browsers to use HTTPS automatically; enabling it before the certificate and aliases are correct can make recovery harder for visitors.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11reCAPTCHA
Use reCAPTCHA where the deployment exposes it as an option, especially on publicly reachable authentication or form endpoints. Keep the site keys and secret keys out of public configuration files and test the protected form from a normal browser.
Namespace isolation
Namespace isolation can separate sites or processes on a shared VPS. Apply it when your hosting layout benefits from isolation and confirm that PHP file access, scheduled tasks, uploads, and backups still work. It is not a substitute for patching WordPress, plugins, or the operating system.
Troubleshoot the common failure points
| Symptom | Likely cause | Action |
|---|---|---|
| Installer cannot bind port 80 or 443 | Another service is listening, or a firewall rule is conflicting | Identify the existing listener, stop or reconfigure it, then rerun the installation or CLI command. |
| WebAdmin is unreachable on 7080 | Port 7080 is blocked or OpenLiteSpeed is not running | Allow the port from your administration network and verify the OpenLiteSpeed service state. |
| Browser shows the wrong site | DNS still points elsewhere or the domain is mapped to the wrong virtual host | Check A/AAAA records and the listener-to-virtual-host mapping. |
| WordPress reports a database-driver error | The selected LSPHP runtime lacks its MySQL connector | Install the matching connector package for that LSPHP version, restart the relevant service, and retry. |
| Let’s Encrypt validation fails | DNS has not propagated, port 80 is blocked, or the requested name is not mapped | Correct DNS, firewall, or virtual-host mapping, then request the certificate again. |
| HTTPS serves a certificate for another site | Listener settings are being used because the virtual-host SSL mapping is incomplete | Set the certificate and private-key paths at the virtual-host level and retain valid listener SSL settings. |
| OWASP rules block a legitimate request | A rule matches normal plugin, API, or form data | Review the matching rule in the logs and add the smallest possible exception. |
| HTTP-to-HTTPS redirect loops | The redirect and HTTPS termination layers disagree | Confirm which listener terminates TLS, remove duplicate redirects, and retest in a fresh browser session. |
Use a repeatable post-install checklist
- The VPS runs a supported Debian, Ubuntu, CentOS, or compatible release.
- DNS A and, if used, AAAA records resolve to the VPS.
- Ports 80 and 443 serve the intended virtual host; port 7080 is restricted to administration.
- The selected LSPHP runtime and its MySQL connector are installed.
- MariaDB or another MySQL-compatible database accepts the WordPress credentials.
- The virtual host is mapped to both HTTP and HTTPS listeners.
- The certificate covers every hostname you publish.
- WordPress dashboard login, front-end pages, permalinks, and media uploads work.
- Security controls are enabled only after reviewing their logs and compatibility with the site.
For a standard clean VPS, the one-click script is the quickest supported path. For strict version and configuration control, use the repository/manual route. For repeatable creation of additional WordPress sites, use the CLI command with --wp and, when appropriate, --le.
