WebServer New Added 9 October 2026

nginx: the "listen ... http2" directive is deprecated, use the "http2" directive

Since nginx 1.25.1, HTTP/2 is switched on with its own http2 directive rather than a parameter on listen. The old form still works for now, so this is only a warning and nginx -t passes, which makes it easy to ignore. It turns up on every reload once nginx is upgraded underneath configs copied from older guides, and a future release can drop the parameter altogether.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

# Which version, and where is the old syntax?
nginx -v
grep -rn 'listen.*http2' /etc/nginx/

# Old
#   listen 443 ssl http2;
# New (nginx 1.25.1 and later)
#   listen 443 ssl;
#   http2 on;

# Edit every server block that matched, then test and reload
sudo nginx -t && sudo systemctl reload nginx

# On nginx older than 1.25.1 keep the old form:
# "http2 on" is an unknown directive there and nginx will not start

How to diagnose WebServer errors

Web server errors are usually about permissions, binding, or configuration that was never loaded. A common trap: the server runs as an unprivileged user (www-data, nginx), so it needs execute permission on every directory in the path to a file, not just read permission on the file itself. Another: editing a config file changes nothing until the server is reloaded and the file is actually included.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Validate configuration before reloading: nginx -t, apachectl configtest, caddy validate. This catches syntax errors without dropping traffic.
Dump the fully resolved configuration with nginx -T to see what is actually in effect, including every include.
Read the error log, not the access log, for 5xx causes. nginx names the failing upstream and the exact filesystem path it could not open.
For permission errors, test as the server user: sudo -u www-data cat /path/to/file. Check execute bits on every parent directory.
For binding failures, find the current listener with ss -tulpn | grep :80. Ports below 1024 need privileges or a capability such as CAP_NET_BIND_SERVICE.

Tools worth reaching for

nginx -t / nginx -T
apachectl configtest
ss -tulpn
tail -f error.log
sudo -u www-data

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

nginx.org

Related WebServer errors

See all 20 WebServer errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.