Nginx Validator
Check local Nginx configuration for unclosed quotes, missing terminators, unmatched braces and the expected include and events directive forms.
Find Nginx Structure Errors by Line
Nginx Validator: how to use it
- Paste your configuration, open a UTF-8 file or select Load example to see two common findings.
- Select Check structure. Review the line and column of each finding, fix the text and rerun the check.
- Download the JSON structure report. Use the target installation to confirm directive values, included files, modules and runtime behavior.
Limits and notes
Paste text or open a UTF-8 file up to 1 MB, with up to 250,000 characters. Include directives remain text and referenced files stay unread. Checks lexical tokens, semicolons, braces, up to 128 levels of blocks and up to 40 findings. Checks the forms of unquoted include and events names. Module availability, resource paths, directive-specific values and actual configuration loading require separate validation.
How your privacy works →Nginx Validator: common questions
Which directive forms does this check cover?
An unquoted include name needs one path or glob and a semicolon. An unquoted events name needs a block with no arguments.
Why can a missing semicolon merge two directives?
A newline separates tokens. If the next semicolon still ends the combined token sequence, a structural pass can succeed. Directive argument checks may then find a problem.
Does the validator open included configuration files?
The report counts include statements found in the supplied text. Review the contents or availability of those files separately.