Hey is there any alternatives to CloudFlare reverse proxies? I want to hide my server IP but not share everything with CF...

top 50 comments
sorted by: hot top controversial new old
[-] chiisana@lemmy.chiisana.net 22 points 1 month ago

What is your objective for ‘hide server IP’?

Privacy to disconnect your identity from the service? There is no solution to this. Full stop. Even with Tor, the state backed acronym entities will figure it out if you get on their radar.

If your objective is to keep your service online, you’re going to be hard pressed to find cost effective alternatives… Commercial solutions are expensive, like, “if you have to ask about the price, you can’t afford it” expensive.

Alternatively, you can try to roll your own by having many many proxy servers yourself… but if you’ve got a target on your back, you’ll never have enough instances; DDOS-as-a-Service is much cheaper than the amount of reverse proxies required to keep your service online.

There’s probably other use cases, but chances are, you’d still be hard pressed to find a solution that’s cost effective.

load more comments (12 replies)
[-] foggy@lemmy.world 20 points 1 month ago* (last edited 1 month ago)



Kinda depends on what's going on, price point, etc. is this for DDOS purposes?

You do not need a CDN, but you have users. So, is this for like, a Plex server, serving friends in a similar geographic region?

What's the use case? That will greatly help us answer.

[-] TCB13@lemmy.world 8 points 1 month ago* (last edited 1 month ago)

@foremanguy92_@lemmy.ml ,

