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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I have a $5/mo VPS that my domain points to. It runs caddy reverse proxy to my homelab over wireguard. If my home IP changes, the wireguard 'server' has the the IP of the VPS wg 'client' configured as the Endpoint, with no endpoint set on the VPS. It will switch over pretty quick.
https://anders94.medium.com/wireguard-config-for-the-initiated-2b1cc5f2b1ee
DynDNS short for dynamic DNS is what you want. But IPv6 only websites are unfortunately even in 2026 still not accessible by many people due to their ISP only supporting IPv4.
Probably reverse proxy too if it's really unstable
Assuming reliability is the priority I would suggest going with Tailscale Funnels or a cheap VPS acting as intermediary.
I don't have a lot of experience with dealing with GCNAT, but perhaps you could look into some solution with UPnP or RFC 6887.
When IPv6 was first created, the dream was that your machine would get a new IP address any time the whole network felt some need for that. The idea was, as someone added a network, we may need to change the way your systems are numbered in order to make the backbone routing a lot easier to fit in memory. This hasn't seemed to work out, but that was the dream.
Assuming you are not in a CGNAT, which is common for mobile networks: DNS with low TTL such as FreeDNS, pointing to your IP. And ofc, if you have a router in between, port-forwarding.
Otherwise, a VPN such as Tailscale. But you would need to install it on all your devices.
Otherwise, for HTTP(S) web services, a reverse-proxy such as CloudFlare.
Does cgnat even exist for ipv6
Whoa, FreeDNS is a killer, I wish I knew about it before! I have domains to donate probably (unless they expired lol). I sure need to try that.
DNS is the way around it. But, the caveat is that while you can update your DNS entry as often as you like, itll often be cached on intermediate servers for an unknown amount of time. Expect a downtime of anywhere from a few minutes to days everytime your address changes.
So how does this work then, I host DNS and it pushes my data to other DNS servers around the net every time my IP address changes? Can you share an example of how could be set up?
You run a dynamic DNS script. It reaches out to the DNS server (provided by whoever registers your domain name) every five minutes and says "my IP is x.x.x.x".
The problem is that it takes a few minutes to update when it changes. That might not fit your use case.
No, typically you use the DNS server of the domain provider.
Hosting your own DNS server is possible, but if you don't have a static IP address the other DNS servers will have no idea which server to ask when your IP changes, so in this specific scenario it wouldn't work. And in general it isn't really worth it as you get a DNS server with your domain included.
I tested a 5G connection as failover for a few weeks.
My homeserver connected to a very small VPS, routing traffic through Wireguard. So the public IPv4/v6 remained constant, even when the gateway switched between WAN connections.
Yeah, using VPS to route traffic is an obvious solution, I'm thinking about it as the last resort here.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| CGNAT | Carrier-Grade NAT |
| DNS | Domain Name Service/System |
| HTTP | Hypertext Transfer Protocol, the Web |
| IP | Internet Protocol |
| NAT | Network Address Translation |
| VPN | Virtual Private Network |
| VPS | Virtual Private Server (opposed to shared hosting) |
[Thread #258 for this comm, first seen 27th Apr 2026, 09:20] [FAQ] [Full list] [Contact] [Source code]