Finally got around to securing my VPS
retained text
I have been managing a VPS for quite a while now. I self-host a few applications for my personal use. It was all internet facing. I had not put any restrictions other than disabling sign-ups. A while ago I noticed massive log files in journald and nginx folders. After inspection, I found thousands of attempts from bots, scanners, etc. Initially I was scared. But then, with the help of ChatGPT, I ran a few checks and did not find any breach or unauthorized access. This prompted me to finally check this thing I had heard often about called fail2ban. After spending a few hours on securing my server, I had done the following: * SSH login only from my home IP range (unfortunately no static IP) or over tailscale. Restriction applied using ufw. * personal websites accessible only from home IP range or over tailscale. Restriction applied using nginx config. No response to any other IP, no 403 or 404. Just plain ignore. * No public access for database (this was just stupid of me) * fail2ban jails for ssh and nginx. * Outright ban in ufw for 2 IP ranges which had sent the most bot requests. Tested everything using mobile data connection. Feels good knowing my VPS is now secure.
document fetched 2026-11-02 00:28 · canonical https://reddit.com/r/selfhosted/comments/1xl5zcs/finally_got_around_to_securing_my_vps