Nginx Configuration Basics

Nginx is one of the most popular web servers in the world. It powers millions of websites, APIs and cloud applications thanks to its speed, efficiency and flexibility. Whether serving static files, acting as a reverse proxy or handling load balancing, Nginx is a fundamental tool for modern web infrastructure. Understanding the basics of Nginx configuration helps developers deploy and manage web applications more effectively.

What Is Nginx?

Nginx is a high-performance web server and reverse proxy originally created to solve scalability challenges faced by traditional web servers.

Unlike older process-based architectures, Nginx uses an event-driven model that allows it to handle thousands of simultaneous connections efficiently.

Today Nginx is commonly used for serving websites, proxying requests, load balancing, SSL termination and API gateways.

Where Nginx Configuration Lives

Nginx configuration is typically stored in text files located inside the server configuration directory.

/etc/nginx/nginx.conf

Additional configuration files are often placed inside dedicated directories such as:

/etc/nginx/sites-available/
/etc/nginx/sites-enabled/

The exact structure varies between Linux distributions and hosting environments.

The Basic Structure

Nginx configuration is organized into blocks. Each block controls a specific aspect of server behavior.

events {
}

http {
}

The main configuration usually contains an events block and an http block, with additional nested sections inside them.

The HTTP Block

Most website-related configuration resides inside the http block.

http {
  include mime.types;
  default_type application/octet-stream;
}

Global HTTP settings, MIME types, logging and virtual hosts are typically configured here.

Server Blocks

A server block is similar to a virtual host in Apache. It defines how Nginx should respond to requests for a specific domain.

server {
  listen 80;
  server_name example.com;

  root /var/www/example;
}

This tells Nginx to serve requests for example.com from the specified directory.

Listening Ports

The listen directive specifies which network port the server block should use.

listen 80;

Port 80 is used for HTTP traffic, while port 443 is typically used for HTTPS.

listen 443 ssl;

Location Blocks

Location blocks determine how specific URLs should be handled.

location / {
  try_files $uri $uri/ =404;
}

This block applies to requests targeting the root path and its subpaths.

Different locations can serve static files, proxy requests or return custom responses.

Serving Static Files

One of Nginx's strengths is serving static content efficiently.

location /images/ {
  root /var/www/assets;
}

Requests for images are served directly from disk without involving an application server.

Reverse Proxy Configuration

Nginx is commonly placed in front of application servers such as Node.js, Django, Laravel or Spring Boot applications.

location / {
  proxy_pass http://localhost:3000;
}

In this configuration Nginx forwards incoming requests to an application running on port 3000.

HTTPS Configuration

Modern websites typically use HTTPS for encrypted communication.

server {
  listen 443 ssl;

  ssl_certificate /path/cert.pem;
  ssl_certificate_key /path/key.pem;
}

The certificate and private key allow Nginx to establish secure TLS connections.

Redirecting HTTP to HTTPS

A common configuration automatically redirects users from HTTP to HTTPS.

server {
  listen 80;
  server_name example.com;

  return 301 https://$host$request_uri;
}

This ensures all traffic uses encrypted connections.

Custom Error Pages

Nginx can display custom pages when errors occur.

error_page 404 /404.html;

This replaces the default error response with a custom page.

Testing Configuration Changes

Before restarting Nginx, configuration files should always be validated.

nginx -t

This command checks syntax and reports any configuration errors.

Reloading Nginx

After successful validation, changes can be applied without interrupting active connections.

systemctl reload nginx

Reloading is generally preferred over a full restart because it avoids downtime.

Nginx vs Apache

Apache and Nginx are the two most popular web servers. Apache supports directory-level .htaccess files, while Nginx uses centralized configuration files.

Nginx often performs better under heavy traffic loads due to its event-driven architecture, while Apache remains popular because of its flexibility and long history.

When Should You Learn Nginx?

Any developer deploying websites, APIs or cloud applications will eventually encounter Nginx. Even basic knowledge of server blocks, location rules and reverse proxying can make troubleshooting and deployment significantly easier.

Conclusion

Nginx configuration revolves around a small set of powerful concepts: server blocks, location blocks, reverse proxies and HTTPS settings. Once these fundamentals are understood, developers can confidently configure websites, APIs and production infrastructure. Nginx remains one of the most important tools in modern web development, making its configuration syntax a valuable skill to learn.