504 Gateway Timeout

504 Gateway Timeout

Overview

A 504 Gateway Timeout error occurs when the Prophaze Web Application Firewall (WAF) does not receive a timely response from the backend application server. This article explains the most common causes and provides a structured resolution process.

Symptoms

Users may experience page load failures, interrupted downloads/uploads, or intermittent application accessibility issues accompanied by a 504 error message.

Common Causes 


This issue is often caused by:

  1. Slow backend application responses  

  1. Large file uploads or downloads

  1. Network latency or temporary connectivity issues

  1. Timeout values configured too low in the WAF

Resolution Steps

1. Navigate to Settings   → Application.



2. Identify the affected application or domain and select the Edit option to access its settings.


3.  Review the current timeout value (default is typically 60 seconds).

4. Increase the timeout value in small increments (for example, 60 → 65 seconds).

5. Save the configuration changes.

6. Retest the application and monitor for recurrence.

 Best Practices

Avoid large timeout increases in a single change. Increment values gradually and validate application performance after each modification. If issues persist, investigate backend server performance, application logs, and network connectivity.

Expected Outcome

After adjusting the timeout setting and validating backend responsiveness, the application should complete requests successfull without triggering a 504 Gateway Timeout error.