Common error diagnosis in Nginx - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does a 502 Bad Gateway error usually indicate in nginx?

It means nginx received an invalid response from the upstream server, often because the backend server is down or misconfigured.

beginner

How can you check nginx error logs to diagnose issues?

Use the command tail -f /var/log/nginx/error.log to view real-time error messages.

beginner

What does a 404 error mean in nginx?

It means the requested resource was not found on the server. This can happen if the URL is wrong or the file does not exist.

intermediate

Why might nginx fail to start after configuration changes?

Because of syntax errors in the config file. Running nginx -t checks the config for errors before restarting.

beginner

What is the purpose of the nginx -t command?

It tests the nginx configuration files for syntax errors without starting the server.

Which log file is most useful for diagnosing nginx errors?

A /var/log/nginx/error.log

B /var/log/nginx/access.log

C /etc/nginx/nginx.conf

D /var/log/syslog

The error.log file contains error messages that help diagnose nginx problems.

What does a 504 Gateway Timeout error mean in nginx?

A The requested page was not found

B The upstream server did not respond in time

C Nginx configuration syntax error

D Permission denied to access the file

A 504 error means nginx waited too long for the backend server to respond.

What command checks nginx configuration syntax without restarting?

A systemctl status nginx

B nginx -s reload

C nginx -v

D nginx -t

nginx -t tests the config files for syntax errors.

If nginx shows a 403 Forbidden error, what is a likely cause?

A File permissions prevent access

B The server is down

C The URL is incorrect

D Nginx configuration syntax error

403 means access is denied, often due to file or directory permissions.

What is the first step to diagnose nginx not starting after config change?

A Delete the config file

B Restart the server immediately

C Run <code>nginx -t</code> to check config syntax

D Check the access log

Checking config syntax helps find errors before restarting nginx.

Explain how to diagnose a 502 Bad Gateway error in nginx.

Think about what nginx means by 'Bad Gateway' and where to look for clues.

Describe the steps to safely apply changes to nginx configuration.

Testing config before reload prevents downtime.

Practice

1. What is the primary command to check if the nginx configuration file has syntax errors before restarting the service?

easy

A. nginx -s reload

B. nginx -t

C. systemctl status nginx

D. nginx -v

Solution

1. Step 1: Understand the purpose of nginx -t

   The command nginx -t tests the syntax of the nginx configuration files without starting or restarting the service.

2. Step 2: Compare with other commands

   nginx -s reload reloads the configuration but does not test it first. systemctl status nginx shows service status, and nginx -v shows version info.

3. Final Answer:

   nginx -t -> Option B

4. Quick Check:

   Test config syntax = nginx -t [OK]

Hint: Use nginx -t to test config syntax before restart [OK]

Common Mistakes:

• Using reload without testing config first
• Checking service status instead of config syntax
• Confusing version command with test command

2. Which of the following nginx configuration snippets will cause a syntax error?

easy

A. server { listen 80 server_name example.com; }

B. server { listen 443 ssl; server_name example.com; }

C. server { listen 80; server_name example.com; }

D. server { listen 8080; server_name localhost; }

Solution

1. Step 1: Identify correct syntax for directives

   Each directive must end with a semicolon. server { listen 80 server_name example.com; } misses a semicolon after listen 80, causing syntax error.

2. Step 2: Verify other options

   Options A, B, and D have correct semicolons and valid directives.

3. Final Answer:

   Missing semicolon after listen directive -> Option A

4. Quick Check:

   Every directive ends with ; [OK]

Hint: Check for missing semicolons in config lines [OK]

Common Mistakes:

• Omitting semicolons after directives
• Writing multiple directives without separators
• Confusing syntax for listen and server_name

3. Given this nginx error log line: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use), what is the most likely cause?

medium

A. Syntax error in nginx.conf

B. Missing SSL certificate files

C. Another process is already using port 80

D. Incorrect server_name directive

Solution

1. Step 1: Understand the error message

   The error bind() to 0.0.0.0:80 failed (98: Address already in use) means nginx tried to use port 80 but it is already occupied.

2. Step 2: Rule out other options

   Syntax errors or missing SSL files cause different errors. Incorrect server_name does not cause bind errors.

3. Final Answer:

   Another process is already using port 80 -> Option C

4. Quick Check:

   Port in use = bind() failed error [OK]

Hint: bind() failed means port is busy, check running services [OK]

Common Mistakes:

• Assuming syntax error causes bind failure
• Ignoring port conflicts
• Confusing SSL errors with port binding

4. You run systemctl restart nginx but nginx fails to start. Which command helps you find detailed error messages to diagnose the problem?

medium

A. netstat -tuln

B. nginx -v

C. ps aux | grep nginx

D. journalctl -u nginx.service

Solution

1. Step 1: Identify command for service logs

   journalctl -u nginx.service shows detailed logs for the nginx service, useful for error diagnosis after failure.

2. Step 2: Understand other commands

   nginx -v shows version, ps aux | grep nginx shows running processes, netstat -tuln shows network ports but not error logs.

3. Final Answer:

   journalctl -u nginx.service -> Option D

4. Quick Check:

   Service logs = journalctl -u [OK]

Hint: Use journalctl -u nginx.service for detailed error logs [OK]

Common Mistakes:

• Using version command instead of logs
• Checking processes without logs
• Looking at ports instead of error messages

5. You updated nginx.conf but after reload, nginx serves the old configuration. What is the best way to ensure nginx uses the new config without downtime?

hard

A. Run nginx -t to test config, then nginx -s reload

B. Restart the server machine

C. Stop nginx, edit config, then start nginx

D. Clear browser cache and refresh

Solution

1. Step 1: Test new configuration syntax

   Run nginx -t to confirm the new config has no errors before applying it.

2. Step 2: Reload nginx gracefully

   Use nginx -s reload to reload config without stopping the service, avoiding downtime.

3. Final Answer:

   Test config then reload nginx gracefully -> Option A

4. Quick Check:

   Test then reload = safe config update [OK]

Hint: Always test config before reload to avoid downtime [OK]

Common Mistakes:

• Restarting server unnecessarily
• Stopping nginx causing downtime
• Assuming browser cache causes config issues