this post was submitted on 25 Oct 2023
31 points (89.7% liked)

Selfhosted

40006 readers
742 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
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
31
A few Questions about reverse proxies and running your own Jellyfin server (lemmy.world)
submitted 1 year ago by [email protected] to c/[email protected]
23 comments fedilink hide all child comments
 

First things first, the setup is currently up and running. but i would like to modify it to use a reverse proxy through my personal domain.

Currently, i'm using an old pc with Truenas and a jail with jellyfin in it. i'm connecting to it with the free Fritz!Box VPN service.

but that's stupid and slow. so i've bought a domain at godaddy.com. but i don't understand the principle of whatever is managing the domain knowing the public IP-adress of my server. i've heard of Caddy, but it's also running locally, so i don't understand how i connect the pc to the domain.

if anyone could simplify this down for me, it'd be very helpful.

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

To connect your domain to your IP use godaddy website, it should have a section where you can configure a dns entry, you can specify an IP address (your public IP) and, after a while, every device on the internet connecting to YOURDOMAIN.COM will be send to your home. If godaddy doesn't offer a dns service you have to buy it somewhere else like on cloudflare, here I think you will need to prove that you own YOURDOMAIN.COM and then setup your IP in the dns. If you don't have a static IP you need a DDNS (Dynamic DNS). After that you open the port number 443 on your home router so that https requests will be send to a device of your choice, this device will host your reverse proxy, the reverse proxy binds a domain name (the one you brought) or a sub domain to a service of you choice on your local network, doing this you don't expose the local server directly and you need to open a single port only.

I bought a domain on namecheap.com and it has a configurable dns built in so I hope that godaddy has one too. I use Caddy as a reverse proxy for my jellyfin instance instead of Nginex, I think that they are both valid, another thing other people said in the comment is to access jellyfin via wireguard tunnel and I confirm that is the best choice if you don't have specific needs, let me explain. The reverse proxy automatically generates ssl certificates using let's encrypt allowing you to cast from an android phone to a Google chromecast (this seems to be the only way to do it and works very well for me). I also configured other services on caddy, in my setup I block every request to the reverse proxy that doesn't arrive from inside my local network (except jellyfin so I can use it remotely), I know that it's not the intended use of a reverse proxy but it makes some things possible that otherwise will need more configuration:

  • I have two separate networks in my home, my reverse proxy has a double interface so I can easily access all services from devices on the main network.
  • I don't need to configure local dns rewrites to my services neither I have to add exceptions for dns rebind inside my router, I simply add a new rule to caddy and it just work.
  • I have https for every service on my network without annoying messages on the browser.

If you think this lazy use of the reverse proxy could be a problem please tell me your thoughts!