this post was submitted on 16 Jun 2023
2 points (75.0% liked)
Self Hosted - Self-hosting your services.
11495 readers
12 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
Important
Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.
Cross-posting
- !everything_git@lemmy.ml is allowed!
- !docker@lemmy.ml is allowed!
- !portainer@lemmy.ml is allowed!
- !fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
- !selfhosted@lemmy.ml is allowed!
If you see a rule-breaker please DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That makes sense.
So the domain name I am using already has letsencrypt/certbot set up as I access my Nextcloud from the web over https. I believe it throws the keys somewhere in /etc.
I guess what I should be doing is searching for where the first jellyfin command created the cert.pem file and then just adjust the path in the second command to that?
Either that (if you want to use a self-signed cert) or point it at the certbot-created files in /etc? If I understand the jellyfin docs correctly, the second command just translates the usual .pem files into a .pfx file for jellyfin, so should work with any certificate you give to it.
If you're going to do the latter, you should also add a certbot deploy script to regenerate the .pfx file after a certificate renewel (and possibly restart jellyfin, idk).
So I happened to have been in my home's /Downloads folder when I executed the commands and apparently it created the cert file there, so I pointed the second command at it and it created a pfx file. I point Jellyfin to it in the networking settings and it seems to have accepted it, but when I try to access it from the web I just get a 404. Argh frustrating.
I've never used Jellyfin so pretty sure I'm one of the worst people to ask and I doubt anybody else will see this so far down. If I were you I'd try and have a look at the logs - either the reverse proxy logs (which seem to be really popular these days) or the actual webserver/Jellyfin ones. Those will typically log some errors.
If you get a 404 from Jellyfin then port forwarding is set up correctly (as otherwise you wouldn't be able to connect to Jellyfin at all). You may be getting a 404 from something else though.
Nah the 404 is coming from Apache. Also I don't use a reverse proxy (yet, though I want to set up my own Lemmy instance on this Pi as well so I'll probably be setting up a reverse proxy before I do that so people don't know where I live).
Okay so the http port for Jellyfin is 8096 and the https is 8920. When I add those to the domain name from the web (https://[domain]:8920/jellyfin), I get this error:
Secure Connection FailedAn error occurred during a connection to [DOMAIN]:8920.PR_CONNECT_RESET_ERRORError code: PR_CONNECT_RESET_ERRORThe page you are trying to view cannot be shown because the authenticity of the received data could not be verified.So I assume the jellyfin pfx that I created is not the correct one and I should just be using the one created by certbot for the overall network itself.
Got it solved! I found someone else solved it here: https://github.com/jellyfin/jellyfin/issues/6697#issuecomment-1086973795
Copied what they did (with tweaks to password and so on) and voila it works now.
Also I do have the port open in ufw and have port forwarded it in my router (https and http).