Lighttpd

Lighttpd is a secure, lightweight web server that uses memory and CPU more efficiently than comparable servers, with FastCGI, CGI, authentication, output…

  • Network Services
Lighttpd is a secure, lightweight web server that uses memory and CPU more efficiently than comparable servers, with FastCGI, CGI, authentication, output compression, and URL rewriting for environments from small home servers to large-scale deployments.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

50/100 Fair

Maintained
61last commit 146 days ago
Popular
54512 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
512
Open issues
3
Last commit
2026-06-28
Activity
stale

Checked 2 days ago - source: GitHub (lighttpd/lighttpd2)

Resources & Compatibility

Requirements not published yet.

Checked 2 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set Angel's listen address and user In the Angel config, set allow_listen (the address and port the server listens on) to the port visitors should use, such as 8080. Also set user to the account the server should run as; without both, visitors may not reach the site or the server may fail with permission errors. source
  • Turn on an access log for debugging Load the access-log plugin and point it at a writable file such as /var/log/lighttpd/access.log. This leaves a plain list of requests, so you can tell if visitors reached the server when a page does not load. source
  • Point domain names to the right site If you host more than one site, add each domain to vhost.map (the lookup table that sends requests for a name to a site). Without it, a request for your domain may go to the default site instead of the site you expect. source
  • 1.4 vs 2.0 releases The production line is 1.4.x; the lighttpd2 GitHub repo is an abandoned 2.0 rewrite with no production release, so get 1.4 packages from the official site and its package repositories. source

Fetched 2 days ago - each note links to its source

Alternatives (5)

  • Apache HTTP Server - Open-source HTTP server offering cross-platform support, modular architecture, secure configuration, robust content delivery, and extensive…
  • BunkerWeb - BunkerWeb is a self-hosted, open-source web application firewall and NGINX-based web server that protects services with secure-by-default s…
  • Caddy - Caddy is an extensible web server and reverse proxy that serves Transport Layer Security (TLS) by default, making it simple to secure and r…
  • Microsoft IIS - Internet Information Services (IIS) for Windows® Server is a flexible, secure and easy-to-manage Web server for hosting anything on the Web.
  • nginx - Nginx is an HTTP web server, reverse proxy, content cache, load balancer, TCP/UDP proxy, and mail proxy server.

Checked 2 days ago - source: AlternativeTo

Common questions

Should I deploy Lighttpd 1.4 or Lighttpd 2.0?

Use the 1.4.x production line. Lighttpd 2.0 is an abandoned rewrite and there will be no production release.

Can Lighttpd route proxy connections by TLS SNI?

Yes. As of 1.4.83, mod_sockproxy can route connections based on TLS SNI.

What TLS grouping change happened in Lighttpd 1.4.83?

1.4.83 added PQC hybrid KEM X25519MLKEM768 to the default TLS groups.

Where do I report Lighttpd bugs or configuration questions?

Use the Lighttpd issue tracker for bugs and the Forums for configuration questions. Non-public bug reports can be sent to the project security contact.

Answers sourced from github.com, redmine.lighttpd.net, www.lighttpd.net

Community

Collected 2 days ago - public community threads