Does the SSL option actually get me a certificate?

No - checking 'Include SSL/TLS block' only writes the ssl_certificate and ssl_certificate_key directives pointing at typical Let's Encrypt / certbot paths; you still need to obtain the certificate yourself before this config will work.

What's the difference between the load balancer's balancing methods?

Round robin (the default, no directive needed) cycles evenly through servers, least_conn sends new connections to whichever backend has the fewest active ones, and ip_hash pins each client IP to the same backend for session persistence.

● runs entirely in your browser

Nginx Config Generator

Pick a mode, fill in the blanks, get a working nginx server block. Nothing is ever uploaded.

server_name

listen port

Static site

root

index

Single-page app fallback (try_files → index.html)

Reverse proxy Proxy target (host:port)

Enable WebSocket support (Upgrade/Connection headers)

Load balancer Upstream servers, one per line (host:port) Balancing method

Extras

Enable gzip compression

Include SSL/TLS block (assumes certificate already obtained, e.g. via certbot)

Generated config

How it works

Each tab builds a real nginx server block from the ground up: static mode writes root/index/try_files directives (switching to an SPA fallback of try_files $uri $uri/ /index.html when checked), reverse proxy mode writes proxy_pass plus the standard X-Forwarded-* headers (and adds proxy_http_version 1.1 with Upgrade/Connection headers if WebSocket support is checked), and load balancer mode wraps multiple servers in an upstream block ahead of the server block. Gzip and SSL are optional extras layered onto whichever mode you're in.

FAQ

Does the SSL option actually get me a certificate?: No - checking 'Include SSL/TLS block' only writes the ssl_certificate and ssl_certificate_key directives pointing at typical Let's Encrypt / certbot paths; you still need to obtain the certificate yourself before this config will work.
What's the difference between the load balancer's balancing methods?: Round robin (the default, no directive needed) cycles evenly through servers, least_conn sends new connections to whichever backend has the fewest active ones, and ip_hash pins each client IP to the same backend for session persistence.

Free, unlimited, no account. If this saved you a paid tool, a small thanks is appreciated.

Say thanks — $3