Handling 504 and 502 Errors in Pyramid

If you're encountering 504 or 502 error messages, the issue is likely related to the reverse proxy or load balancer sitting in front of Pyramid. These errors often occur due to timeouts that are set too low. To prevent such issues, it's recommended to increase the timeout values on your reverse proxy and load balancer to at least 10 minutes.

Increasing Timeout Settings in Nginx Reverse Proxy

If you're using Nginx as a reverse proxy, follow these steps to increase the timeout settings:

1. Open your nginx.conf file, typically located in /etc/nginx/nginx.conf or inside your site's configuration file under /etc/nginx/sites-available/.

2. Locate or add the following directives inside the server or location block:

   proxy_connect_timeout 600s;
   proxy_send_timeout 600s;
   proxy_read_timeout 600s;
   send_timeout 600s;

3. Save the file and restart Nginx to apply the changes:

   sudo systemctl restart nginx

This increases the timeout settings to 10 minutes (600 seconds), reducing the chances of timeout-related 502 and 504 errors.

Increasing Timeout Settings in IIS

If you are using IIS, follow these steps to increase the timeout:

1. Open IIS Manager on the Pyramid web servers.

2. Double-click on Application Request Router Cache.

3. Click on Server Proxy Settings.

4. Locate the timeout settings and double the current value (or increase it to at least 10 minutes).

5. Click Apply to save the changes.

Other Web Servers and Load Balancers

If you are using any other third-party web server or load balancer, please refer to its documentation on how to increase its timeouts.

By increasing these timeout settings, you can ensure that your Pyramid application remains stable and minimizes 504/502 errors caused by timeouts.