Killed my Lighttpd

Troubleshooting
21

I removed everything with my domain in it, and now I’ll wait until I can request another certificate. (I backed up the whole folder first, just in case! Sometimes, I’ll learn from my mistakes :sunglasses: )

Thank you so much for the help so far!

22

Ok let’s see if this will work now

23 
[  OK  ] DietPi-LetsEncrypt | Lighttpd webserver detected
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate

IMPORTANT NOTES:
 - Congratulations! Your certificate and chain have been saved at:
   /etc/letsencrypt/live/MY_DOMAINt/fullchain.pem
   Your key file has been saved at:
   /etc/letsencrypt/live/MY_DOMAIN/privkey.pem
   Your cert will expire on 2021-06-05. To obtain a new or tweaked
   version of this certificate in the future, simply run certbot
   again. To non-interactively renew *all* of your certificates, run
   "certbot renew"
 - If you like Certbot, please consider supporting our work by:

   Donating to ISRG / Let's Encrypt:   https://letsencrypt.org/donate
   Donating to EFF:                    https://eff.org/donate-le

[  OK  ] DietPi-LetsEncrypt | Desired setting in /etc/lighttpd/lighttpd.conf was already set:   "mod_setenv",
Enabling dietpi-https: ok
Run "service lighttpd force-reload" to enable changes
Enabling dietpi-https_redirect: ok
Run "service lighttpd force-reload" to enable changes
already enabled
Run "service lighttpd force-reload" to enable changes

Press any key to continue...

I can’t seem to connect, though. I’ll restart my router (had to reenable ports) and the pi.

24

But certificate seems to be created

25

Yeah, I had to press a button to let dietpi restart the services :smiley: Everything is working as intended now.

Thank you so much for your help!

26

ok perfect, after long journey you are back online :smiley:

27

Hi,

I have a similar issue. Every time I request a certificate, lighttpd does not start anymore after the certificate was fetched.
When I delete the letsencrypt folder and delete the symlinks as described above, it starts again.
Happens again if I request another certificate.
Log: 52ed741d-bf34-4117-b051-3ba0a9845973

Any idea guys?

Thanks and regards
Hyper

28

I don’t think so as this issue is 2 years old. Better to look into a topic from yesterday. Lighttpd fails after renewing letsencrypt - #6 by Jappe

1 Like