this post was submitted on 19 Jun 2026
37 points (97.4% liked)
Selfhosted
60482 readers
700 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:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
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.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm just curious about the reason for both a reverse proxy and wireguard? If using a proxy (Nginx/etc), I would expect it to be exposed to the internet.
The reverse proxy is infernal. I type sub.domain.tld to get to my internal site. All with automated certs.
Makes it so I dont have to remember IP and port combos
Makes sense, I do something similar but just for things I want to access externally. I started adding some internal only ones but ultimately decided I was too lazy to remember the names and already knew the IPs/ports.
I use a combination of a custom built Caddy Docker container, Technitium for DNS, and DNSWeaver.
Automated DNS Entries, Automated Reverse Proxy entries all with Docker labels.
Sounds like an awesome setup, but I'll stick with remembering the IP:port, its just easier for me to remember numbers than whatever words I used when I set it up.
Hey all good by me. Different setups for different folk!