Pikkola Nginx, tool No. 62
Write the block, then read it back.
Seven starting points cover what a host usually does: proxy to Node, Python or Go, serve a React or Vue build from disk, carry a WebSocket upgrade, or send old names to a new one with 301. Every switch writes its own lines and the file leaves as nginx.conf. Then the linter reads any config back, line by line, and names what nginx -t will not.
- 7
- presets
- 30
- checks
- 0
- uploads
The studio
One bench writes, one bench reads
The left bench turns a few choices into a whole nginx.conf. The right bench takes a config you already have and points at the lines worth changing. Neither one sends the text anywhere, and neither one needs an account.
A server block from seven starting points
Start from the preset closest to the host, correct the name and the target, then turn on only what this server needs. The comments in the file say which lines belong in the http block and which in conf.d.
sudo nginx -t && sudo systemctl reload nginx
Paste a config and read it back
The linter parses the file the way nginx does, braces and semicolons first. Then it reads the lines that pass nginx -t and still cost you: an old protocol, a missing Host header, a header that disappears on an error page.
Nothing to read yet. Paste a config on the left, or start from one of the three samples.
What the linter reads
Thirty checks, each with a failure behind it
A check earns its place by naming something you would otherwise meet in production: a config that starts, answers, and then leaks. These five groups are the whole list, and the count on each card is what runs.
A finding carries a severity. Fail means nginx would refuse the file, or serve traffic that a browser or an attacker treats as broken. Warn means it loads and the damage is quiet. Info is a line worth a second look. None of them replaces nginx -t.
Questions
What this does, and where it stops
Will this config work on my nginx?
The file assumes a packaged nginx on Debian or Ubuntu: mime.types under /etc/nginx, a certificate from certbot, and http2 on its own line, which arrived in nginx 1.25.1. On an older build, write http2 on the listen line instead. Every directive is plain nginx, and only brotli needs a module.
Why does a header on an error page matter?
add_header without always adds the header to 2xx and 3xx responses and leaves it off 4xx and 5xx. A scanner that requests a missing page finds no HSTS and no frame rule, and reports the site as unprotected, which is the same conclusion a browser reaches on that response.
Is proxy_set_header Host really necessary?
Without it nginx passes the upstream address as Host, so the app is told it is 127.0.0.1:3000. Apps build absolute URLs from that value, so a password reset mail or a redirect points at the loopback address and breaks outside the host.
How is the rate limit counted?
The zone is keyed on binary_remote_addr, the client address. Ten requests a second are served, twenty more may queue and the rest get 429. Behind another proxy every visitor shares one address, so set real_ip or key the zone on a header you trust.
Does the linter run my config?
No. It reads the text. No request leaves the page, since the content policy sets connect-src to none, and nothing is executed. nginx -t remains the only test that proves a file loads.
Where does the pasted text go?
Nowhere. There is no endpoint to send it to. Both benches run in this tab, and only the language, the theme and the switches you set stay in this browser.