Step 1: get a cheap VPS, or even a free one (https://www.oracle.com/cloud/free/)

Step 2: If you've a static IP at home great, if you don't get a dynamic DNS from https://freedns.afraid.org/ or https://www.duckdns.org/

Step 3: Install nginx on the VPS and configure it as reverse proxy to your home address. Something like this:

server {
    listen 80;
    server_name example.org; # your real domain name you want people to use to access your website
    location / {
        proxy_pass http://home-dynamic-dns.freeprovider... # replace with your home server IP or Dynamic DNS.
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_redirect off;

Step 4: Point your A record of example.org to your VPS.

Step 5: there's a potential security issue with this option: https://nginx.org/en/docs/http/ngx_http_realip_module.html#set_real_ip_from and to get around this you can do the following on the home server nginx config:

http {
        real_ip_header    X-Real-IP;
        set_real_ip_from  x.x.x.x; # Replace with the VPS IP address.

This will make sure only the VPS is allowed to override the real IP of the client.

Step 6: Once your setup works you may increase your security by using SSL / disabling plain HTTP setup letsencrypt in both servers to get valid SSL certificates for real domain and the dynamic DNS one.

Proceed to disable plain text / HTTP traffic. To do this simply remove the entire server { listen 80 section on both servers. You should replace them with server { listen 443 ssl; so it listens only for HTTPs traffic.

Step 7: set your home router to allow incoming traffic in port 443 and forward it into the home server;

Step 8: set the home server's firewall to only accept traffic coming from outside the LAN subnet on port 443 and if it comes from the VPS IP. Drop everything else.

Another alternative to this it to setup a Wireguard tunnel between your home server and the VPS and have the reverse proxy send the traffic through that tunnel (change proxy_pass to the IP of the home server inside the tunnel like proxy_pass This has two advantages: 1) you don't need to setup SSL at your home server as all the traffic will flow encrypted over the tunnel and 2) will not require to open a local port for incoming traffic on the home network... however it also has two drawbacks: you'll need a better VPS because WG requires extra processing power and 2) your home server will have to keep the tunnel connected and working however it will fail. Frankly I wouldn't bother to setup the tunnel as your home server will only accept traffic from the VPS IP so you won't gain much there in terms of security.

[-] chiisana@lemmy.chiisana.net 0 points 1 month ago

Say someone wants to take your service down, you've got 500Mbits line at home ISP, and 10Gbits on your VPS; they sends 1Gbits of traffic to your VPS, your VPS happily tries to forward 1Gbits, fully saturating your home ISP line. Now you're knocked offline.

Say someone discovers the actual IP, dropping traffic from anything else other than the VPS doesn't help if they just, again, flood your line with 500Mbits of traffic. The traffic still flows from the ISP to your gateway before they could be dropped.

Say someone wants to perform SQL injection on your website, there is no WAF in this stack to prevent that.

Say someone abuses a remote code execution bug from the application you're hosting in order to create a reverse shell to get into your system, this complex stack introduced doesn't protect that.

You've provided a comprehensive guide, and I don't want to single you out for being helpful, but I must ask: What problem does this solve, and does OP actually have the problem this stack can solve? From the replies we've seen in this thread, OP doesn't have sufficient understanding to the full scope of the situation. Prescribing a well intended solution might be helpful, but it gives a false sense of security that doesn't really help with the full picture.

[-] Auli@lemmy.ca 4 points 1 month ago

The chances someone is going to DDOS a residential IP is small as important as you think you are nobody cares about taking down someones plex server.

[-] TCB13@lemmy.world 1 points 1 month ago

You aren't wrong but the things you're mentioned are always an issue, even if he was running the entire website on a VPS.

VPS happily tries to forward 1Gbits, fully saturating your home ISP line. Now you’re knocked offline.

Yeah, but at the same time any VPS provider worth it will have some kind os firewalling in place and block a DDoS like that one. People usually don't ever notice this but big providers actually have those measures in place and do block DDoS attacks without their customers ever noticing. If they didn't hackers would just overrun a few IPs and take all the bandwidth the provider has and take their all their customers down that way.

I'm not saying anyone should actually rely only on the VPS provider ability to block such things but it's still there.

The OP should obviously take a good read at nftables rate limiting options and fail2ban. This should be implemented both at the VPS and his home server to help mitigate potential DDoS attacks.

Say someone abuses a remote code execution bug from the application you’re hosting in order to create a reverse shell to get into your system, this complex stack introduced doesn’t protect that.

It doesn't and it was never supposed to mitigate that as the OP only asked for a way to reverse proxy / hide is real IP.

[-] chiisana@lemmy.chiisana.net 1 points 1 month ago* (last edited 1 month ago)

You aren’t wrong, but that’s also the point… It makes no difference if they’re securing a VPS or their own network. In fact, they’d need to secure both systems — and I’ve seen so many neglected VPS’s in my time… I’ll be the first to admit: myself included.

There are very valid reasons to need a tunnel; CGNAT, ISP level port blocking, network policies (ie campus dorm), etc etc etc. However, if you read the other replies, this doesn’t seem to be the case here, and OP doesn’t seem to even know why they’re hiding their IP. They just wanted to do it because of some loose notion that it may be nice since they’re opening up their port.

For someone in that situation, introducing a whole stack that punches through the firewall via an VPN or alike introduces way more risk than just securing down the gateway directly, and handle the other issues as they come up.

[-] rand_alpha19@moist.catsweat.com 8 points 1 month ago

You could try Tailscale? It creates a secure tunnel to your server so you don't have to connect it to the internet. Not sure if that checks all your boxes though.

[-] machinin@lemmy.world 1 points 1 month ago

I was looking into Tailscale, but it got me a little worried. I'm not very knowledgeable, so I hope someone can correct me

They don't allow ssh, so you have to give your keys over them and they manage your ssh connection? That seems idiotic. Surely that can't be correct?

I'm my use case, I was wanting to rsync to an off-site Synology from a Linux box. Synology also doesn't allow ssh over their VPN service - frustrating.

[-] folkrav@lemmy.ca 3 points 1 month ago* (last edited 1 month ago)

Pretty much the only thing I use Tailscale for is remotely SSHing from my phone to my home NAS, and they definitely don’t manage my keys. They do have a “Tailscale SSH” feature I don’t use…

[-] rand_alpha19@moist.catsweat.com 3 points 1 month ago

I'm not really knowledgeable about it, but there is an article from Tailscale that explains how they use SSH (basically it creates a separate SSH server specifically for Tailnet traffic). From what I understand, this feature is relatively new.

You may also want to look into Tailnet lock.

[-] node815@lemmy.world 1 points 1 month ago

You can always use something like SSHwifty It retains your logins through your browser's session data and never on your server, but it will allow you to remote into your local system from anywhere on the WWW if you desire to do so. With Tailscale, once you are connected into your Tailnet, you can pretty much SSH into any of your devices as long as the subnet sharing flag is turned on I believe. I've never had any issues with mine not allowing any SSH connections.

[-] foremanguy92_@lemmy.ml 0 points 1 month ago

But I need to configure something on the client side... I want people to access my server as they access their Instagram account

[-] rand_alpha19@moist.catsweat.com 3 points 1 month ago

Then you can't "hide" your server IP without a VPS/VPN set up. Maybe I'm not understanding what you're asking? Your public IP is visible to any machine you connect to and that includes Cloudflare's servers.

Are you worried about copyright or something? This isn't legal advice, but I doubt they give a shit unless you're hosting content illegally for a large number of people. Obviously, only take the risk if you are comfortable with the potential consequences where you live.

Set up a VPS. Create a VPN tunnel from you local network to the VPS. Use the VPS as the edge router by opening ports on the VPS firewall and routing incoming traffic on those ports through the VPN tunnel to servers on your local network.

I used to do this to get around CGNAT. I ran RouterOS in a Digital Ocean droplet and setting up a wire guard tunnel between it and my local Mikrotik router.

It will obscure your local WAN IP and give you a static IP but that's about the only benefit. And you have to be pretty network savvy to configure it correctly.

It does not make you immune to DDoS attacks and is honestly more headache to maintain (albeit just a small headache).

[-] Cyber@feddit.uk 1 points 1 month ago

Not heard of RouterOS before ... I didn't realise jad released firmware that would run in a normal VM... don't suppose you have anything to compare it to pfSense?

[-] jubilationtcornpone@sh.itjust.works 3 points 1 month ago* (last edited 1 month ago)

They do maintain an x86 build. I haven't used pfSense but I have used OpnSense so that's that closest thing I have to compare it to. I think the upside and downside to RouterOS/Mikrotik is the same thing: it allows very granular control over almost everything. Maybe to a fault. It's probably overkill for most home networks.

[-] Cyber@feddit.uk 1 points 1 month ago

Ok, thanks... Good to know for a rainy day.

[-] SeeJayEmm@lemmy.procrastinati.org 1 points 1 month ago

DDOS protection is going to depend on the VPS. But for most services you could spin up a pretty lean Debian vm running a proxy like nginx proxy manager and run that over the tunnel. Something like opnsense seems like overkill.

[-] breakingcups@lemmy.world 5 points 1 month ago

Depends on why you want to hide your server ip, what's your use case? Is it to protect against DDOS?

Cloudflare is evil, but is there any other party you would trust to share everything with?

[-] foremanguy92_@lemmy.ml 2 points 1 month ago* (last edited 1 month ago)

Do you something like a vps would be more secure? Paying some dollars a month

[-] Toes@ani.social 2 points 1 month ago

I like that idea.

I'd suggest OVH or Digital Ocean.

If you think a DDoS attack is possible I'd suggest azure for that.

[-] tal@lemmy.today 2 points 1 month ago* (last edited 1 month ago)

I'd probably use a VPS myself.

I seem to recall db0 saying that lemmy.dbzer0.com is behind some sort of reverse proxy. I assume that they're in the same boat as OP.


$ host -t a lemmy.dbzer0.com
lemmy.dbzer0.com has address
$ whois
role:           OVH Technical Contact
address:        OVH SAS
address:        2 rue Kellermann
address:        59100 Roubaix
address:        France
admin-c:        OK217-RIPE
tech-c:         GM84-RIPE
tech-c:         SL10162-RIPE
nic-hdl:        OTC2-RIPE
abuse-mailbox:  abuse@ovh.net
mnt-by:         OVH-MNT
created:        2004-01-28T17:42:29Z
last-modified:  2014-09-05T10:47:15Z
source:         RIPE # Filtered

% Information related to ''

origin:         AS16276
mnt-by:         OVH-MNT
created:        2018-03-07T09:24:45Z
last-modified:  2018-03-07T09:24:45Z
source:         RIPE

I don't know if that's a VPS, but looks like they're using OVH.

[-] pupbiru@aussie.zone 3 points 1 month ago

a reverse proxy these days is pretty much just a requirement of any dynamic service. they often run on the same host as the software

[-] tal@lemmy.today 2 points 1 month ago

Aight, but db0 had something about it obscuring the server location, IIRC.

[-] pupbiru@aussie.zone 1 points 1 month ago

it’s possible, but that would seem… odd… for such a large and tech-savvy instance. there’s a lot of reasons why this isn’t a good idea, and very few technical reasons why it is

my guess is that it’s less about obscuring server location for privacy reasons as is the implications in this thread, and more about handling changes cleanly or something like that - in which case, sure it obscures the server location but more that it makes the server “location” (or hardware, etc) irrelevant and fungible

[-] solrize@lemmy.world 4 points 1 month ago

Do you want something that also has CDN like Cloudflare? Bunny.net is good, but way more expensive than a cheap VPS if you use a lot of traffic.

[-] foremanguy92_@lemmy.ml 2 points 1 month ago

No I don't need a CDN only a way to hide my IP to final users and that nobody can use my real IP to connect to my server

[-] jelloeater85@lemmy.world 2 points 1 month ago

Literally cloudflare tunnel, sorry my dude.

[-] kenkenken@sh.itjust.works 3 points 1 month ago
[-] foremanguy92_@lemmy.ml 2 points 1 month ago

So I need to have always the same exit node, need to connect to the server via an other IP and only this server know my ip

[-] axzxc1236@lemm.ee 4 points 1 month ago

AFAIK tor websites (onion service) doesn't require exit node, and no one knows your IP unless you are unlucky enough all nodes you connected are controlled by same entity.

[-] foremanguy92_@lemmy.ml 2 points 1 month ago

But the speeds are much slower nah? And can I host "normal" website trough Tor?

[-] axzxc1236@lemm.ee 3 points 1 month ago

Yes, speed would be much slower.

Yes, you can host a normal website through tor.

[-] DetachablePianist@lemmy.ml 3 points 1 month ago

If for personal access only, ZeroTier might solve your use case.

[-] possiblylinux127@lemmy.zip 3 points 1 month ago

VPS with Wireguard

[-] Andromxda@lemmy.dbzer0.com 2 points 1 month ago

Perhaps NetBird, ZeroTier or Tailscale? If you want to make a service available publicly, check out Tailscale Funnel.

[-] Mora@pawb.social 2 points 1 month ago

Very confused by the answers here. Anyway, check this list: https://github.com/anderspitman/awesome-tunneling

I personally used frp many years ago and it worked great.

[-] Decronym@lemmy.decronym.xyz 2 points 1 month ago* (last edited 1 month ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
CF CloudFlare
CGNAT Carrier-Grade NAT
DNS Domain Name Service/System
HTTP Hypertext Transfer Protocol, the Web
IP Internet Protocol
NAS Network-Attached Storage
NAT Network Address Translation
Plex Brand of media server package
SSH Secure Shell for remote terminal access
SSL Secure Sockets Layer, for transparent encryption
VPN Virtual Private Network
VPS Virtual Private Server (opposed to shared hosting)
nginx Popular HTTP server

12 acronyms in this thread; the most compressed thread commented on today has 15 acronyms.

[Thread #803 for this sub, first seen 15th Jun 2024, 10:35] [FAQ] [Full list] [Contact] [Source code]

[-] bin_bash@lemmy.world 1 points 1 month ago

I used boringproxy for years and I recomend you

load more comments
view more: next ›
this post was submitted on 15 Jun 2024
50 points (89.1% liked)


37939 readers
512 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.


  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.


Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago