Cloudflare is bad. Youre right.
Cloudflare is bad. Youre right.
Centralization is bad for everyone everywhere.
That bring said... I just moved my homeserver to another city... and I plugged in the power, then I plugged in the ethernet, and that was the whole shebang.
Tunnels made it very easy. No port forwarding no dns configuration no firewall fiddling no nothing.
Why do they have to make it so so easy...
You're viewing a single thread.
I use cloud flare tunnel for my home server too. Are there any viable and somewhat easy alternatives?
6 0 Reply11 0 ReplyDNS names are restricted to your tailnet’s domain name (node-name.tailnet-name.ts.net)
I guess that's fine for some. Not a compromise I'm willing to make though.
4 0 ReplyAs soon as I can use my personal domains with tailscale funnel I'll be switching, I like tail scale a lot
4 0 Reply
Get a cheap VPS and set up a VPN of your choice.
8 1 ReplyJust make sure the VPS will shut down if the bandwidth is exceeded rather than giving you a big overage charge.
7 0 Reply
Once configured, Tor Hidden Services also just work (you may need to use some fresh bridges in certain countries if ISPs block Tor there though). You don't have to trust any specific third party in this case.
5 0 ReplyWouldn't that be slow?
2 0 ReplyIt would. But it's a good option when you have computationally heavy tasks and communication is relatively light.
3 0 ReplyYes. Very slow. And only accessible from tor clients or tor2web/onion.to-like constructions. Which adds additional delay and errors.
There are things for which onion addresses are the right solution. This is not one of them.
3 0 Reply
DynDNS? I'm not 100% sure what CF Tunnel does, but from my 2 min reading it seems that DynDNS would accomplish what OP described just as well.
7 3 ReplyIt might help to read it once more then 🙂
8 1 ReplyOh, it's way more than what any dyndns can do.
3 0 Reply
Port forwards in the router + DynDns.
3 0 Reply