Cloudflare is just so nice. Handles ssl for all your sites automatically.
I'd say to start with CF tunnels unless you need non-web based applications. Cloudflare tunnels require you to have a domain, though.
It has the added benefit that you have network monitoring, logging and some filtering for security that they do on top and you get to manage everything from their web interface.
be warned that the first time can be a bit confusing, but since it's done using their web interface it's easier than if you have a problem making wireguard work.
- Create a tunnel with a public hostname that will be the url to access that service. During the creation of the hostname specify you want it protected by L7 application firewall.
- Create a new self-hosted application in cloudflare application section and for starters use the default login email and in rules specify the list of emails that are allowed to login
you should now be able to access your application from anywhere.
Alternatively, if you have a DNS server in your home network you can add a private IP range to your tunnel. Let's say 192.168.0.0/24. Then when you connect with their pseudo-VPN (cloudflare warp or cloudflare ONE) you can directly use your home network's ip address from that device. If you tell your device to use a local DNS server that resolves your internal services, you'll be able to connect to them that way.
This is he best Cloudflare guide I've seen so far. Thank you!
Thanks fro this little guide, might come in handy :)
My advice: only forward ports 8080 and 443, then make sure that you have fail2ban or crossed properly set up on your reverse proxy. After that, you are pretty much fine as long as you keep on top of updating your containers.
I would be careful about which apps you proxy. Idk why you need to access the admin portal for pi hole worldwide. If you really want to do that, you should set up a vpn.
My router supported OpenVPN out of the box so I just use that and have remote connections disabled in all of my software
I'm curious what the other, more advanced users here have to tell me about it because I'm still new to the self hosted stuff and that was the first thing I thought of to do
Wireguard is just much faster connection-wise. Built into the kernel too. Since it came out I haven’t gone back to openvpn.
Nothing wrong with openvpn otherwise. More config options.
Something like Tailscale makes wireguard setup dead easy.
This is what I use too. Also using the provided dynamic dns server just makes this dead simple and has been working for years. Is there a good reason to switch?
I want to have the same setup as you! Do you have any guides on how you did it?
Twingate has been my go to. It’s amazing. Highly recommended.
Looks very similar to tailscale, thanks :)
Selfhosted
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.
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!