500 Internal server error
A 500 error is a generic server-side failure. In WordPress, it is most commonly caused by:Corrupted .htaccess file
Corrupted .htaccess file
A broken
.htaccess file is the most frequent cause of 500 errors. To fix it:- Access your site files via the Hoop file manager or SFTP
- Rename
.htaccessto.htaccess_backup - Reload your site — if the error is resolved, the file was the issue
- Go to Settings > Permalinks in WordPress and click Save Changes to regenerate a clean
.htaccessfile
PHP memory limit exceeded
PHP memory limit exceeded
If your site runs out of memory, PHP crashes with a 500 error. Increase the memory limit by adding the following line to your Save the file and reload your site.
wp-config.php file:Plugin or theme conflict
Plugin or theme conflict
A recently activated plugin or theme update can trigger 500 errors. Rename the
wp-content/plugins folder to wp-content/plugins_disabled via the file manager to deactivate all plugins at once. If the site loads, re-enable plugins one at a time to identify the offending plugin.502 Bad gateway
A 502 error means the web server received an invalid response from an upstream process (typically PHP).Check for PHP process crashes
This often indicates a PHP fatal error. Check the Error Logs section in your Hoop WordPress hosting dashboard for recent PHP errors.
Increase PHP execution time
If a script is taking too long, the PHP process may be terminated. Add the following to
wp-config.php:503 Service unavailable
A 503 error indicates the server is temporarily unable to handle requests. Common causes in WordPress:| Cause | Solution |
|---|---|
| Maintenance mode active | WordPress enters maintenance mode during updates. If an update was interrupted, delete the .maintenance file from the WordPress root directory |
| Server resource limits | High traffic or resource-intensive plugins can exhaust server capacity. Consider upgrading your Hoop hosting plan or enabling a caching plugin |
| Cron job overload | Poorly configured WP-Cron tasks can stack up and consume resources. Add define('DISABLE_WP_CRON', true); to wp-config.php and set up a real server cron instead |
504 Gateway timeout
A 504 error means the server did not receive a timely response from an upstream process. This is common during:- Large database queries on pages with complex content
- Plugin operations that make external API calls (e.g., backup plugins, SEO crawlers)
- Bulk import or export operations
Identify the slow operation
Check which page or action triggers the 504. If it happens on specific admin pages, a plugin on that page is likely causing the delay.
Deactivate heavy plugins temporarily
Disable plugins related to backups, migration, or real-time analytics. Reload the page to see if the timeout resolves.
Database connection errors
If you see “Error establishing a database connection”, the issue is between WordPress and the MySQL database:- Verify the database credentials in
wp-config.phpmatch the values in your Hoop hosting dashboard under Database Settings - Check whether the database server is running — go to your Hoop hosting dashboard and look for the database status indicator
- If the database has exceeded its storage quota, you may need to clean up unused data or upgrade your hosting plan
A corrupted database table can also cause connection-like errors. If credentials are correct but the error persists, use phpMyAdmin (available in your Hoop hosting dashboard) to run a Repair Table operation on the
wp_options table.PHP version issues
WordPress and its plugins require specific PHP versions. Running an incompatible version can cause errors ranging from blank pages to fatal crashes.- WordPress 6.x requires PHP 7.4 or higher (PHP 8.1+ recommended)
- Check your current PHP version in Hoop Hosting Dashboard > Site Settings > PHP Version
- If a plugin requires a newer PHP version, update the version in the dashboard and test your site immediately
.png?fit=max&auto=format&n=EQK5eX9kTD8NzWwA&q=85&s=878008bf159fcc4964d0c0d508b6e400)