How to Fix a 504 Error in WordPress (UK Guide 2026)
17 August 2026
Need to fix a WordPress 504 error? This UK-specific guide covers quick fixes, plugin conflicts, and hosting support to get your site back online fast.
What Is a 504 Error and Why Does It Occur?
A 504 Gateway Timeout error means your web server didn't get a timely response from another server (often WordPress's PHP processing). In simple terms, the server gave up waiting. On UK-hosted WordPress sites, this commonly happens due to PHP execution time limits, memory exhaustion, plugin conflicts, or an overloaded shared server. Other culprits include poorly coded themes, external API calls, or even a spike in traffic during peak UK business hours. Understanding the root cause is your first step; without it, the error will likely return. Don't panic—a 504 is usually temporary and fixable without losing content, provided you follow the structured troubleshooting steps below.
UK Quick Fixes: Get Your Site Back Up in Minutes
Before diving into technical fixes, try these quick solutions that often clear a 504 error. First, refresh the page: sometimes the timeout is transient. If that doesn't work, restart your browser or clear its cache. Next, use a UK-based uptime checker like UptimeRobot or ping your site from a different network (e.g., mobile data) to see if the issue is local. Also, check if your hosting provider—whether it's 123 Reg, Fasthosts, Krystal, or another UK company—has a status page or announced maintenance. If the site is down for everyone, your host may be having issues. In that case, contact their UK support line directly, as many offer 24/7 phone and live chat.
Increase PHP Timeout: A Step-by-Step Guide (cPanel & wp-config)
A common UK host setup uses cPanel, where PHP timeout limits can be too strict for WordPress. To increase the limit, log into cPanel, open the 'MultiPHP INI Editor' (if available), and set max_execution_time to 300 or higher. Alternatively, edit your wp-config.php file via FTP or File Manager. Add the line: set_time_limit(300); near the top, after the opening PHP tag. For Apache servers, you can also add a line to .htaccess: php_value max_execution_time 300. Save and refresh. Remember, some UK hosts (e.g., shared plans) restrict this; if the change isn't applied, contact your host to adjust it server-side. This fix resolves many timeout-based 504 errors.
Troubleshoot Plugins and Themes Causing the 504 Error
Plugins and themes are the most frequent triggers for 504 errors on WordPress. A plugin with a slow external request or a memory-hungry script can exceed the server timeout. To isolate the problem, disable all plugins temporarily. If you can't access the admin dashboard, use FTP or your cPanel File Manager to rename the /wp-content/plugins/ folder (e.g., to 'plugins_old'). WordPress will then load with no plugins, which usually clears the 504. If that works, re-enable plugins one by one, testing after each. Similarly, switch to a default theme like Twenty Twenty-Four via FTP. For UK users, ensure your themes and plugins are compatible with the latest PHP version your UK host provides.
When to Contact Your UK Host: Server-Level Solutions
If you've tried everything above and the 504 persists, it's time to escalate to your hosting provider. UK hosts like Krystal, 20i, and IONOS often have excellent technical support teams. Ask them specifically to: 1) increase PHP memory limit and max execution time, 2) check server error logs for PHP fatal errors, and 3) review whether your site is hitting CPU or RAM limits on a shared server. Many 504 errors stem from your site exceeding resources allocated by the host. In some cases, upgrading to a VPS or dedicated plan is the permanent fix. Always mention the exact URL where the error appears and the time it occurs—this helps UK support teams pinpoint the issue quickly.
FAQ
A 504 Gateway Timeout error occurs when one server (like your web server) doesn't receive a timely response from another server (like WordPress's PHP engine). Essentially, the request hung up. It's different from a 500 error because it's about timeouts, not a crash. In WordPress, this often means a script took too long to execute.