this post was submitted on 15 Aug 2026
41 points (95.6% liked)

Selfhosted

61978 readers
1433 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
 

I've been using Linux for decades, I've worked as a software engineer/architect/sre for around a decade, but networking has always been my biggest gap in knowledge.

I have a local server, I have caddy spun up, a glinet router running their version of openwrt, and I have a domain name purchased through porkbun.

I am looking to setup "local.domain.com" to point to my local server, ideally without exposing it publicly, and enable devices on my home network to be able to access it from that url. Id also like to be able to access containers running on that server by something like "searxng.local.domain.com" or "local.domain.com/searxng" aka without using the port suffix. Id also like to enable https.

I have read so many guides that have fragments of what I need, but nothing that ties enough together to get it working. And with all the options around different domain registers, let's encrypt, reverse proxies, etc, im struggling just a bit.

Are their any guides (prefer text over YouTube, but beggars cant be choosers) that people recommend that encompass the whole process, instead of just pieces? Id like to understand it instead of just fumble through it.

you are viewing a single comment's thread
view the rest of the comments
[–] MarauderIIC@lemmy.zip 4 points 3 weeks ago* (last edited 3 weeks ago)

I am not an expert but I've dabbled on this before some years ago. I'm taking a swing at this not knowing what Caddy is.

If you don't need it exposed publicly, you just need a local DNS server like bind or dnsmasq set up somewhere on the local network, or edit the hosts files on your individual machines to hard code your local network service IPs for those machines. You don't need a purchased domain name to advertise domains locally. It's probably also possible for each machine to advertise its DNS without a central server, but it's outside of my expertise.

Exposing port services with a domain name is a lot trickier but it's doable in various ways. A cursory search says SRV records or setting up a proxy on your local network. It's been a long time since I've attempted this. Optimally your host and client will just be configured to use the correct ports already, like port 80 for http and port 443 for https and whatever the default port is for your other services, so that you can use the same hostname per IP.

Since it's all on your local network I wouldn't bother with encryption/self signed certs, unless your risk profile includes randos on your network sniffing your services (spying on your network traffic while connected to your network).

I don't have guides handy but maybe some of those keywords will help. If you're not staunchly anti-ai, it's a common enough scenario for something like chatgpt to guide you through.