Website showing 502 bad gateway error during peak hours

Summary

This guide helps you troubleshoot and resolve: Website showing 502 bad gateway error during peak hours. Follow the steps below to fix the issue.

Common Causes

A 502 Bad Gateway error indicates that your web server, acting as a gateway or proxy, received an invalid response from an upstream server. During peak traffic hours, this usually points to server resource limits, upstream service timeouts, or proxy misconfigurations. For small business websites, these errors often occur when the hosting environment cannot handle concurrent visitor requests, causing the gateway to fail while waiting for a response from the backend application or database server.

Quick Fix Steps

1. Refresh your website after waiting one to two minutes to see if the error clears.
2. Clear your browser cache or test the site in an incognito window to rule out cached error pages.
3. Check your hosting provider's status page for any reported outages or maintenance.
4. If you manage your own server, restart the web server and application services.

Detailed Instructions

Check Server Resource Usage

1. Log in to your hosting control panel or connect to your server via SSH.
2. Open the system resource monitor to view current CPU and memory usage.
3. On Linux servers, run top or htop to identify processes consuming excessive resources.
4. Look for memory spikes or CPU usage consistently near 100% during peak traffic periods.
5. If resource limits are being reached, consider upgrading your hosting plan or optimising your website code and database queries.

Review Server Logs

1. Locate your web server error logs. Common file paths include /var/log/nginx/error.log or /var/log/apache2/error.log.
2. Open the log file using a text editor or run tail -f /var/log/nginx/error.log to monitor entries in real time.
3. Search for entries matching the time when the 502 error occurred.
4. Look for messages indicating upstream timeouts, connection refusals, or PHP-FPM errors.
5. Note any recurring patterns that correlate with high traffic periods.

Verify Upstream Service Configuration

1. Confirm that your backend application service is running. For example, check PHP-FPM, Node.js, or your application server status.
2. Review your proxy configuration file, typically located in /etc/nginx/sites-available/ or /etc/apache2/sites-available/.
3. Ensure the proxy pass directive points to the correct upstream address and port.
4. Check that timeout values are sufficient for your application's processing needs during peak load.
5. Reload the web server configuration after making changes using sudo systemctl reload nginx or sudo systemctl reload apache2.

If you are unsure about editing server configuration files, create a backup before making changes. Incorrect syntax in files like nginx.conf or .htaccess can take your website offline completely.

Avoid making changes to live production server settings during business hours unless you have tested them in a staging environment first.

If you have checked your server resources, reviewed logs, and verified your proxy configuration but the 502 Bad Gateway error continues during peak hours, your hosting environment may be outgrown for your current traffic levels. Contact your hosting provider to discuss upgrading your plan or migrating to a more robust infrastructure.

If you host with us, you don't need to do this yourself — just Open a Ticket and our team will get it sorted.

Still Having Issues?