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:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Lets Encrypt should be fine issuing a cert on a FreeDNS hostname using the HTTP-01 challenge, I believe you may also need port 80 open?
The basic steps would be install a letsencrypt client on the NAS, issue a cert for the FreeDNS hostname, then give that cert to jellyfin directly or to a reverse proxy sitting in front of it.
I do have port 80 open as well as 443, both going to my Jellyfin HTTP/HTTPS ports respectively. HTTP seems to work for both when I access "pretty" domain and the FreeDNS URLs directly. It's really only when I try to force HTTPS that I'm having issues.
I'll play around with Let's Encrypt today to see if I can get the FreeDNS cert applied. I've tried to use AI to assist me in learning how to do all this, it suggests I need both my "pretty" domain and the FreDNS domain tied to the same Cert, which Im unable to do at my current domain registrar, so I might also need to move that but I'll take it one step at a time.
I want to access my Jellyfin over the web
Do you want other people to access jellyfin? Or strangers?
Or would a VPN like wireguard (or even tailscale) be more appropriate?
No, I don't necessarily want other people to access my Jellyfin, but my folx live out in the boons, (visiting on holidays etc.) and that was the only way I could find to reliably access my media. I guess I also come from a web background so it felt right to me. The Asustor I have really limits what I can and can't do with it. I got it as a like, starter point since it felt out of the box. I'm also on Windows lol.
Do you have any resources for how I could grant access outside my network with a VPN, wireguard, or tailscale? I'm open to other options, I'm really just kind of fumbling my way through this idea of what I want.
If its just yourself (or up to 3 people), go with tailscale. Sign up for a free account, looks like there is an installer in the asusator (or whatever its called) app store.
Start reading up on tailscale. Its essentially a managed VPN designed for enterprises with features for servers and infrastructure.
How exactly is SSL terminated in your setup? Usually, you'd use something like nginx or apache for termination, but I don't see that in your description?
So who exactly has the private key?
I'm still pretty green so I'm not sure what terminated means in this context.
My domain registrar for my "pretty" domain (not FreeDNS) allowed me to issue a Let's Encrypt on it. It gave me the encrypted Cert code, Private Key code, and Immediate Cert code. I was able to bring them down into .crt and .key files respectively and assign them to my NAS. Jellyfin though required a PKCS #12 file so I installed openssl CLI via Choco and fed it my .crt and .key files to generate the necessary pfx file. So, right now all the cert information is tied to my "pretty" domain via my domain register. I would assume that my register and Let's Encrypt has my private key info, but also my key files uploaded to the NAS and rolled into the PFK file.
Not sure if that helps or answers your question but that's the info I got.
"Terminated" means something that's using the certificate to encrypt connections. You got the certificate but doesn't sound like anything is actually using it.
You can give it to Jellyfin so it can start encrypting the HTTPS port. The downside is that you'll be stuck using your pretty domain for just Jellyfin, for now.
If you decide to use it for more services later you can install a reverse proxy, get a wildcard certificate for *.pretty.domain, start creating subdomains as CNAMEs to the FreeDNS (eg. jellyfin.pretty.domain) and defining them in the reverse proxy.
The reverse proxy will be handling the forwarded port and terminate the encryption for all subdomains, and will hand-off the unencrypted connection privately to the relevant app based on which domain the visitor is using (and issuing 404 not found it they use a domain you haven't defined).
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| HTTP | Hypertext Transfer Protocol, the Web |
| HTTPS | HTTP over SSL |
| IP | Internet Protocol |
| NAS | Network-Attached Storage |
| SSL | Secure Sockets Layer, for transparent encryption |
| VPN | Virtual Private Network |
| nginx | Popular HTTP server |
7 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.
[Thread #607 for this sub, first seen 16th Mar 2024, 16:25] [FAQ] [Full list] [Contact] [Source code]
I do appreciate everyone's suggestions and help. Here's what I ended up doing.
FreeDNS via freedns.afraid.org as a DDNS Subdomain
Domain + Subdomain via hosting provider
Hosted Subdomain CNAME to the DDNS Subdomain
Setup DDNS using Asustor > Settings > Manual Connect and setting up a FreeDNS account and input the info it needed. Last DDNS update keeps coming back as Failure but FreeDNS keeps updating my IP so it seems to work, but for whatever reason Asustor doesn't think it's working.
Used openssl + certbot CLI tools to generate a certificate that covers all 3 cases: Hosted Subdomain, Hosted Domain, DDNS Subdomain. Looks like this:
certbot certonly --key-type rsa --rsa-key-size 2048 --manual --preferred-challenges dns -d hosteddomain.example -d subdomain.hosteddomain.example -d ddns.domain.example
This will set up verification codes that you can create TXT records for on the Hosted Domain and the DDNS Domain. I had to contact FreeDNS to get access to add text records with underscores but they were cool and quick to reply. They look like this:
_acme-challenge.hosteddomain.example
8suZTccF9ZpB0fnBr9mgEEXTcX7cqSkDXiBzucTcOfw
Once the certificates are in place I uploaded them to my Hosted Domain and verified that my Hosted Domain was showing the SSL certificate / lock at HTTPS.
Next I logged into my Asustor and under Settings > Certificate Manager I added my SSL Certificates and assigned it as the primary certificate for the NAS.
Finally, I needed to enable SSL on my Jellyfin, which required a PFX file.
openssl pkcs12 --export -out "Z:\Path\To\PFXOutput\jellyfin.pfx" -inkey "Z:\Path\To\Cert\jellyfin.key" -in "Z:\Path\To\Cert\jellyfin.crt"
Under Jellyfin > Dashboard > Networking I enable HTTPS, Require HTTPS, give it the path to the PFX file and the PFX password, and Allow remote connections to the server. I disabled port forwarding from Jellyfin and had to jump into my router to remove the UPnP records it had previously added. All port numbers are default to Jellyfin and no URLs in the Server Address Settings.
Important to take note of the Jellyfin ports here for both HTTP and HTTPS requests. Important note to restart Jellyfin after this takes effect. Asustor has an App Central where under Installed Apps you can just turn it off and back on again.
Finally, I added Port Forwarding to my router so that the 443 looks for the Jellyfin HTTPS port and 80 looks for the Jellyfin HTTP port at my NAS IP.
Now I can access HTTPS subdomain.domain.example and land at my Dockered Jellyfin app.
I don't know if this will help anyone but damn is the documentation on how to do this kind of thing scarce so here I am. I was quite a struggle both learning all this and implementing it but it's been fun overall.
FreeDNS doesn't seem to have a way to add any kind of SSL Certs as far as I can tell. Not that I needed to, but when I tried explaining my situation to the hosting provider they suggested that the cert needed to be on the DDNS server.
I also couldn't get the Asustor Reverse Proxy to work either. Many of the tutorials and user suggestions i ran across suggested that this is the way to get SSL but when I tried to implement it I kept landing at my portal login and nothing was getting proxy'd. The netstat command was showing that whatever the reverse proxy port needed was not open - I also ran across this in a 2020+ thread on Asustor.
Right now I'll also need to manually update the certs and go through this process again in 3 months time. There might be a way to automate this process but it's a lot of steps that I'm not sure can be automated in this seeming (to me) flawed setup. In any case, it's been challenging but fun and I think in the next 6 months I'll upgrade out of Asustor and into a bigger server with a core Linux setup. I know nothing about Linux :)