WordPress is a CMS application with a wide range of different applications and functions, which means there are also many errors that can be generated by them. In this guide, we show the most common and generic errors that WordPress may display:
Errors due to PHP resources
Sometimes, when trying to make changes to our WordPress or upload a file, WordPress shows an error indicating that it does not have sufficient resources to perform the action. Example:
fatal error: allowed memory size of 67108864 bytes exhausted (tried to allocate 122880 bytes)
This is one example of the many PHP resource errors that WordPress may generate. In most cases, it is only necessary to assign more resources to the hosting so it can perform the required action. To do this, you must access the PHP values management from the cdmon control panel:
How to configure hosting PHP
This error is one of the most common and also one of the most problematic, since when the white screen appears and no error is displayed, it provides no information to further investigate the issue.
For this error, trial and error is recommended, meaning performing checks until the white screen disappears or shows another error indicating its origin.
This white screen may appear for many reasons, but we show the 3 most generic checks to perform:
Debug mode
WordPress debug mode is a method that allows WordPress to store internal errors, so if we activate it, an error may be displayed on the page or the hosting error log may start storing errors in that file.
To activate debug mode, we must modify the "wp-config.php" file of our hosting. To do so, access your hosting via FTP (
How to connect via FTP using webFTP) and edit the wp-config.php file. Locate the line that says define( 'WP_DEBUG', false ); and change it to define( 'WP_DEBUG', true ); to activate debug mode:
Then access the white screen page or the server error logs to check whether additional information about the origin of the error is displayed.
Change active theme
Sometimes, the white screen is generated by a vulnerability or incompatibility of the active WordPress theme. In these cases, we recommend switching to the default WordPress theme (Twenty Twenty-One) to see if content appears.
If it works, the website may not display correctly since it was not configured for the default theme, but it confirms the theme was causing the issue.
IMPORTANT: The issue is not always caused by the theme; it may also be one of the active plugins. We recommend temporarily renaming the /plugins folder so the server does not detect it and loads the website without plugins.
PHP Compatibility
Most of the time, when WordPress requires increasing a PHP value, it indicates it. However, sometimes the white screen may appear without displaying this information.
We suggest verifying that the PHP version is compatible with your WordPress and installed plugins, and increasing the "memory_limit" to the maximum allowed by your hosting plan.
How to configure hosting PHP
The internal server error, better known as Internal Server Error or Error 500, is a well-known HTTP error that can appear on any page running on a server.
The reason this error appears is not due to the server itself, but to a function within WordPress that is generating it.
To find the origin of the problem, we must perform the same actions as in the previous white screen case:
- Change theme/template or plugin: It is very likely that the theme/template being used, or a plugin installed, is generating this 500 error. In this case, rename the /themes or /plugins folder respectively (for example to /themes1 or /plugins1) so the server does not detect them and the website can load without them. These changes can be made via FTP (How to connect via FTP using webFTP)
If the Internal Server Error disappears and the page displays content again, it means one of the themes or plugins was causing the error.
- .htaccess file: This file is one of the main files of the website, where all distribution configurations are stored. It defines how the website responds. If a plugin modifies the .htaccess file or it is modified manually via FTP, ensure the changes are correct.
It is very common for .htaccess files to generate this error. Before making changes, create a backup of the original .htaccess file so you can restore it if needed.
- PHP memory limit: It is also common for this error to appear because a WordPress function is consuming too many server resources. Usually this happens because the "memory_limit" or another PHP value is set below what WordPress requires.
To fix it, assign more PHP resources to your hosting. Go to the hosting management, access "Server", and modify the PHP values as required.
How to configure hosting PHP
IMPORTANT: As mentioned earlier, this error is generated by a WordPress tool/function. Restoring a backup from when the website worked correctly should make the error disappear. You can restore backups from the control panel:
How to restore a hosting backup
Error establishing database connection
This error is quite common when importing WordPress or making changes affecting the database. WordPress may not connect to the database due to configuration issues.
Check that the database name, username, and password match the server credentials. Open the "wp-config.php" file located in the /web folder of your WordPress.
How to connect via FTP using webFTP
Ensure the database name, username, and password match those in the "wp-config.php" file.
If they do not match, that is likely causing the connection error. Correct them and the error should disappear.
Connection is not private
This error commonly appears after installing a security certificate or uploading files.
First, verify that the hosting has an SSL certificate installed. Go to the hosting management, then "Security" → "SSL Certificates":
How to request an SSL certificate
If active and the error persists, force HTTPS navigation in WordPress. We recommend using the Really Simple SSL plugin to automatically make internal changes.
How to configure your SSL certificate
IMPORTANT: You can also force HTTPS via the .htaccess file by adding:
RewriteEngine On
RewriteCond %{HTTP_HOST} yourdomain\.com [NC]
RewriteCond %{SERVER_PORT} 80
If logs show a ModSecurity error (web application firewall), contact technical support.
Lost WordPress administrator password
If WordPress does not accept your login credentials, it may be due to a syntax issue.
You can use the “Lost your password?” option to recover it via email:
This error occurs due to a syntax error in a WordPress file. It displays "Parse error: syntax error" along with the affected file and line.
Parse error: syntax error, unexpected end of file in /usr/home/example.com/web/wp-content/themes/twenty/functions.php on line 95
Access the file and correct the code carefully. These changes directly affect your website’s programming.
This error appears when the browser cannot complete the connection and shows ERR_CONNECTION_TIMED_OUT.
This often happens when hosting does not have sufficient memory assigned.
This affects website layout display. The page appears completely misconfigured and content displays randomly.
Usually caused by theme or plugin incompatibility. Try switching themes or deactivating plugins one by one.
Scheduled posts are not published
If you changed the PHP version or there was an automatic update, WordPress scheduled publishing may fail.
These tasks are scheduled in the "wp-cron.php" file.
Plugins like WP-Missed-Schedule can monitor and trigger missed posts.
WordPress does not send emails
WordPress may have issues sending emails via web forms.
This may be due to incorrect configuration of the mail application. Verify settings first.
IMPORTANT: If cdmon servers detect suspicious or injected code activity, web mail sending may be disabled until reviewed. To increase WordPress security, use anti-spam and protection plugins:
Plugins to increase WordPress security