Where should I save Nginx server configuration files on Linux?

On Debian/Ubuntu systems, save your configuration to '/etc/nginx/sites-available/yourdomain.conf' and symlink it to '/etc/nginx/sites-enabled/'. On RHEL/AlmaLinux/CentOS, save it directly into '/etc/nginx/conf.d/yourdomain.conf'.

How do I test and reload Nginx configuration without downtime?

First test the syntax with 'sudo nginx -t'. If syntax test is successful, reload worker processes gracefully with 'sudo systemctl reload nginx'.

Why is proxy_set_header Upgrade needed for Next.js and WebSockets?

The 'Upgrade' and 'Connection' headers allow Nginx to pass persistent WebSocket handshakes to Node.js/Next.js for Hot Module Reloading (HMR) and real-time streaming connections.

Contact Log in Get Started →

Pricing

View Plans →

Verified 5.0 Clutch RatingAZBrand Cloud

Docker StackCompose Cron GenCrontab Nginx StudioProxy Systemd GenService Cloud-InitVPS Boot Subnet & CIDRIPv4/v6 SSH KeygenEd25519

Reverse Proxy • SSL • Hardened Headers

Nginx Config & Reverse Proxy Studio

Generate hardened, production-ready Nginx configurations for Next.js, Node, WordPress, and Python APIs.

Domain Name (server_name):

Upstream App Port:

Max Upload Size:

SSL / HTTPSForce HTTPS 301HSTS & SecurityGzip Compress

Generated Nginx Configuration:48 lines

upstream app_backend {
  server 127.0.0.1:3000;
  keepalive 32;
}

server {
  listen 80;
  listen [::]:80;
  server_name api.example.com;
  return 301 https://$host$request_uri;
}

server {
  listen 443 ssl http2;
  listen [::]:443 ssl http2;
  server_name api.example.com;
  client_max_body_size 50M;

  # SSL Certificate Configuration (Certbot / Let's Encrypt)
  ssl_certificate /etc/letsencrypt/live/api.example.com/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/api.example.com/privkey.pem;
  ssl_protocols TLSv1.2 TLSv1.3;
  ssl_ciphers HIGH:!aNULL:!MD5;
  ssl_prefer_server_ciphers on;

  # Hardened HTTP Security Headers
  add_header X-Frame-Options "SAMEORIGIN" always;
  add_header X-Content-Type-Options "nosniff" always;
  add_header X-XSS-Protection "1; mode=block" always;
  add_header Referrer-Policy "strict-origin-when-cross-origin" always;
  add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;

  # Gzip Compression
  gzip on;
  gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript image/svg+xml;
  gzip_min_length 1024;

  location / {
    proxy_pass http://app_backend;
    proxy_http_version 1.1;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
  }
}

Test & Reload: sudo nginx -t && sudo systemctl reload nginx

Deploy high-performance web servers on AZBrand VPS

1 Gbps unmetered network ports, dedicated IPv4 & IPv6, NVMe SSD compute.

Deploy Cloud VPS →

Architecture & Best Practices

Hardening Nginx for Production Deployment

Nginx is an event-driven, asynchronous web server and reverse proxy that handles tens of thousands of concurrent connections with low memory footprints. Proper configuration prevents common security vulnerabilities such as clickjacking, MIME-sniffing, and DDoS slow-loris attacks.

HSTS (HTTP Strict Transport Security)

Instructs browsers to strictly communicate over HTTPS, preventing SSL-stripping attacks on insecure public Wi-Fi networks.

Upstream Keepalive Pooling

Maintains open TCP sockets to your backend application (Node.js, Python), eliminating TCP handshake overhead for high-throughput API endpoints.

Server Administration

Nginx Config & Reverse Proxy Studio

Hardening Nginx for Production Deployment

Frequently Asked Questions