this post was submitted on 16 Mar 2024
12 points (100.0% liked)

Selfhosted

40183 readers
485 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I feel like I have a doozy of a complicated issue and am looking for some guidance.

I'm new to Selfhosting so I got myself an off-the-shelf Asustor NAS. It's got apps which is cool, so I've installed Jellyfin. I want to access my Jellyfin over the web so I've set up DDNS via my Asusstor Manual Connect and FreeDNS. This works well, I can access it over HTTP but the domain is... kind of long and unpleasant, so I got myself a "pretty" domain and setup a CNAME to the FreeDNS. I'm port forwarding on my router, everything works, so far so good.

To make it overtly complicated, I want to make the connection HTTPS. This is where I'm struggling. I've set up the SSL cert for my "pretty" domain via Lets Encrypt, but it times out. I'm not sure if, or how I can make the FreeDNS HTTPS or covered under my Lets Encrypt cert since I don't technically own the FreeDNS domain. My provider doesn't give my any wildcard options on the "pretty" domains cert either.

I've got the HTTPS set on my Asustor and Jellyfin based on the "pretty" domains SSL cert. I've got my port-forwarding 443 to Jellyfins suggested HTTPS port on my router. I feel like the lynchpin is the FreeDNS subdomain handing off the DDNS request but I'm not sure how to solve it. Any suggestions on how I can get this setup to work? Anyone else run a similar setup where they access their local X port via the web via HTTPS?

Open to similar experiences, suggestions, ideas, pretty much anything at this point.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 8 months ago* (last edited 7 months ago) (1 children)

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]