Automation, scripting, infrastructure management for DevOps, SysAdmin and other Tech stuff
I spent years using OpenVPN for internal VPNs and I was always mildly frustrated by it. The configuration files are long, the certificates require careful management, the performance is decent but not great, and debugging connection issues is painful. Then I tried WireGuard and everything got simpler. WireGuard is modern, fast, and has a remarkably
WireGuard VPN on Linux: Setup and Configuration Read Post »
SSH is one of the first services I lock down on a new server because it is usually the front door to everything else. If SSH is weak, the rest of your hardening work starts from a bad premise. If SSH is solid, you at least force attackers into harder, noisier, or less direct paths.
SSH Hardening: A Practical Guide for Production Servers Read Post »
PHP-FPM (FastCGI Process Manager) is how PHP runs behind Nginx. The two don’t talk to each other directly — Nginx hands PHP requests to PHP-FPM via FastCGI, PHP-FPM processes them, and sends responses back. Getting this configuration right affects both performance and stability. I’ve set this up dozens of times. Here’s what I’ve learned about
PHP-FPM and Nginx: Configuration and Performance Tuning Read Post »
I still write a lot of Bash. Not because Bash is elegant, and definitely not because it is my first choice for complex software, but because it is already on the server, it is fast to deploy, and it solves a lot of admin problems before Python would finish creating its virtual environment. The catch
Bash Scripting for Sysadmins: Practical Patterns and Real-World Examples Read Post »
A 504 Gateway Timeout means the proxy or gateway did not get a response from the upstream fast enough. In practical terms, a frontend server such as Nginx waited for Apache, PHP-FPM, Gunicorn, Node.js, or some internal API, and the answer took longer than the configured limit. I treat 504 as a timing problem with
HTTP 504 Gateway Timeout: Nginx and Apache Debugging That Finds the Real Bottleneck Read Post »
A 503 Service Unavailable response tells me the server is reachable, but it cannot handle the request right now. That wording matters. Unlike a DNS failure or connection refusal, the system is still present enough to answer. It is simply overloaded, deliberately unavailable, or temporarily unable to hand work to the component that should process
HTTP 503 Service Unavailable: Causes, Fixes, and the Checks I Rely On Read Post »
UFW (Uncomplicated Firewall) is the default firewall management tool on Ubuntu. It’s a frontend to iptables that makes common firewall tasks manageable without having to write iptables rules directly. I use it on most of my Ubuntu servers — it handles the 95% case well and doesn’t get in the way. Installation and Initial State
UFW Firewall on Ubuntu: Setup and Daily Use Read Post »
A 502 Bad Gateway error usually means Nginx was able to accept the client request, but it failed when it tried to talk to the upstream application that should have generated the real response. In practice, that upstream might be PHP-FPM, Apache, Gunicorn, uWSGI, Node.js, a local API on another port, or even another reverse
HTTP 502 Bad Gateway in Nginx: How I Troubleshoot It Without Guessing Read Post »
Redirects look simple until they are not. I have seen one misplaced 301 break a migration plan for days because browsers cached it so aggressively that testers kept insisting the “old bug” was still there after the config had already changed. I have also seen 302 used for a permanent site move, which delayed search
Redis is one of those services that starts as a simple cache and ends up being a critical piece of infrastructure. I’ve used it for session storage, rate limiting, job queues, pub/sub, and as a general-purpose key-value store. Getting the configuration right from the start saves headaches later. Installation For the latest stable version from
Redis on Linux: Installation, Configuration, and Production Tuning Read Post »