Self-hosted VPN with WireGuard on VPS - update after messing around for weeks

Self-hosted VPN with WireGuard on VPS - update after messing around for weeks

Summit

New member
so i posted about trying to set up my own VPN before and after a lot of reading and trial and error I finally got a decent setup going with wireguard on a vps. honestly it's not perfect but it's been kinda fun learning the ins and outs. I went with a small droplet on digitalocean cause it was cheap and seemed reliable. setup was kinda straightforward but figuring out the keys and configs took a while. my main reason was privacy and speed, also I hate how most commercial VPNs keep logs and stuff. anyway I tested it with speed tests and streaming and torrenting, seems pretty solid so far. streaming works fine on Netflix and Disney+, no lag or buffering so that's a win. torrenting is faster than I thought too and no weird IP leaks so far. protocols? I stuck with wireguard cause it's lightweight and supposedly more secure than openvpn. only thing I wonder about is how do I keep it super secure, like updating configs or if the VPS gets compromised? I keep thinking if I should self-host on a second server or just keep it simple. anyone else doing this? is it worth the hassle or just better to pay for a VPN service? also thinking about maybe adding some multi-hop routing but idk if it's overkill or not. just glad I finally got a working setup, feels good knowing I control the logs and privacy more than any VPN service I pay for.
 
different angle: yeah digitalocean is popular for small projects but don't forget to regularly back up your configs and keys somewhere safe. if your VPS gets compromised, those backups can save your bacon and help you restore fast. always good to have a plan B.
 
Make sure to keep your DNS leak protections tight, bruh, or Netflix might detect and block your VPN even if streaming seems smooth now.
 
you thinking about using DNS leak protection or just relying on the default setup? lol always worried about those sneaky leaks lmao
 
spot on. I did the same a while back, spent ages tweaking configs, only to get paranoid about if I did enough for security. ended up just doing regular updates and changing keys every so often, but yeah, that feeling of control is kinda addictive. kinda funny how it's always a balance between hassle and peace of mind.
 
yep exactly, always better to explicitly enable DNS leak protection and test it, fwiw. default configs often miss those sneaky leaks. stay safe out there.
 
lol, honestly I think doing regular key rotations every 3-6 months and patching your VPS quickly if there's a vuln is the best for security, like 60% of VPS breaches happen from outdated software rn.
 
But you really think that's enough? smh, just patching and rotating keys doesn't cover some dude getting in through a zero day or a misconfigured server. gotta stay on top of everything constantly, not just rely on routines.
 
spot on. just patching and configs ain't enough, gotta keep an eye on security updates, monitor logs, maybe even add some intrusion detection like fail2ban. check out tincan for multi-hop routing, it's lightweight and easy to set up, might save you from overkill. don't wanna get too comfy thinking it's all good, that
 
mine's been the same, streaming on Netflix and Disney+ is smooth too. last month I added a small fail2ban script and set up automatic updates on my VPS. it's simple but really helps keep the setup tight. just be careful with configs when updating, or you might introduce leaks. overkill? maybe, but peace of mind is worth it for me
 
just my 2 cents: if you're happy with digitalocean for now, cool, but keep in mind they've had some outages before. maybe set up monitoring or alerts so you catch if your droplet goes down. could be worth testing a second provider down the line, ymmv.
 
yo thanks for the tips, backup is def on my list now, dont wanna lose all my configs if shit hits the fan. DNS leak protection? yeah I'm trying to get that dialed in, don't want Netflix blocking me after I spent all that time. I think I'll look into some more strict DNS configs, maybe use a trusted DNS provider for that.
 
Back
Top