How to Test and Reload Nginx Config (nginx -t, Reload vs Restart)

How to Test and Reload Nginx Config (nginx -t, Reload vs Restart)

A single missing semicolon in an Nginx config can take every site on the server offline if you restart blindly. The safe routine is always the same: test, then reload.

Check the Config: nginx -t

sudo nginx -t

A good config prints:

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

A broken one prints the exact file and line:

nginx: [emerg] unexpected "}" in /etc/nginx/sites-enabled/example.com:24

Run it with sudo: without root, Nginx cannot read certificate keys or open log files and reports misleading permission errors.

See the Full Config: nginx -T

sudo nginx -T | less

Capital -T tests the config and prints every included file merged together. It is the fastest way to find duplicate server_name or default_server entries spread across files:

sudo nginx -T | grep -n "server_name"

Reload vs Restart

Combine the test and the reload so a broken config is never applied:

sudo nginx -t && sudo systemctl reload nginx

Without systemd (for example inside a container), use nginx -s reload.

Check That Nginx Is Running

systemctl status nginx
sudo journalctl -u nginx -n 50 --no-pager

The journal shows why a start or reload failed, with the same file and line references as nginx -t.

Common Errors

Failed to restart nginx.service: Unit nginx.service not found

systemd has no Nginx service on this machine. Either Nginx is not installed (sudo apt install nginx), it was installed another way (a Docker container, a control panel, OpenResty with its own service name), or you are inside a container without systemd. Check with systemctl list-unit-files | grep -i nginx and which nginx.

bind() to 0.0.0.0:80 failed (98: Address already in use)

Another process holds the port, often Apache or a second Nginx. Find it with sudo ss -tlpn | grep -E ":80 |:443 " and stop it.

Duplicate default server

Two server blocks both use default_server on the same port. Remove it from one; nginx -T shows where both are.

Changes are not taking effect

The file may not be in sites-enabled, a different server block may be matching the domain, or a CDN or browser is caching the old response.

Nginx in Docker

docker exec web nginx -t
docker exec web nginx -s reload

See docker exec for running commands inside containers. For errors visitors see, read common Nginx errors and fixes or 502 Bad Gateway.

Frequently Asked Questions

How do I check if my Nginx config is valid?
Run sudo nginx -t. It reports whether the syntax is OK or points to the exact file and line of the error.

Does nginx reload cause downtime?
No. Reload starts new worker processes and lets the old ones finish their requests, so connections are not dropped.

What is the difference between nginx -t and nginx -T?
-t only tests the configuration. -T tests it and also prints the full merged configuration.

Rather Not Babysit the Web Server?

RackUp IT managed hosting runs a tested, monitored Nginx stack and handles configuration changes, SSL and updates for you.