Starting, stopping, and reloading in Nginx - Commands & Configuration

Introduction

Managing the nginx web server involves controlling when it runs, stops, or reloads its settings. Starting, stopping, and reloading help keep the server running smoothly and apply changes without downtime.

When you install nginx and want to start serving web pages for the first time

When you need to stop nginx to perform maintenance or updates safely

When you change the nginx configuration and want to apply the new settings without stopping the server

When nginx is not responding and you want to restart it cleanly

When you want to check the status of nginx to ensure it is running

Commands

This command starts the nginx service so it begins serving web pages. Use it after installation or after stopping nginx.

Terminal

sudo systemctl start nginx

Expected Output

No output (command runs silently)

This command shows the current status of nginx, including whether it is running and recent logs.

Terminal

sudo systemctl status nginx

Expected Output

● nginx.service - A high performance web server and a reverse proxy server

   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)

   Active: active (running) since Fri 2024-06-07 10:00:00 UTC; 1min 30s ago

     Docs: man:nginx(8)

 Main PID: 1234 (nginx)

    Tasks: 3 (limit: 4915)

   Memory: 5.0M

   CGroup: /system.slice/nginx.service

           ├─1234 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;

           ├─1235 nginx: worker process

           └─1236 nginx: worker process

This command reloads the nginx configuration without stopping the server, applying changes smoothly.

Terminal

sudo systemctl reload nginx

Expected Output

No output (command runs silently)

This command stops the nginx service, halting all web serving until it is started again.

Terminal

sudo systemctl stop nginx

Expected Output

No output (command runs silently)

Key Concept

If you remember nothing else from this pattern, remember: use reload to apply config changes without downtime, start to run nginx, and stop to halt it safely.

Common Mistakes

Trying to reload nginx when the configuration file has errors

Reloading with bad config causes nginx to fail silently or keep old settings, leading to unexpected behavior

Always test the configuration with 'sudo nginx -t' before reloading

Using 'stop' instead of 'reload' after changing configuration

Stopping nginx causes downtime and interrupts service, which is avoidable

Use 'sudo systemctl reload nginx' to apply config changes without stopping the server

Not running commands with sudo or root privileges

Without proper permissions, commands will fail to control the nginx service

Always use 'sudo' before systemctl commands for nginx

Summary

Use 'sudo systemctl start nginx' to start the nginx server.

Use 'sudo systemctl reload nginx' to apply configuration changes without stopping the server.

Use 'sudo systemctl stop nginx' to safely stop the nginx server.