Post #3927372
2026-07-12 01:49 UTC
If they’re just internal the simplest way is to add another IP on the same interface to whatever is serving your service, then bind the service to that IP and add the entry in DNS.
If for some reason you want to keep everything hosted on one IP, for a reverse proxy, caddy is pretty simple. An example caddyfile would be:
http://service1.devicename.lan/ {
reverse_proxy 1.2.3.4:9005
}
http://service2.devicename.lan/ {
reverse_proxy 127.0.0.1:1234
}
This would also allow you to set https in the future using ACME (dns method if internal only) or your own CA / custom cert.
Replies (1)
-
@laserjet@lemmy.dbzer0.com 2026-07-12 03:29
I don’t really like the idea of having a separate IP for every service. It would need to be configured in the service itself (assuming that is possible for all of them, I don’t know), on the router, and by whatever means you create IPs. Too complex. A lot of people are recommending caddy. All my web services use apache or lighttd. Do I use caddy just for this or do I have to figure out how to move each of them to use this web server? Also does it work for non-web services, like ssh or samba? (Which wasn’t in my original question, I only thought of it now.)