this post was submitted on 17 Jun 2023
13 points (93.3% liked)

Selfhosted

60758 readers
194 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

How do you guys set internal domains?

Say i dont want to type 192.168.1.100:8096 and want a url instead, say jellyfin.servername - how would I go about that? I don't want it exposed online via reverse proxy. I don't need certs. No port forwarding on the router.

How do I type 'jellyfin.servername' into a browser and being up the jellyfin dashboard?

you are viewing a single comment's thread
view the rest of the comments
[–] Lee@kbin.social 16 points 3 years ago (2 children)

If you have your own DNS server you can set a hostname there like 'jellyfin.myserver' and have that accessible from your internal network. If you want to do so on your PC you can edit your hosts file to add a custom entry. https://www.hostinger.com/tutorials/how-to-edit-hosts-file

[–] jjakc@lemthony.com 8 points 3 years ago (1 children)

Keep in mind you still need to specify the port with this method.

[–] novarime@sopuli.xyz 2 points 3 years ago (1 children)

Yeah, how and where? In the docker compose? I have a dozem containers and is love if they were all a.server. b.server, c.server. How can I do this? Pihole DNS records don't do anything at the port level.

[–] jjakc@lemthony.com 6 points 3 years ago

Sorry I meant in your browser. Yes dns does not point to ports.

You would have to use some sort of reverse proxy that is only accessible from internal networks

[–] novarime@sopuli.xyz 1 points 3 years ago (1 children)

It's the port that's tripping me. How do I point jellyfin to that domain? It's on docker on port 8096 - the hostname isn't the problem, it's the container.

[–] plo@kbin.social 4 points 3 years ago* (last edited 3 years ago)

Ah okay. You need some sort of reverse proxy.
I really like caddy. Using it with caddy-docker-proxy in docker-compose makes it quite nifty:

`version: '3.7'
services:
whoami:
image: containous/whoami
networks:
- caddy
labels:
caddy: http://whoami.mylab.home
caddy.reverse_proxy: "{{upstreams 80}}"

networks:
caddy:
external: true`

Just make sure to explicitly use 'http' instead of 'https'. That way it won't try to create certificates.