this post was submitted on 17 Jun 2023
24 points (96.2% liked)

Selfhosted

40023 readers
1276 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
 

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
[–] novarime@sopuli.xyz 1 points 1 year ago (2 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 1 year 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

[–] captainjaneway@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

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