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?
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:1234You 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: trueJust make sure to explicitly use ‘http’ instead of ‘https’. That way it won’t try to create certificates.
I use a pi hole instance for this. I just point all the subdomains at my ngnix server and reverse proxy everything through that
You don’t need to expose it to the web to use a reverse proxy. You can use traefik, caddy, nginx, or any other reverse proxy to serve
IP:PORTondomain.tld. You can use 80 or 443 as you’d like.If you’re using docker, it’s even easier. How are you hosting your jellyfin?
PiHole as your DNS resolver. LocalDNS mapping whatever hostname you want to whatever IP you want.
Because I use Nginx Proxy Manager internally - then most of my hostname point to the Nginx IP addressdeleted by creator
The host isn’t really the issue. It’s the container. How do I access the container with a name rather than number.
deleted by creator
deleted by creator
I currently use a custom filter/rewrite in AdGuard Home (similar to pihole).
An alternative to running a central dns server is to use mDNS. You can install a daemon on each server that you want to access via hostname, and then clients know that ServerName.local domains should be resolved using mdns. They send out a dns query to a local multicast IP, the daemon on the servers receives the query and the appropriate one responds. By design it’s local only.
You’ll need certs if you want to use a Chromecast in certain circumstances, btw.
Theres a few ways to do that but this is the easiest way it to use a caddy reverse proxy & a local dns server (like pihole or adgarud home)
register servername.local in pihole/adguard https://discourse.pi-hole.net/t/howto-using-pi-hole-as-lan-dns-server/533
example caddyfile:
# you must set 'http://' or caddy may error when getting a ssl cert http://jellyfin.servername.local { reverse_proxy 192.168.1.100:8096 }There are a lot of comments, and I didn’t feel like reading them all to see if someone said this, but you could use pi-hole to host a dns server on your network that forwards requests to a normal dns server but has a list of custom exceptions. This could be used for that as well as being a great ad blocker for any device that lets you change dns settings. (This includes a lot of smart tvs and things)
Wolfangs Channel had a video about that a few weeks ago: https://www.youtube.com/watch?v=qlcVx-k-02E
I didn’t try it myself yet, but judging from his other videos, he’s not a complete idiot, so I assume it’s solid advice.
If externally available - i use domain. If local - by ip:port. I find it easier to rely on firefox bookmarks and their folders lol.
Reverse proxy and local DNS. Just add the domains you want to your DNS and point them at the reverse proxy.
Thanks. It’s the reverse proxy part i’m scared of. For some reason theyve just never clicked with me.
I get that, they’re a bit confusing at first. I’d highly recommend looking at Caddy, it’s configuration is very simple. Really all you have to do is pick a domain name and point it at the correct port. If you’re only accessing locally you don’t even need to buy a domain.
Yep! If you have a local DNS server such as a pihole you could just manually add watch.tv to your local dns records and set the IP as your servers IP. If you don’t have a local DNS server, you can just add it to your hosts file.
Once you do this, any requests to that domain will go to your reverse proxy, which if set up correctly will send you to Jellyfin.
You need to set up a local DNS server with a
.servernamezone and point your machines to it. You’d add an external DNS server like 1.1.1.1 as forwarder to allow internet traffic to still resolve.
