I deadass got a cloudflare error after reopening this post:
the people on selfhost would be very upset if they could read this.
if you can provide me a better way to keep my homelab from getting DDoSed every five minutes then by all means, please share it
@[email protected] @[email protected] Is that an actual issue or a hypothetical one? I’ve never had an attack in 10 years of publicly hosting stuff.
As someone else who used to host via an open port, you get random connections all the time. Almost constantly and the request paths make it obvious they are scanning for vulnerabilities. Via cloud flare the number of those requests is much lower, as they have to know at least the DNS to do so, (and can’t guess it from a presented SSL cert.)
It’s the reason I set up cloudflare in the first place, so yeah. I was getting SYN flood-ed to the point that my router would just crash almost immediately, and after rebooting it the attack would resume after a minute or two.
@[email protected] @[email protected] Hm weird, I don’t see why they would spend their resources attacking random people without any kind of demand. Even at work I’ve never seen one happening.
I still believe Cloudflare has most of its customers because of fearmongering tbh.
Is you homelab getting ddosed constantly?
I had had it for years and never ever got ddosed.
Are you sure it’s actually ddos and not just the typical bots scanning for vulnerabilities? Which are easy defended for by keeping updated.
It’s weird as a DDOS is not something that’s just happens, it’s a targeted attack. It’s a rare occurrence that someone decided to attack a homelab.
I spent multiple days getting SYN flooded to the point my router would crash and reboot over and over, and it stopped the moment I set up cloudflare and asked my ISP to change my IP. This was the instance which pushed me over the edge, but there had been smaller attacks lasting a few minutes each for years leading up to this.
What kind of router to you have? A good router should not crash from any amount WAN traffic. But yes, if you host anything you will get scanned even harder than usual.
Anubis:3
Just put it behind a wireguard server and don’t expose any ports?
If you absolutely must expose some stuff, get a cheap 3$/mo vps that connects via wireguard to your home and setup a reverse proxy? They almost all come with DDoS protection.
Conservatives will get really upset once they realize you are changing genders
What’s a good VPS provider for privacy enthusiasts?
How do I stop a DDOS attack of my website without having port 80 or 443 open, so you can access the website?
Don’t expose the website. That’s the point. Only connect remotely via wireguard.
If you must expose the website, I also provided options in my original post.
I think you misunderstood; if I run a publicly accessible website (like a Lemmy instance), those ports need to be opened.
A cheap VPS hosting
https://anubis.techaro.lol/docs/admin/installation/
as a reverse proxy may work. The VPS will do the work of verifying requests and stopping bad requests from hitting the target resource. Though certainly if the DDoS is a matter of a massive botnet raiding your domain it may not work as well as something like cloudflare
Yes, I’ve addressed this in my original message.
Get yourself a 3$/month VPS, they almost all come with DDoS protection, and reverse proxy from there. Either restrict the ports on your home network to only that IP, or better yet tunnel all the traffic via Wireguard.
Obviously if you’re hosting a large server this is another matter, but nevertheless almost all serious hosting services offer in house DDoS protection.
But the comment I was originally replying to specifically refered to homelabs.
deleted by creator
What would be a good resource to, like, relearn modern networking stuff cuz some of these solutions are totally new ideas to me? I was CISCO and A+ certified way back in 2003; but the only thing I ever really used from those classes and training since then was making cables and setting up smaller, simple networks for home or small businesses. I get the sense a fuckton has changed and this exchange made me want to brush up.
A fuckton is an understatement.
I found just doing it the best for me. Start with proxmox hypervisor on some old pc. Start running a bunch of services. Some documentation mentions “heres how you set it up behind a reverse proxy”. “Hmm…whats that” is pretty much how i learned it.
Then compare with people in the homelab communities who are doing differently and find out why.
Host your own cloud worthy anti DDOS solution with fail2ban /s
Don’t forget your SSL certificate to prevent man-in-the-middle attacks. 🤪
moms 🙄
