Custom Local Domains

novarime@sopuli.xyz to Selfhosted@lemmy.world – 19 points –

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?

39

You are viewing a single comment

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

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

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.

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

Just to clarify a bit further. You browser doesn't specify ports in the URL because HTTP and HTTPS have basically coopted the 80/443 ports. You could have a website running an HTTP server on another port like 3000. But then you'd need to specify the port in the URL since the browser - by default - is looking at 80/443 and not 3000.

You should be able to configure the port for your Jellyfin server. I'm not a Jellyfin user, but most applications allow you to pick a port to run it on. So you'll have to change the port to port 80 and then expose that port on your docker container in the docker-compose file.

Edit: actually now that I think about it... You could just point your local port 80 to the docker container port. I forget the port mapping schema but it's something like

ports:
  - 80:1234

You might have to flip the order of the ports. But basically that example above is trying to map port 80 to port 1234. If that fails, you might have port 80 being used by another application on your computer and you'd either have to shut that app down, pick a different port for that app or you're back to picking a different port for Jellyfin

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.

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.