Lighttpd 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 Lighttpd sits

Lighttpd is a small web server with lighttpd.conf, modules you enable by name, and conditionals for hosts and paths. The test is lighttpd -t against the file you edited. Reload only after that test. It is not Nginx and it is not Apache, so their generators' output does not get pasted here. Lighttpd has its own drafts.

The lab binds 127.0.0.1:8080 and serves one test page. Modules such as mod_proxy are enabled only when the ticket names a proxy. A conditional that accidentally matches every host is the bug to look for. Read the condition aloud.

The user the daemon runs as can read the document root and cannot write it. The permissions guide is the mode. The web guide is the public-listener decision.

Keep the config short. Lighttpd's advantage is a file you can read. A generated file longer than the site you have is a file to trim.

A loopback site you can fetch

Step 1 for Lighttpd is the file. Edit the config the service actually loads. A second conf in the wrong path is invisible. Check: The test names the file you edited. If the check fails, do not reload again and do not point a name at this host. Restore the previous file. The generators for Lighttpd 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 Lighttpd is loopback. Bind 127.0.0.1:8080 and a document root with one page. Loopback is enough proof. Check: The 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 Lighttpd 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 Lighttpd is the test. Run lighttpd -t and read the result. A reload of a bad conditional takes the site down. Check: The test passes before reload. If the check fails, do not reload again and do not point a name at this host. Restore the previous file. The generators for Lighttpd 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 Lighttpd is modules. Leave unused modules disabled. A proxy module without an upstream is noise. Check: The enabled modules match the ticket. If the check fails, do not reload again and do not point a name at this host. Restore the previous file. The generators for Lighttpd 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 Lighttpd is the user. Confirm the daemon user and the directory mode. A writable document root is the same mistake as on any other server. Check: The user can read and cannot write. If the check fails, do not reload again and do not point a name at this host. Restore the previous file. The generators for Lighttpd 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.

# Lighttpd lab. Review before you paste.
# bind 127.0.0.1 port 8080. One test page.
# lighttpd -t before reload.
# Enable mod_proxy only if the ticket names an upstream.
# prompt-for-this is not a password to keep.

Certificates come after the name is yours

TLS modules and certificate paths come after the plain loopback site works, and only for a name you control. The key stays out of the ticket.

lighttpd -t must still pass with the certificate paths in place. A missing file is a failed test, not a reload.

Rollback is the previous lighttpd.conf you copied.

What not to paste

Lighttpd is not Nginx. There is no server block to paste.

Enabling every module in the default file is not required.

A conditional you do not understand does not stay in the file.

The hour you stop

Write the hostname, the role, and the clock time before you change Lighttpd. 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 Lighttpd. 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 Lighttpd in production.

If a step on Lighttpd 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. Lighttpd 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 Lighttpd 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.

Lighttpd checks before a public listener

Confirm this before you call the change done: Lighttpd 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. lighttpd -t passed on the loaded file. The bind address is loopback. Unused modules are off. No Nginx or Apache syntax remains. The daemon user was confirmed with the process list after reload. And the document root contains the test page and nothing you did not mean to publish. 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.