this post was submitted on 12 Jul 2026
52 points (94.8% liked)

Selfhosted

60664 readers
661 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
52
what's the simple way to map services to subdomains instead of specifying the port number? (lemmy.dbzer0.com)
submitted 3 days ago by laserjet@lemmy.dbzer0.com to c/selfhosted@lemmy.world
42 comments fedilink hide all child comments
 

I have a bunch of services running on my LAN, mostly from a single Debian machine. I access them at URLs like http://devicename.lan:portnumber. I would like to change to http://servicename.devicename.lan.

How it works now: The router (openwrt) sets a static IP per device and the port number is selected by the application or system unit running it.

What is the absolute simplest way to accomplish this? I don't mind if it is managed by the router or by the server machine itself. Hoping for something that can be configured with a text file or web interface or other basic mathod.

These sevices are private, just for me and I have no plans to ever access them externally. I have so far avoided any certificates or SSL or other stuff. I don't use docker and would rather not get into it right now. I like my domain name setup how it is with fake local domains.

Hoping this could be possible without making a whole project out of it.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] ikidd@lemmy.dbzer0.com 2 points 2 days ago (1 children)

In OpenWRT, add an entry in DNSmasq under General - Addresses of /myfakecomain.com/<serverIPAddress This will make every variation of service.myfakedomain.com resolve to that address (assuming you have the hosts on your network obtaining DNS via the OpenWRT router).

Then set up a reverse proxy on that server or whereever you're directing that wildcard. If you have a lot of docker stacks on that machine, I'd suggest Traefik because you can just configure the compose files with the hostnames you want for that service, and it'll update Traefik to redirect that hostname to that container. You can also add bespoke entries to Traefik for non-container services, or other services on your network to redirect towards.

[โ€“] lemmyvore@feddit.nl 1 points 1 day ago* (last edited 1 day ago)

Also, to create the reverse proxy, the most simple setup is to install Caddy and write something like this to its config file (Caddyfile):

a.myfakedomain.com {
  reverse_proxy 10.0.0.1:1000
}
b.myfakedomain.com {
  reverse_proxy 10.0.0.2:2000
}