this post was submitted on 25 Oct 2025
60 points (98.4% liked)

Selfhosted

52586 readers
485 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
60
Internal domain and reverse proxy (lemmy.zip)
submitted 2 days ago by jobbies@lemmy.zip to c/selfhosted@lemmy.world
30 comments fedilink hide all child comments
 

I'm going round in circles on this one.

What I want to do is:

  • serve up my self-hosted apps with https (to local clients only - nothing over the open web)
  • address them as 'app.server.lan' or 'sever.lan/app'
  • preferably host whatever is needed in docker

I think this is achievable with a reverse proxy, some kind of DNS server and self-signed certs. I'm not a complete noob but my knowledge in this area is lacking. I've done a fair bit of research but I'm probably not using the right terminology or whatever.

Would anyone have a link to a good guide that covers this?

you are viewing a single comment's thread
view the rest of the comments
[–] irmadlad@lemmy.world 3 points 1 day ago (1 children)

I'm not sure if this is a complete fit for you, and some people have animosity towards Cloudflare, however check out Cloudflare tunnels. To use Cloudflare tunnels tho, you need a proper domain name. Get one from NamesCheap and switch the NameServers to the ones assigned to you when you sign up for a Cloudflare tunnel account. I bought one for $1.75 USD.

The beauty of using Cloudflare is that you don't have to 'punch holes' in your network defenses. You don't have to worry about opening ports or having to secure them. You can create subdomains, and Cloudflare handles the certs. For instance, you could have:

  • app1.mycoolserver.com ---which points to--->http://localhost:45684/
  • app2.mycoolserver.com ---which points to--->http://localhost:59487/

When you get everything set up, overlay Tailscale on the server, Jack's a doughnut, Bob's your uncle. The free tier Cloudflare Tunnel package is quite generous and has all manner of bells and whistles, most of which I didn't need, but are there if you do.

I've used Caddy before and still do on a couple of test VPS, and derivatives like Pangolin. They are great and do the job quite well. It is a case of 6 of this and half dozen of the other. It seemed to me, tho Cloudflare had a bit of a learning curve, once set in place, it's a little easier than Caddy. They're all pretty decent packages.

[–] PeriodicallyPedantic@lemmy.ca 1 points 12 hours ago

They're looking for local access network access only