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.

  • Swarfega@lemm.eeEnglish
    0·
    14 days ago

    Caddy is awesome! I originally went for nginx proxy manager to manage my certs as it has a GUI. However, despite being text based, Caddy is so even easier to configure…

            email myemail@mydomain.net
}

jellyfin.mydomain.net {
        reverse_proxy 192.168.0.1:8096
}```


That's all there is to it. Caddy does the heavy lifting.
    • Rogue@feddit.ukEnglish
      0·
      14 days ago

      I don’t think you even need to configure the email.

      If I recall correctly emails are optional for Let’s Encrypt but Caddy are partnered with ZeroSSL who do require emails so you’re encouraged to provide one.