Check into Cloudflare Tunnels.
this post was submitted on 14 Jun 2023
13 points (93.3% liked)
Selfhosted
39950 readers
470 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: 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!
founded 1 year ago
MODERATORS
Was going to suggest CloudFlare as well. At the very least just setup your DNS with there nameservers and benefit from CloudFlare proxies on the IP addresses.
But tunnels is pretty sweet.
Cloudflare tunnels are great but OP may not want to have to authenticate each user to their services.
Agreed, but they could always setup a bypass rule.
True, in that case CF tunnels may be easier to manage due to fewer moving parts to configure. Good point!
Cloudflare free tier + a reverse proxy will set you straight. You can add subdomains for your services as A records in Cloudflare off of your root domain, i.e. lemmy.yourdomain.tld, personalsite.yourdomain.tld, images.yourdomain.tld.
When doing this, enable the Cloudflare DNS proxy which will route DNS requests to your origin service through Cloudflares's CDN. This essentially "hides" your public IP as anyone doing a nslookup lemmy.yourdomain.tld will get Cloudflares's IPs back as a response.
Once you've done this, you can break everything back out to it's respective backend via a reverse proxy. For example, lemmy.yourdomain.tld gets passed to 192.168.0.10, personalsite.yourdomain.tld gets passed to 192.168.0.20, etc.
That's sounds so much simpler than what I am doing right now. Right now I have a digital ocean droplet server running openvpn and I have any servers I want open to the internet connecting to that openvpn server as a client. I then NAT all incoming traffic to the servers I have with iptables as if the droplet is a router. Is it much easier to setup a cloudflare tunnel? Or am I basically accomplishing the same thing? Will I be able to run all the other services I have because I'm not just web hosting? I also do not have a static IP.
Since I didn't want to use cloudflare I use a free oracle vps with tailscale and a reverse proxy on it. Then thru tailscale all services from home can go to the proxy without forwarding any ports and services can be accessible
Cloudflare tunnels or a reverse proxy with Cloudflare DNS would be much easier to manage IMO. What you're doing will work but it seems like you have a lot of moving parts in your setup which can lead to errors creeping in.
With both proposed setups you should be able to pass non web-based traffic to their respective backends. In nginx that would look something like the following:
server {
listen 443 ssl http2;
server_name service.yoursite.tld;
location / {
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host:$proxy_port;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://<IP of your service>:<port>;
}
}
With Cloudflare tunnels you can setup a VM as your tunnel termination point and configure ingress rules to pass traffic where it needs to go, similar to this:
tunnel: <Tunnel UUID>
credentials-file: /root/.cloudflared/<Tunnel credentials>.json
ingress:
- hostname: service1.yourdomain.tld
service: http://192.168.0.10:80
- hostname: service2.yourdomain.tld
service: ssh://192.168.0.20:22
- service: http_status:404 # This is a catch-all rule to handle unmatched ingress traffic
One thing you can do for your public IP is use something like inadyn to update cloudflare with your public IP when it changes. Inadyn is super lightweight and will make sure, +/- 5 minutes, that your public IP is up-to-date with Cloudflare.
As others have pointed out,
- a VPN (so that your outbound traffic comes from your VPN endpoint, not your bare IP address)
- a reverse proxy server
I use a router from GL-iNet to run the always-on VPN, and rathole for a reverse proxy. Both the VPN and the reverse proxy terminate at $4/mo VPSes.
You need a VPN or a reverse proxy or similar for this.
What you want is either a service that gives you an IP address unrelated to your physical location (a VPN), or a machine that is willing to accept connections for you and forward them transparently to your machine (a reverse proxy).
You can set up your own VPN to proxy connections by getting a host from ~any hosting service and running something like OpenVPN on it.
It's not a perfect solution but, and requires some sort of VPS, but you could run a reverse proxy on a VPS, site-to-site vpn from the VPS to your Homelab, and point your reverse proxy to the services over said VPN.
I do something like this. However, it doesn't completely hide your IP.
So the software you're looking for is a Reverse Proxy (nginx, traefik, caddy... etc. there are tons), a VPN (Wireguard, OpenVPN, StrongSwan (IPsec)), and more than likely some sort of VPS. My Linode VPS costs me $5 a month. They constantly have sponsor deals that will get new users free time though.
Hope that gets you started.
I thought that solution completely ideas the homelab IP. Why/How is it visible?
Well the VPN connection depending on what technology you use will still need to connect to the Public home IP, which is probably dynamic, which means that you'd probably need to use Dyanmic DNS to keep it connecting properly.
As far as someone just connecting to the reverse proxy the Home IP shouldn't be visible at all. I just mean it wouldn't hide well were someone really trying to find it.
I'm not sure I'm explaining this well. I haven't had coffee yet.
I see, thanks for the explanation.
If I understand correctly, with a service like Tailscale that doesn't require Dynamic DNS even if your IP changes, there wouldn't be a risk of revealing the IP, right?
Well in that case, tailscale is running as a daemon, so it effectively is doing it's own little Dynamic DNS.
I suppose the point I'm trying to make is SOMEONE has to know your public Home IP. In the case of using tailscale, it would be the tailscale servers. But you would be correct that I don't believe it would be published to any public DNS servers.
In my case, I'm using cloudflare for DDNS.
The solution I describe comes with a bit of risk acceptance (just like anything else really).
Got It! Thank you very much.
ingress traffic to lemmy is obvious (CF -> reverse proxy, for example) but what about egress traffic i.e. federation requests? I kind of poked around lemmy backend / issue tracker but didn't find any way to setup a HTTP proxy for backend requests, so your real IP would be visible to any instance you contact, I think.
Look into getting a VPS to proxy things through using either wireguard+DNAT, rathole or SSH tunneling.
Cloudflare DNS Proxy sounds like exactly what you're looking for, where cloudflare acts as the DNS middleman and responds with their own IPs, while forwarding all traffic for the site(s) to your public IP space
view more: next ›