How does Nginx reload work without downtime?
The master process reads the new config, starts new worker processes with the new config, old workers finish their current requests, and old workers shut down gracefully. Existing connections continue with old workers, new connections use new workers. Zero downtime.
Verify This Answer
Cross-check this information using these trusted sources:
More FAQs in Why Update Nginx Config and When to Reload Configuration Management
When adding new subdomains, SSL certificates, WebSocket support, performance tuning (gzip, caching, workers), security hardening (headers, rate limiting), load balancing (multiple instances), changing proxy settings, or adding static file serving.
Always use reload (sudo systemctl reload nginx) in production. Reload starts new worker processes with the new config and lets old workers finish their current requests zero downtime. Restart stops and starts Nginx, causing a brief downtime.
Edit the config file, test with sudo nginx -t (catches syntax errors), reload with sudo systemctl reload nginx (zero downtime), and verify with sudo systemctl status nginx and curl -I. Never reload without testing first.
Still have questions?
Browse all our FAQs or reach out to our support team