Jellyfin Forum
Let's Encrpt has expired, can't access Jellyfin remotely - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Let's Encrpt has expired, can't access Jellyfin remotely (/t-let-s-encrpt-has-expired-can-t-access-jellyfin-remotely)



Let's Encrpt has expired, can't access Jellyfin remotely - Hostile_18 - 2024-04-16

Hi All,

I've a setup Unraid + Jellyfin. Users connect outside the home network on a reverse proxy using Swag.
 
All has being running great for the last two months. A few days ago I got an email saying Lets Encrypt was expiring. Today I can't use the Jellyfin app on my phone and several clients can no longer connect. I can connect outside the network using chrome, but it says my website is unsafe. Unraid, Jellyfin, Duck DNS and Swag have being updated and restarted when required.
 
My Swag log seems to be showing errors, but I've no idea what it means (I had a lot of guidance setting this up). Can anyone tell me what I need to do to renew this certifcate?

*swag log removed*



RE: Let's Encrpt has expired, can't access Jellyfin remotely - TheDreadPirate - 2024-04-16

Is port 80 open on your router? During the renewal process the ACME challenge happens on port 80.


RE: Let's Encrpt has expired, can't access Jellyfin remotely - Hostile_18 - 2024-04-16

(2024-04-16, 06:53 PM)TheDreadPirate Wrote: Is port 80 open on your router?  During the renewal process the ACME challenge happens on port 80.

I believe so, nothing has changed in the last few months its being working Smiling-face

[Image: Screenshot-2024-04-16-200225.png]


RE: Let's Encrpt has expired, can't access Jellyfin remotely - TheDreadPirate - 2024-04-16

Try having the internal and external ports both be 80 instead of 80 -> 180. I'm not certain that the renewal process will listen on your custom http port.


RE: Let's Encrpt has expired, can't access Jellyfin remotely - Hostile_18 - 2024-04-16

(2024-04-16, 07:26 PM)TheDreadPirate Wrote: Try having the internal and external ports both be 80 instead of 80 -> 180.  I'm not certain that the renewal process will listen on your custom http port.

Hi, I reverted it back so 80>80 etc and changed the network back to bridge (from proxynet) and it failed to work (I didn't change the hub settings thinking on it), when I pressed apply. However I put it back to how i had it and it is all working now. Perhaps it was just a glitch, or reinputting what was working before sent out a new request or something.

In any case all working now, albeit strange solution! lol. Thank you once more for helping me!