NGX

Nginx Config Helper

Build server blocks for a reverse proxy, static site or PHP-FPM, or check the syntax and format existing configs — all in your browser.

server block
reverse proxy
TLS
rate-limit
lint

nginx.conf

Settings

Service type

Domains (server_name)

Port (listen)

Enable HTTPS (SSL/TLS)

SSL certificate path Private key path Auto-redirect HTTP to HTTPS Add HSTS header

Document root Index files Single-page app (SPA) — fall back to index.html

Backend address (proxy_pass) WebSocket support

Document root PHP-FPM address (fastcgi_pass) Index file

General options Gzip compression Basic security headers Rate limiting

Requests/second Burst

Custom log path

access_log error_log

Max upload size (client_max_body_size)

Config preview

nginx.conf

Waiting for input...

Input config

Check result

—Blocks

—Lines

—Errors

—Warnings

This tool runs entirely in your browser; no config is sent to a server. The "Builder" covers common server blocks (static, reverse proxy, PHP-FPM) along with SSL, gzip, security headers and rate limiting. The "Check & format" section fully validates config syntax (matching braces and semicolons) and warns about overall structure (listen/server_name, proxy_pass headers, outdated SSL protocols, conflicting add_header, if inside location, and rate-limit zone references); since Nginx has dozens of modules and hundreds of directives, unknown directives are deliberately not flagged as errors. This tool is not a replacement for running nginx -t on the real server.

ABOUT

Build an Nginx server block and catch common config mistakes

A small mistake in nginx.conf can take the site down at reload. This tool generates a standard server block for reverse proxying, TLS and rate limiting, and lints an existing config for common slips such as proxy_pass without the needed headers or a missing server_name. Always test with nginx -t before applying.

HOW TO

How to use it

In builder mode, enter the domain and the upstream address.
Set TLS and rate-limit options, or paste an existing config to lint it.
Drop the output into /etc/nginx/conf.d/, run nginx -t, then systemctl reload nginx.

FAQ

Frequently asked questions

What does a 502 Bad Gateway mean?

Nginx could not reach the upstream or got an invalid response — typically the app is down, the port is wrong, or a firewall/SELinux blocks it.

Reload or restart?

reload applies the new config without dropping live connections and is preferred in production.