Varnish Cache in front of Nginx on Ubuntu
Put Varnish in front of nginx on Ubuntu 24.04 or 26.04. Bind it to loopback, write VCL with a health probe and a locked PURGE, then prove each cache hit.
Filtering by topic #nginx · clear
Put Varnish in front of nginx on Ubuntu 24.04 or 26.04. Bind it to loopback, write VCL with a health probe and a locked PURGE, then prove each cache hit.
Random HTTP 500s after an nginx security update? Find the volatile map behind this alert and install AlmaLinux's fixed build without losing the CVE patch.
A web server can mean the machine or the program that answers HTTP requests. Run one with Python and one with nginx on localhost, then read the real headers.
How a one-line GET request became HTTP/3, with the real RFC dates and authors, and where each decision still shows on your own server today.
Build an nginx reverse proxy server block line by line: proxy_pass, the four headers your app needs, websockets, trailing slashes, and uploads.
Lock an admin panel behind mTLS: build a private CA with openssl, issue client certificates, and configure nginx to refuse anyone without one.
Three version numbers in one nginx config. What HTTP/2 multiplexing and HTTP/3 over QUIC actually change, how to enable each, and when it is worth it.
Flush the DNS cache on Ubuntu with resolvectl, then find the copies a flush misses: nscd, nginx, Docker, the JVM and stale or negative answers held upstream.
Measure how much of your traffic is AI crawlers from your own access log, then block or rate limit them in nginx, Apache or Caddy without losing real visitors.
Run Django in production on Ubuntu 24.04: uv or venv, Gunicorn on a Unix socket, a systemd unit, Nginx for TLS and static files, plus what breaks first.
Your agent wrote the app. Now keep it running: systemd supervision, a reverse proxy with TLS, an env file for secrets, backups, and safe redeploys.
HTTP and HTTPS differ on the server side: a second listener, a redirect, HSTS you cannot easily undo, mixed content, and renewal that fails at 3am.
Pick home or a VPS first, then put a static site live on nginx: server block, DNS record, firewall rule and TLS certificate, and what changes for an app.
Three services, one VPS, one public IP. How Nginx, Caddy and Traefik differ on certificates, config cost per app, websockets and Docker routing.
Run a v3 onion service on Ubuntu with tor and nginx bound to loopback, then close the leaks that link the address back to your public IP.
sudo apt install certbot python3-certbot-nginx, then one certbot --nginx run for a Let's Encrypt cert. Plus apt vs snap and the port 80 renewal timeout.
Run Sonarr and Radarr behind nginx or Traefik with forward auth: the Allowed Hosts entries that stop Invalid Hostname errors, and why /api must skip login.
Publish an Onion-Location header in nginx so Tor Browser offers your onion address, then close the leaks that undo it: redirects and third-party assets.