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.