Hello,

I’m relatively new to self-hosting, please be gentle. If any of what I’m about to say reveals some egregious lack in understanding, I’m listening :)

I have a cute little Synology NAS on our local LAN through a Fritz Box and I’m quite happy with how I’ve been able to figure out stuff on my own so far (bit proud of meself here). Using Portainer to manage Immich, Syncthing, Jellyfin, some arrs, Dashy, jDownloader, tinyMediaManager, in the process of setting up Navidrome, looking into ways to block ads that agree with the Fritz Box, it’s all very nice and cosy.

The thing is that it’s getting a bit difficult to remember what’s on which port. Dashy is at 192.168.178.36:4500, Immich is at 192.168.178.36:2283 etc. Which isn’t a problem per se but it’s not exactly pretty (and I have a husband who isn’t interested in all that stuff at all but might want to use some things if he can remember where they are) (also numbers are scawwy).

So, question: is there a way to make these services reachable from inside the LAN at, say, 192.168.178.36/[service name]? Or, even better, something like //[service name]?

Like, a kind of DNS thing to route [service name] to [(NAS IP:)port]? Maybe? I think? I’m behind a CGNAT so I can’t go through any external service (I think? right?). I know there are ways around that but I don’t need to access my network from the outside for now (and the foreseeable future) so this is lowest priority.

Been trying to figure this out for several days but tbh I don’t even know what I’m looking for, so if anyone can even give me some terms to ask the internet about, that would already be progress and I’d be very grateful. Also, please speak slowly i’m new uwu

  • MentalEdge@sopuli.xyz
    1·
    5 hours ago

    What the other guy said.

    What you do is set up a reverse proxy, which you can then configure to forward connections either using subdomains or subpaths to the relevant ports.

    Subdomains look like jellyfin.domain.com while subpaths look like domain.com/jellyfin. Generally the former is preferred, because the latter often requires that the service you are running allow you to configure the subpath you’re using.

    Subdomains in turn require separate SSL certificates for each one.

    You can also set up domains that only work inside your LAN, using self-signed certificates. No external or public domain needed.