502 Bad Gateway troubleshooting in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the cause of 502 Bad Gateway in Nginx

What is the most common cause of a 502 Bad Gateway error when using Nginx as a reverse proxy?

A Nginx configuration file syntax error

B The backend server is down or not responding

C Client browser cache is corrupted

D DNS server is unreachable

💡 Hint

Think about what happens when Nginx tries to connect to the backend server.

A 502 Bad Gateway error usually means Nginx cannot get a valid response from the backend server it proxies to. This often happens if the backend is down or not responding.

💻 Command Output

intermediate

Identifying backend server status from Nginx error log

Given the following Nginx error log snippet, what does it indicate about the backend server?

Nginx

2024/06/01 12:00:00 [error] 1234#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.1.10, server: example.com, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:8080/", host: "example.com"

A The backend server at 127.0.0.1:8080 is refusing connections

B Nginx has a syntax error in its config

C The DNS resolution for example.com failed

D The client IP 192.168.1.10 is blocked

💡 Hint

Look at the phrase 'connect() failed (111: Connection refused)'.

The error means Nginx tried to connect to the backend at 127.0.0.1:8080 but the connection was refused, indicating the backend server is not accepting connections.

❓ Configuration

advanced

Correcting Nginx upstream configuration to avoid 502 error

Which Nginx upstream configuration will correctly proxy requests to a backend server running on localhost port 3000 and avoid 502 errors if the backend is healthy?

A

upstream backend { server 3000; }
server {
  location / {
    proxy_pass http://backend;
  }
}

B

upstream backend { server 127.0.0.1; }
server {
  location / {
    proxy_pass http://backend:3000;
  }
}

C

upstream backend { server localhost:3000; }
server {
  location / {
    proxy_pass http://127.0.0.1;
  }
}

D

upstream backend { server 127.0.0.1:3000; }
server {
  location / {
    proxy_pass http://backend;
  }
}

💡 Hint

The upstream server must include both IP and port correctly.

Option D correctly defines the upstream server with IP and port, and proxy_pass uses the upstream name. Other options have syntax or address errors causing connection failures.

❓ Troubleshoot

advanced

Diagnosing intermittent 502 Bad Gateway errors

You notice intermittent 502 Bad Gateway errors in Nginx logs with messages about upstream timed out. What is the most likely cause?

A Backend server is slow or overloaded causing timeouts

B Nginx configuration file has syntax errors

C Client is sending malformed HTTP requests

D Nginx worker processes crashed

💡 Hint

Timeouts usually mean the backend took too long to respond.

Intermittent 502 errors with upstream timeout messages usually mean the backend server is slow or overloaded and does not respond in time.

✅ Best Practice

expert

Best practice to prevent 502 Bad Gateway during backend restarts

Which approach best prevents 502 Bad Gateway errors when restarting backend servers behind Nginx?

A Disable proxy buffering in Nginx

B Restart Nginx every time backend restarts

C Use Nginx health checks and remove unhealthy backends from upstream dynamically

D Increase client_max_body_size in Nginx

💡 Hint

Think about how Nginx can avoid sending requests to backends that are down.

Using health checks allows Nginx to detect backend availability and avoid sending requests to down servers, preventing 502 errors during restarts.

Practice

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

easy

A. nginx cannot get a valid response from the backend server

B. nginx configuration file has a syntax error

C. nginx server is overloaded with too many requests

D. nginx is running out of disk space

Solution

1. Step 1: Understand the meaning of 502 Bad Gateway

   A 502 error means the gateway (nginx) got an invalid response from the backend server it tries to connect to.

2. Step 2: Identify the cause related to backend communication

   This error is not about nginx config syntax or server load, but about backend response failure.

3. Final Answer:

   nginx cannot get a valid response from the backend server -> Option A

4. Quick Check:

   502 Bad Gateway = backend response failure [OK]

Hint: 502 means backend server response problem [OK]

Common Mistakes:

• Confusing 502 with nginx config syntax errors
• Thinking 502 means nginx is overloaded
• Assuming 502 is due to disk space issues

2. Which of the following nginx configuration directives is essential to correctly proxy requests to a backend server to avoid 502 errors?

easy

A. listen 8080;

B. root /var/www/html;

C. server_name localhost;

D. proxy_pass http://backend_server;

Solution

1. Step 1: Identify the directive that defines backend server address

   The proxy_pass directive tells nginx where to send requests, crucial for proxying.

2. Step 2: Understand other directives' roles

   listen sets port, server_name sets hostname, root sets static file location; none define backend proxy.

3. Final Answer:

   proxy_pass http://backend_server; -> Option D

4. Quick Check:

   proxy_pass sets backend URL [OK]

Hint: proxy_pass sets backend URL to avoid 502 [OK]

Common Mistakes:

• Using listen instead of proxy_pass for backend
• Confusing server_name with backend address
• Setting root instead of proxy_pass for proxying

3. Given this nginx error log snippet:
connect() failed (111: Connection refused) while connecting to upstream
What is the most likely cause of the 502 error?

medium

A. nginx has insufficient permissions to read files

B. nginx configuration syntax error

C. Backend server is not running or not accepting connections

D. DNS resolution failure for backend server

Solution

1. Step 1: Interpret the error message

   "Connection refused" means nginx tried to connect but backend server refused, likely because it is down or not listening.

2. Step 2: Rule out other causes

   Syntax errors cause config reload failures, permissions affect file access, DNS failure shows different errors.

3. Final Answer:

   Backend server is not running or not accepting connections -> Option C

4. Quick Check:

   Connection refused = backend down [OK]

Hint: Connection refused means backend server is down [OK]

Common Mistakes:

• Assuming syntax error from connection refused
• Blaming nginx file permissions
• Thinking DNS failure causes connection refused

4. You see a 502 error in nginx logs caused by upstream timed out. Which fix is most appropriate?

medium

A. Clear browser cache and cookies

B. Increase proxy_read_timeout in nginx config

C. Change server_name directive

D. Restart nginx service immediately

Solution

1. Step 1: Understand the timeout error

   "upstream timed out" means nginx waited too long for backend response.

2. Step 2: Adjust nginx timeout settings

   Increasing proxy_read_timeout lets nginx wait longer before giving 502 error.

3. Final Answer:

   Increase proxy_read_timeout in nginx config -> Option B

4. Quick Check:

   Timeout error fixed by increasing proxy_read_timeout [OK]

Hint: Increase proxy_read_timeout to fix upstream timeout [OK]

Common Mistakes:

• Restarting nginx without config change
• Changing server_name unrelated to timeout
• Clearing browser cache won't fix backend timeout

5. You fixed a backend server crash causing 502 errors. What is the correct next step to apply nginx changes and confirm the fix?

hard

A. Reload or restart nginx and check error logs for 502 errors

B. Clear browser cache and refresh the page

C. Edit nginx config to change server_name

D. Delete nginx access logs to free space

Solution

1. Step 1: Apply nginx configuration and backend fixes

   After fixing backend, reload or restart nginx to apply any config changes and reset connections.

2. Step 2: Verify fix by checking logs

   Check nginx error logs to confirm 502 errors no longer appear, ensuring the problem is solved.

3. Final Answer:

   Reload or restart nginx and check error logs for 502 errors -> Option A

4. Quick Check:

   Reload nginx and check logs to confirm fix [OK]

Hint: Reload nginx and check logs after backend fix [OK]

Common Mistakes:

• Only clearing browser cache without server reload
• Changing unrelated config like server_name
• Deleting logs instead of reading them