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?

      • novarimeOP
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        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
          link
          fedilink
          arrow-up
          8
          ·
          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

          • novarimeOP
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            Gotcha. I have nginx proxy manager on the go and I’ve heard caddy is simple, so i’ll see how I get on. Thanks for the advice.

        • Captain Janeway@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          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

    • novarimeOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      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
        link
        fedilink
        arrow-up
        7
        ·
        edit-2
        1 year 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.

        • novarimeOP
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Cheers. I appear to have something of a mental block with revese proxies. I’ve used them successfully, but couldn’t definitively say I understood them enough to get on with things. I’ve always had some niche condition on my end that was slightly different to the guide or video I was watching which snafued the process.

          I have nginx proxy manager currently up and running and set up wildcards, but no dice on actually mapping anything properly, and there are multiple layers where things can be misconfigured, so diagnosis takes time, which is hard to come by at the moment.

          What this post has taught me, is that I need to just spend a weekend playing with reverse proxies enough til they’re sunk in. Thanks again for the advice.