As the title says I’m unable to renew a cert on a self-hosted lemmy instance. A friend of mine just passed away and he had his hands all up in this and had it working like magic. I’m not an idiot and have done a ton of the legwork to get our server running and working - but lemmy specifically required a bit of fadanglin’ to get working correctly. Unfortunately he’s not here to ask for help, so I’m turning to you guys. I haven’t had a problem with any of my other software such as nextcloud or pixelfed but for some reason lemmy just refuses to cooperate. I’m using acme.sh to renew the cert because that’s what my buddy was using when he had set this all up. I’m running apache2 on a bare metal ubuntu server.

Here’s my httpd-ssl.conf:

https://pastebin.com/YehfTPNV

Here’s some recent output from my acme.sh/acme.log:

https://pastebin.com/PESVVNg4

Here’s the terminal read out and what I’m attempting to execute:

https://pastebin.com/jfHfiaE0

If you can make any suggestions at all on what I might be missing or what may be configured incorrectly I’d greatly appreciate a nudge in the right direction as I’m ripping my hair out.

Thank you kindly for your time.

  • verstra@programming.devEnglish
    0·
    15 days ago

    You’ve just reminded me to fix cert renewal on my instance. I’m using let’s encrypt & their certbot with nginx and it is great.

    Recently my nginx config got too complex, so nginx plugin stopped working correctly, because it wasn’t able to inject the config for ACME challenge correctly anymore. The solution was to manually configure location /.well-known/acme-challange to read from a local directory and configure certbot to use a local webroot directory instead of fiddling with nginx config.