Lighttpd stopped working


I´m facing the problem that my webserver suddenly stopped working. Using a portscanner I found out that only
the port 22 is working. I rebooted the system, I have checked for updates, but I can´t start the webserver.

DietPi v6.28.0 on a RasPi 3
[] 82 LLMP: lighttpd | mariadb | php
] 114 Nextcloud: File sync, sharing and collaboration platform

I searched with Google and I think the problem is a not starting Lighttpd:


How can I fix this problem?



many thanks for your report.

Usually there is no need to use a port scanner to check what ports are in use on your system. As well if you would know the open port, you still would not know which application is using the port :wink:

A better view you will get on the system themselves. There are multiple ways to check ports in LISTEN status. The follwoing 2 commands could help on this.

lsof -i -P -n | grep LISTEN 
ss -alnp | grep LISTEN

It could happen that lsof tool is not available, but can be installed quite easy

apt update
apt install lsof

Back to your issue: yep lighttpd is failing to start, therefore your web server is not working. Pls can you restart web server and check error log as follow

systemctl restart lighttpd.service
cat /var/log/lighttpd/error.log

Hi Joulinar, this is the result:

root@DietPi-Raspi3:~# systemctl restart lighttpd.service
Job for lighttpd.service failed because the control process exited with error code.
See "systemctl status lighttpd.service" and "journalctl -xe" for details.
root@DietPi-Raspi3:~# cat /var/log/lighttpd/error.log

The filesize of /var/log/lighttpd/error.log is “0”:

root@DietPi-Raspi3:~# ls -l /var/log/lighttpd/error.log
-rw-r--r-- 1 www-data www-data 0 Mär  3 22:26 /var/log/lighttpd/error.log

can you check

journalctl -u lighttpd

That is the (repeating) result:


first I updated your post because it contains your DDNS entry.

than it seems you have SSL configured and Lighttpd is not able to read the certificate anymore. Basically you would have 2 options. ensure the certificate file is still there could be access by Lighttpd or you remove SSL configuration from Lighttpd config file.

SSL: couldn't read X509 certificate from '/etc/letsencrypt/live/<yourDDNS>/combined.pem'