Human-readable forwarding addresses for ports on Synology NAS? (feddit.org)

submitted 2 days ago by Lumidaub@feddit.org to c/selfhosting@slrpnk.net

5 comments fedilink hide all child comments

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

top 5 comments

sorted by: hot top new old

[-] Wxfisch@lemmy.world 3 points 2 days ago

What you want is a reverse proxy, something like Trafik or Nginx Proxy Manager makes it really easy to setup and even then lets yous apply a lets encrypt certificate for HTTPS support getting rid of the browser warnings.

[-] MentalEdge@sopuli.xyz 2 points 1 day ago* (last edited 1 day 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.

[-] umbra@slrpnk.net 1 points 21 hours ago

You can also have SSL internal only domains without self signed certificates with something like acme.sh doing the DNS-01 challenge. It requires a domain registrar with an API but you be able to get the certificate and serve it with your reverse proxy so no need to manage your self signed certs on every device.

You can also get a wildcard cert so you dont need to force a reissue every time you set up a new service

[-] xylol@leminal.space 1 points 1 day ago

All these years I've just bookmarked all the containers I run

[-] harsh3466@lemmy.ml 1 points 1 day ago* (last edited 1 day ago)

I learned the setup from this video. It works great.

this post was submitted on 30 May 2026

9 points (90.9% liked)

Self-hosting

4368 readers

1 users here now

Hosting your own services. Preferably at home and on low-power or shared hardware.

Also check out:

founded 4 years ago

MODERATORS

poVoq@slrpnk.net

sam_uk@slrpnk.net