Proxy timeouts in Nginx - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the effect of this nginx proxy timeout setting?

Given the nginx configuration snippet below, what will happen if the backend server takes longer than 10 seconds to respond?

Nginx

proxy_read_timeout 10s;

A nginx will wait indefinitely for the backend server to respond.

B nginx will retry the request automatically to the backend server.

C nginx will close the connection and return a 504 Gateway Timeout error to the client.

D nginx will return a 502 Bad Gateway error immediately.

💡 Hint

Think about what 'proxy_read_timeout' controls in nginx.

The proxy_read_timeout directive sets the time nginx will wait to receive a response from the backend server. If the backend takes longer than this time, nginx closes the connection and returns a 504 Gateway Timeout error.

❓ Configuration

intermediate

Which configuration sets the maximum time nginx waits to establish a connection to the backend?

Select the correct nginx directive to limit the time nginx waits to connect to the backend server.

A proxy_connect_timeout 5s;

B proxy_send_timeout 5s;

C proxy_read_timeout 5s;

D client_body_timeout 5s;

💡 Hint

Connecting to backend is different from sending or reading data.

proxy_connect_timeout sets the timeout for establishing a connection to the backend server. Other timeouts control sending or reading data.

❓ Troubleshoot

advanced

Why does nginx return a 504 error despite a high proxy_read_timeout value?

An nginx server has proxy_read_timeout 120s; but clients still get 504 Gateway Timeout errors after 60 seconds. What is a likely cause?

A The backend server closes the connection after 60 seconds.

B The client closed the connection before 60 seconds.

C The proxy_connect_timeout is set to 60 seconds.

D The client_body_timeout is set to 60 seconds.

💡 Hint

Consider what controls the backend server's behavior.

If the backend server closes the connection early, nginx cannot receive data and returns a 504 error even if its timeout is longer.

✅ Best Practice

advanced

What is a recommended practice to avoid proxy timeout errors in nginx for slow backend responses?

Choose the best practice to handle slow backend responses without causing frequent 504 errors.

A Set proxy_connect_timeout to 1 second to fail fast.

B Increase proxy_read_timeout to a value longer than the expected backend response time.

C Disable proxy_read_timeout to wait indefinitely.

D Set client_body_timeout to a very low value.

💡 Hint

Think about how to give backend enough time to respond.

Increasing proxy_read_timeout allows nginx to wait longer for slow backend responses, reducing 504 errors. Other options either cause premature failures or are unrelated.

🔀 Workflow

expert

Order the steps to troubleshoot nginx proxy timeout errors effectively

Arrange the steps in the correct order to troubleshoot frequent 504 Gateway Timeout errors in nginx proxy setups.

A 2,3,1,4

B 1,3,2,4

C 1,2,3,4

D 3,2,1,4

💡 Hint

Start by understanding backend behavior before changing nginx settings.

First test backend response times, then check backend logs, next review nginx timeout settings, and finally adjust nginx configuration accordingly.