OpenLiteSpeed Configuration Guide

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

Where OpenLiteSpeed sits

OpenLiteSpeed is a separate server from Apache even when a virtual host sounds familiar. Listeners, virtual hosts, and contexts are its objects. The WebAdmin console is a different port, often 7080, and it is an admin surface. It stays on loopback or the management prefix. It does not sit next to the public site.

A graceful restart applies a config you have checked. Restarting because the console looked saved is how a typo becomes an outage. Use the config path the install actually uses, not an Apache conf.d you hoped it would read.

The lab listener is 127.0.0.1 and a site root with one test page. The generators draft a vhost, a proxy context, and a TLS shape. Trim them to loopback for the lab.

An external application or a proxy context points at a process you run. Name it in the ticket. Do not point it at a host you do not operate.

A loopback site you can fetch

Step 1 for OpenLiteSpeed is the listener. Create a listener on 127.0.0.1 and a virtual host with one test page. A public bind is a later ticket. Check: A local fetch returns the page. If the check fails, do not reload again and do not point a name at this host. Restore the previous file. The generators for OpenLiteSpeed draft a site in the browser and do not open a firewall. Delete every listen-on-every-address line for the lab. Replace prompt-for-this. A config from a neighbouring web server is not this syntax.

Step 2 for OpenLiteSpeed is WebAdmin. Bind the admin console to loopback. Set an admin password that is not prompt-for-this and not in the ticket. 7080 on a public address is a second product. Check: An outside address cannot open the admin port. If the check fails, do not reload again and do not point a name at this host. Restore the previous file. The generators for OpenLiteSpeed draft a site in the browser and do not open a firewall. Delete every listen-on-every-address line for the lab. Replace prompt-for-this. A config from a neighbouring web server is not this syntax.

Step 3 for OpenLiteSpeed is the restart. Take a copy of the config, then graceful restart, then fetch again. A restart without a copy has no rollback. Check: The page still matches after restart. If the check fails, do not reload again and do not point a name at this host. Restore the previous file. The generators for OpenLiteSpeed draft a site in the browser and do not open a firewall. Delete every listen-on-every-address line for the lab. Replace prompt-for-this. A config from a neighbouring web server is not this syntax.

Step 4 for OpenLiteSpeed is the context. Add a proxy or app context only if the upstream is in the ticket. An empty context looks configured and serves nothing useful. Check: The upstream answers through the vhost. If the check fails, do not reload again and do not point a name at this host. Restore the previous file. The generators for OpenLiteSpeed draft a site in the browser and do not open a firewall. Delete every listen-on-every-address line for the lab. Replace prompt-for-this. A config from a neighbouring web server is not this syntax.

Step 5 for OpenLiteSpeed is the draft. Diff the generator output against the running config. Drafts include listeners you did not want. Check: The diff is the change you meant. If the check fails, do not reload again and do not point a name at this host. Restore the previous file. The generators for OpenLiteSpeed draft a site in the browser and do not open a firewall. Delete every listen-on-every-address line for the lab. Replace prompt-for-this. A config from a neighbouring web server is not this syntax.

# OpenLiteSpeed lab. Review before you paste.
# Site listener 127.0.0.1. One test page.
# WebAdmin stays on loopback or the management prefix.
# Graceful restart only after you can read the config back.
# prompt-for-this is not a password to keep.

Certificates come after the name is yours

TLS uses the certificate fields OpenLiteSpeed expects, for a name you control, after the plain lab site works. The key is a file with a tight mode, not a paste in the ticket.

The WebAdmin listener does not get a public certificate and a public bind just because the site did.

Rollback is the previous config directory copy you took before the graceful restart.

What not to paste

OpenLiteSpeed is not Apache. apachectl does not test this config.

Port 7080 on every address is not a default you accept.

A context that proxies to the world is not a connectivity test.

The hour you stop

Write the hostname, the role, and the clock time before you change OpenLiteSpeed. If this host is also serving users, it is not the lab and this first hour belongs on a spare. The provisioning guide is how the spare gets built. A change without a spare is a change you can still postpone.

Keep the console or the out-of-band path open for the whole hour. Reloading a network service, a firewall, or a secure-shell daemon from the only session is how a lab becomes a drive across town. The hardware guide names that path for a physical machine. A virtual machine uses the hypervisor console. A cloud instance uses the serial console the platform gives you. Test it before the reload, not after.

The address 192.0.2.10/24 and the gateway 192.0.2.1 are documentation. They belong in the lab note and nowhere else. On a real network, use the prefix the network desk already assigned. On a cloud instance, use the address the platform assigned and do not hard-code the documentation range into user-data. If a generator filled the documentation address into a production draft, delete it.

prompt-for-this is a reminder that a secret is missing. It is not a password you set, not a token you commit, and not a string you leave in a configuration file because the service started. The real secret lives in the password store. The ticket says who can read it. A file that still contains the reminder is a file you have not finished.

One service is enough for the first hour on OpenLiteSpeed. The purpose from the fundamentals page says which service. Every other package stays uninstalled until its own guide has a ticket. A host that enables a web server, a database, and a queue in the first hour has three changes and no proof. Finish the login, the address, and the update. Then stop.

Read the package transaction before you accept it. A count of packages is not a review. If the list contains a repository you did not add, stop. If it contains a kernel, the patch guide's reboot decision applies and the console stays open. If it contains software this role does not need, remove that line from the plan rather than installing it and disabling it later.

The previous image, the previous configuration file, or the previous package version is the rollback. Write the path down while the host still works. A rollback you invent after a failed reload is a guess. The migration guide assumes the old copy is still there. Do not delete it in the same hour to free a disk.

When the checks pass, copy the notes into the ticket and leave the host alone. The next host waits until a second person can repeat the login and the address from the notes. A fleet built from memory drifts. A fleet built from the file the provisioning guide stored stays boring, which is the point of OpenLiteSpeed in production.

If a step on OpenLiteSpeed fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied config produces a host nobody can rebuild. Rebuild from the image instead. The time you lose is smaller than the time you will spend explaining the hybrid.

Hand the finished lab to the guide that matches the role: web, mail, storage, backup, or hardening. OpenLiteSpeed being installed is not the same as the role being ready. The role guide has its own proof. Do not skip it because the package manager exited without an error.

A second person reads the hostname, the address, and the rollback path aloud before you build the next host. If they cannot find those three in the ticket, the notes are not done. Silence is not agreement. The check is the sentence they repeat back.

Store the working notes next to the image version. A month from now OpenLiteSpeed will still boot from that pair, and the chat where you remembered a flag will be gone. The file is the memory. The host is replaceable. That is the whole point of writing this hour down.

OpenLiteSpeed checks before a public listener

Confirm this before you call the change done: OpenLiteSpeed is the process that is listening, confirmed on the host. The lab site binds to 127.0.0.1, not to every address. The config test passed before the reload. A fetch of the test page from the host itself succeeded. The admin or dashboard port is not reachable from a public address. The document root is readable by the worker and not writable by it. No certificate was requested for a name you do not control. The generator draft was edited until it matched this file. The previous config is saved. prompt-for-this was not left in a password field. Logs from the test do not contain a secret. A second person read the listen address. WebAdmin is not on a public address. The admin password is not in the ticket. A copy of the previous config exists. apachectl was not used as the test. The listener address was read back from the running config, not only from the form. And the test page is the only document in the lab root, so a fetch cannot succeed by accident. If one of those fails, stop.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

Guides in this cluster

These supporting pages belong to this pillar.