Installing Let's Encrypt on a DNS to use with a Jellyfin server

Help
21

From the Internet OR within the same network(s)?

2 Likes
22

From my home wifi.

Sam

23

Okay thanks. How would I go about using the certificate on a different?

Sam

1 Like
24

Firsta a caution: This is only viable if this is for your private use. The general public won't know to use the alternate URL format

That said:

First test to be sure the alt port can work at all:

  • Create a new server block in nginx for jellyfin.sbljellyfin.com
  • The listen value should be this alternate port to be tested (listen 8443; for example)
  • Update your router as needed to get that port forwarded to your server
  • Run http test from outside your own network (like cell phone with wifi off)

If that works
Modify the server block to support https (so, it's like the one for 443 but using 8443)
Then, run test for that like
https://jellyfin.sbljellyfin.com:8443

2 Likes
25

I don't intend the site for the general public. I just want to be able to access the content on my JellyFin from outside my home network and possibly share it with friends and family on occasion. JellyFin seems designed to use urls like that because I also have to include the port number at the end of the http url that is currently working. The weird thing is, when I first got the domain and server working together, https was working. But then I had some issues with the JellyFin settings and after I removed the option for a base url (i.e. /jellyfin), it stopped working.
One quick question, setting up this new server block won't impact my current one will? I just don't want to risk making everything not work again.

26

Right now both port 80 and 443 are blocked. If HTTPS was working once then your ISP can't be blocking it.

To your question, I don't know Jellyfin at all. But, with nginx you can add new server blocks, restart nginx, and not disrupt the other server blocks (apart from the brief time for restart). Before trying restart you can do nginx -t to test syntax.

What I described is manually editing nginx conf. I don't believe certbot --nginx plug-in will configure that. And, as noted, if jellyfin is updating your nginx conf too I can't speak to that.

Take a backup or careful notes of what you change and test each step. That way you can unwind if need be. But, generally, nginx servers can handle many (many) server blocks.

2 Likes
27

Or they suddenly changed their policy or something similar, but I agree, it's highly unlikely.

3 Likes
28

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.