Jellyfin Forum
Goofed up SSL, can no longer 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)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: Goofed up SSL, can no longer access Jellyfin remotely. (/t-goofed-up-ssl-can-no-longer-access-jellyfin-remotely)

Pages: 1 2


Goofed up SSL, can no longer access Jellyfin remotely. - CoraBorealis - 2023-12-07

Alright, so here's the scoop.

I reserved my IP address and opened port 8096 on my router. I went to my public IP in my browser (with the port specified) to test it, and it worked! And then I installed Certbot in an attempt to get SSL going.

Well, I guess I was way in over my head! I wasn't fully understanding the guide on the Certbot website, but I thought I could figure it out through trial and error. Well, long story short, I didn't get SSL working. But not only that, now I can't access my Jellyfin via my public IP address anymore! I can still get to it with my private IP, but that's not helpful! I'm trying to share my Jellyfin with my family!

So I uninstalled Certbot, hoping that would somehow fix it as everything was working fine before I started messing around with CertBot. But nope. Even after uninstalling it, I still can no longer access my Jellyfin via my public IP.

Would anyone know how I might be able to fix this? Everything was working for a grand total of 5 minutes before I goofed it up! I'd really like to go back in time to that moment, but alas I cannot. Any help will be greatly appreciated!

Thanks for reading!


RE: Goofed up SSL, can no longer access Jellyfin remotely. - TheDreadPirate - 2023-12-07

Borking your SSL setup shouldn't break public access to jellyfin unless you also changed something with Jellyfin. Or your public IP changed or something. Verify you didn't check "Require HTTPS" in Jellyfin, remove any cert configs in Jellyfin.


RE: Goofed up SSL, can no longer access Jellyfin remotely. - CoraBorealis - 2023-12-07

Thanks so much for the reply!

I swear, I changed nothing in my Jellyfin settings though. "Require HTTPS" has not been checked. And the public IP address has not changed (I've checked several times to make sure). I've restarted Jellyfin, as well as the computer it's running on several times, but it hasn't helped.


RE: Goofed up SSL, can no longer access Jellyfin remotely. - TheDreadPirate - 2023-12-07

Did you turn off port forwarding for port 8096 in your router in anticipation of not using it?


RE: Goofed up SSL, can no longer access Jellyfin remotely. - CoraBorealis - 2023-12-07

I have not turned off port forwarding, except briefly to test if disabling and then re-enabling it would fix the issue. It didn't. Port forwarding is still enabled.


RE: Goofed up SSL, can no longer access Jellyfin remotely. - TheDreadPirate - 2023-12-07

Firewall rules? Verify that Jellyfin is listening on port 8096?

What OS are you running? I'm assuming Linux? Which distro?


RE: Goofed up SSL, can no longer access Jellyfin remotely. - CoraBorealis - 2023-12-07

I didn't have to do anything with my firewall when it was working before (before I tried configuring SSL), but I suppose it's possible CertBot may have changed a firewall setting or something?

I'm actually using Windows, not Linux.


RE: Goofed up SSL, can no longer access Jellyfin remotely. - CoraBorealis - 2023-12-07

Jellyfin seems to be listening on all ports according to Windows Firewall with Advanced Security.


RE: Goofed up SSL, can no longer access Jellyfin remotely. - TheDreadPirate - 2023-12-07

In resource monitor, network tab, listening ports, do you see this?

   


RE: Goofed up SSL, can no longer access Jellyfin remotely. - CoraBorealis - 2023-12-07

Yup! Though, I also see entries for Jellyfin listening on ports 1900 and 7359. Is that normal?