view the rest of the comments
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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!
That's what I meant. Hosting the VPS at a company with ddos protection. So the VPS can take the hit instead of my home connection.
You could do it that way. You could use something like Cloudflare Tunnels/Zero Trust where you'd get DDoS protection for tunneled hostnames http/https. If you're looking for raw tcp/udp arbitrary ports protection, they have a paid Spectrum protection plan.
I don't know your specific situation, but after all these years of self hosting, I can't say as I've ever experienced a DDoS attack. Not saying they don't happen or that it isn't a concern. I've experienced someone hacking my server, but I was super green back then and undoubtedly didn't have the proper protections in order.
Most of your reputable, well established VPS vendors like Digital Ocean, Linode, Vultr, offer DDoS protections. Some like Hetzner offer multiple tiers of DDoS protection.