A reverse proxy will achieve what you're looking for, yes. I do precisely what you're describing. I use "local DNS" on my pihole, with CNAMEs for each service pointing to my server IP address. I'm running Caddy on the server, specifically this (because my services are running in Docker containers): https://github.com/lucaslorentz/caddy-docker-proxy

As far as a "dashboard" app, you have options there as well. I'm using Heimdall currently, but Homarr also looks pretty nice.

Lots of good suggestions, but no one has mentioned the simple option of browser bookmarks?

Any good browser has built in sync, so bookmarks are already shared across all of your devices.

I mean, if you're problem is just remembering to type "10.0.0.100:8080" you could just have browser bookmarks. But that's not very selfhosty. 😁

Personally, I've got a bit of #1 and #2 going on.

I've got Nginx Proxy Manager in docker that rev proxies pretty much everything and adds SSL on top. I am running an inside DNS zone, so I have a bunch of CNAMEs that all point to the host running NPM. Lastly, I'm using Dashy as the front end to it all.

Heimdall

Short answer: something like nginx proxy manager with a single wildcard dns entry makes this super simple.

I'm using Homer with links to all services based on ip. I've also added a local Dns entry to pi hole.

Ill just recommend homepage as dashboard

I would personally run reverse proxy separately since it's more critical than dashboard. I personally run traefik. For dashboard check homarr if you are running other arr apps I think it is an interesting choice.

If you are running everything in containers then there’s a very simple and straightforward solution for this. Run your reverse proxy (NPM, Caddy, whatever) on two network (internal and external or whatever you want to call them). In the external network is where you will map your host port to the reverse proxy container. For example, on NPM it’s 81 so you map host 81 to container 81. You should then be able to go to http://localhost:81. The internal network will be where your reverse proxy will talk to your other two web services you want to run so make sure you add your other services to this internal network.

On your DNS (personally I run PiHole) point your service name (as guard) to the IP of the host running your reverse proxy. Do an nslookup on the name to make sure you actually get the right IP for the name you want.

Login to your reverse proxy and configure a proxy host to point to the name of the container and the correct port. Since the reverse proxy is on the same “internal” network, they should be able to talk to each other via names rather than IPs.

Test your connection to the service on your browser.

Another solution (less technical but much faster) would be to runa dashboard service like Heimdall then just add a “link” to the service you want and the port it’s running on. Then you will have a single link to click on that will take you where you want without typing manually. You could even add the dashboard as your browser default page on startup.

There are other ways to skin this cat but these two solutions will get you where you want to go quickly.

According point 2: I choose homepage over Heimdall. It has more direct integrations (e.g. Homeassistant, Synology, Paperless-ngx, Warchtower…) where you can display specific information directly on your dashboard. It is easily set up by a couple .yaml files. You can find lots of examples online and in the documentation.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

6 acronyms in this thread; the most compressed thread commented on today has 11 acronyms.

[Thread #70 for this sub, first seen 20th Aug 2023, 01:25] [FAQ] [Full list] [Contact] [Source code]

Set up a domain with a main site that has links to your different services, then set up reverse proxies so you can put certificates on them and serve them all on port 443. If your WAN IP is relatively static then you can forward ports 80 and 443 to your server and use your own domain, if not you can use something like FreeDNS. Or skip the last bit if you don't need WAN access.