Some of them may be minor WordPress errors, but others may pose real problems. Website downtime, faulty updates, improper installation and loss of resources may prevent visitors from accessing or using your site. These problems may damage your credibility and potentially negatively affect your income.
It’s almost impossible to know all of the potential WordPress errors inside and out. However, understanding some of the common problems users face may help you to address them when they arise.
This post includes the most common WordPress errors, as well as information that can help you bypass each one of them so that you can restart your site as quickly as possible.
Errors with numbers between 400 and 499 are HTTP client errors and not specifically WordPress errors. This usually means that an error has occurred during the communication between the browser your visitor is using and the server of your site.
400 Bad Request error
Error 400 occurs when your server encounters a client error, but it does not fall into a particular category. This means that this error has several possible causes, including:
The URL is incorrectly typed or contains illegal characters.
Corruption of browser cache or cookies.
Mismatch between your Domain Name System (DNS) data and your DNS.
Try to download a huge file.
A type of generic server error.
Potential solutions include checking the URL for misspellings, clearing the browser cache, cookies and DNS, and deactivating browser extensions.
403 Forbidden error
There are several measures taken to keep your WordPress site safe, including various levels of “Permissions / Permissions”. While this feature can prevent people who should not have access to your site from accessing your site, it can also sometimes cause problems if the access permissions are not set up properly.
To fix it, you should reset your file permissions or create .htaccess file. (File that controls advanced configuration of your site) New. This problem could also be caused by a problem with a plugin, in your CDN, or with hotlink protection.
404 Not Found
A 404 error occurs when a user attempts to access a webpage that does not exist. Instead of finding the page they’re looking for, they’ll see a page similar to this one:
404 Not Found
404 Not Found
This problem is relatively harmless but nonetheless frustrating for users. To avoid this, make sure to fix corrupted links on your site periodically and perform redirects in case you delete a page or move it to a new URL.
405 Method Not Allowed error
Error 405 “Method not allowed” is your server’s way of saying that it has received a browser request but is rejecting it for some reason.
There are several possible ways to solve this problem, including rolling back the latest template updates and plugins, checking server settings and error logs, and manipulating the template code to make sure it is free from any errors.
Error 413 Request Entity Too Large
If this error appears in your browser, this means that the server of the site you are trying to access cannot handle the HTTP request that you submitted because it is too large.
This often happens when you are trying to download a very “heavy” file. You can solve this problem by increasing the maximum HTTP request size.
Error 429 Too Many Requests
If a user tries to access a specific page several times within a short period of time, he or she may receive the error 429 “Too many requests”. This is your server’s way of blocking suspicious behavior.
To help prevent cyber attacks on your login page that could lead to a 429 error, you can change its URL. Other solutions include testing for template and plugin conflicts.
Any error in your site with a number between 500 and 599 is an indication that your server is unable to fulfill a request directed to it for some reason. Here are some of the more common examples.
500 Internal Server Error
In addition to preventing users from accessing your site, the 500 “Internal Server Error” error can negatively affect your site’s SEO if it is not resolved quickly: Image
Unfortunately, there are many causes and solutions for a 500 error, which makes it difficult to address this problem. You can start by clearing your browser cache and reloading the page. If that doesn’t work, you can dive into more advanced methods. (Link to article for advanced methods)
501 Not Implemented Error
This error means that your server does not have the necessary elements to complete the request directed from the user’s browser. It is possible that the server does not understand the request method.
Like error 500, the 501 error can lower your site’s ranking in the search engine if you don’t process it within a few hours. You can try reloading the page, clearing the browser cache and deactivating any active proxy settings to solve the problem.
Either way, it is likely that you will need to contact the hosting company for help.
Arahoster hosting company is known for its excellent technical support, see our WordPress hosting.
502 Bad Gateway error
In the event that one of the servers is acting as a proxy (proxy) or “gateway” to another server, there is a possibility that users will encounter the error 502 “Wrong Entry”. This occurs when the proxy receives an invalid response from the internal server.
The 502 error also affects SEO, so it is best to get rid of it quickly.
Reloading the page and clearing the browser cache are a good start. If these solutions don’t work, check for DNS issues, try disabling the CDN or firewall
Or, contact your host for help.
10- 503 Service Unavailable error
When the 503 “Service is not available” error appears, this means that for some reason your server cannot be reached. Even though your site is running, it will not be accessible to users.
This could be due to routine maintenance, high traffic levels or a more serious problem with your server. The good news is that the 503 error will not affect your site’s ranking in search engines. However, it is still extremely annoying for visitors.
To fix this error, you can try the following:
Deactivate your plugins
Switch to a default template
Limit the WordPress Heartbeat API
Increase your server resources
If none of these solutions work, the best course of action you can take is to contact the support team at your hosting company.
11- 504 Gateway Timeout error
As with Error 502, the 504 error response is the result of a communication problem between an internal server and a proxy. Basically, this means that the last server timed out while the previous server was waiting to respond to the request.
This kind of error can negatively affect your SEO. Possible solutions include reloading the page, disabling any active proxy settings, checking for any problem that might exist in the DNS and temporarily disabling the CDN.
The server is responsible for storing all of your WordPress site files and for communicating with browsers to make your site content available to users.
12- WordPress Memory Limit Error
Your hosting provider allocates a certain amount of server memory to your site. If you reach the maximum server memory, you may encounter problems installing new plugins or themes, or uploading media files to your site.
Instead of successfully adding the new file or component, you will see a message that reads: “fatal error: allowed memory size has been exhausted” meaning “The allowed memory is exhausted”. If this happens, you can try to increase the PHP memory limit by modifying your wp-config.php file.
Alternatively, you can reveal the disk space you’re using and consider upgrading to a larger hosting plan that provides more space for your growing WordPress site.
13- Error Uploaded File Exceeds the upload_max_filesize Directive in php.ini
Likewise, your host also allocates a maximum size for individual files that you can upload to your server. You can see this limit by entering Media> Add New in your WordPress dashboard, and looking for the maximum upload file size.
If you need to upload a file that is larger than the specified maximum, you can change the limit by modifying your php.ini file. Alternatively, you can reach out to your hosting provider to discuss the matter with them.
This is much simpler and less risky than trying to change it yourself and shouldn’t be a problem for your hosting company’s support team.
14- Fatal Error: Maximum Execution Time Exceeded
Servers have time limits for running scripts (usually 30 seconds). If your php script is taking longer than the specified time limit, you may see the message: “Fatal error: Maximum execution time exceeded”.
You can solve this problem by increasing the execution time limit on your site. To do this, you’ll need to find and remove the text file that is taking a long time to work, and which is likely part of an add-on or template.
15- Upload: Failed to Write File to Disk error
Adding images to your posts and pages can make them more informative and interesting and increase your free traffic. However, you will find it difficult to do this if you see the message: “Upload: Failed to write file to disk” for every attempt you make to add a media file to your site.
This error is usually caused by erroneous file statements. You can fix this problem by changing file permissions / permissions via FTP.
However, it could be a problem with your server. When you upload files to WordPress, they are first saved as temporary files on the server. After that, they will be taken to the appropriate WordPress directory. If changing the file permissions did not fix this error, contact your host and ask them to empty your temporary files directory, as it might be full and prevent files from downloading.
16- Secure Connection Error
When updating the WordPress installation base files, your site must connect to WordPress.org. Sometimes this is not possible due to your server configuration. The result is a warning in your WordPress dashboard.
Since this is a problem directly related to your server, you will likely need to contact the hosting company to fix it. It is possible that your server is undergoing a DDoS attack, in which case the error should fix itself within a short time. Alternatively, you can try to fix it yourself by pointing the server toward WordPress.org through Secure Transfer Protocol (SSP).
Security related errors
It is wise to provide your site with the best of WordPress security.
Cyber attacks can cause massive damage that costs a lot of money to repair.
Unfortunately, sometimes the measures you take to protect your site lead to errors.
You can read our article discussing whether WordPress is more hackable than others
17- Cloudflare error 521
Although this is a 500 error like the ones we described in a previous paragraph, it is specific to Cloudflare. This popular platform is used as CDN, to protect against DDoS attacks and more.
Error 521 p
To your location means that Cloudflare cannot connect to your server. Either it is down or it is blocking the service for some reason. Generally speaking, verifying that your server is up and that its firewall has all of the Cloudflare IP address ranges whitelisted will let you know what is causing the problem. Then you can take steps to work with your host in resolving the problem.
18- “Sorry, This File Type Is Not Permitted for Security Reasons” error
As a security measure, WordPress includes a standard list of allowed file types. This measure prevents malicious parties from adding executable breach files to your site that could put users’ personal information at risk.
If a user tries to upload a file type that is not listed in this list, a message will appear that reads: “Sorry, this type of file is not allowed for security reasons.”
You can enable uploading of disallowed file types in the default WordPress configuration by modifying your wp-config.php file.
Alternatively, the WP Extra File Types plugin can be used.
19- “Sorry, You Are Not Allowed to Access This Page” error
We briefly touched on file permissions / permissions earlier in this post, but as a reminder, they specify who can edit files on your WordPress site. This keeps your site safe from hacker hackers who may want to insert malicious codes into your site.
However, if your permission settings are incorrect, it is possible that you or your well-meaning visitors will be inadvertently blocked from accessing your site.
This may result in an error that reads: “Sorry, you are not allowed to access this page”.
There are several possible solutions to this problem. You may want to try:
Reset your file permissions via Secure File Transfer Protocol (SFTP).
Check that your account is taking the right user role with phpMyAdmin.
Ensure that the prefix (prefix name) of your database is correct.
Troubleshoot a conflict between plugins and the theme.
In the worst case, you can restore your site backup or reset WordPress.
20- “Installation Failed: Could Not Create Directory” Error
Whenever you install a plugin or theme on your WordPress site, its files are added to your server. If you receive a message that reads: “Installation failed: Could not create directory” during installation, this means that WordPress was not able to add the necessary files to your raw material for some reason.
This also applies to additions and template updates. This is another error regarding file statements.
To fix this, make sure you have write permission to the wp-admin, wp-content and wp-includes directories via FTP.
21- Incorrect File Permissions Error The file statements are incorrect
In addition to preventing you from accessing certain areas of your site, as in the case of Error # 19, false statements can prevent you from:
Update or install plugins or templates.
Post or update posts or pages.
On the other hand, if your file permissions aren’t too strong, you are putting your site at risk and you risk hackers getting access to your files. Then they can delete the content, steal the data, or even add their own malicious code.
If you’re experiencing one of the above issues, or suspect you have been hacked, you may need to check file permissions via SFTP:
The default WordPress numeric values are 755 for folders and 644 for files.
SSL Certificates are a security measure used to encrypt data. This prevents hackers from stealing sensitive data such as credit card information while it is being transferred between servers.
If you recently switched hosting providers or installed a new SSL certificate on your domain, you might see an ERR_SSL_PROTOCOL_ERROR error in your browser. This means that for some reason, your server was unable to establish a secure connection.
There are several steps you can take to solve this problem, including updating your browser and operating system, checking the SSL certificate, disabling browser extensions, and clearing the browser’s cache and cookies.
Read more about SSL Certificates
This error may indicate that your browser or operating system is out of date. It may also be caused by problems with your SSL certificate, or appear suddenly after you have moved your WordPress site to a new host. If updating your browser or operating system doesn’t help, check if there is a mismatch for your SSL certificate name.
Alternatively, clearing the SSL status on the computer may solve this problem, or your SSL certificate may be out of date and need to be updated.
24- Mixed Content Warnings Warning
When you add an SSL certificate to your WordPress site, it will start running HTTPS instead of HTTP. If your site is trying to upload HTTPS and HTTP content or scripts at the same time, you will see a content mixing warning.
This could be read as another type of error: “This site is completely insecure”. To resolve this error, you will need to follow a few steps to determine which HTTP resources are loaded and remove or replace them with HTTPS resources.
WordPress Media Errors
In the WordPress world, the word “media” often refers to image files. However, it also includes video and audio. Although these elements may provide users with attractive and interesting content, it is difficult to incorporate it at times due to the many errors that may arise during the process.
25- WordPress HTTP error (upload an image to media library)
While trying to upload an image to your WordPress media library, you might encounter an unclear “HTTP Error”. This is generally shown on u
Each small box pops up on the right side of the image downloader.
There are a few possible causes for this problem, including an expired login session, unauthorized characters in the file name, wrong permission, and server-related issues.
First, start by refreshing the page. If that doesn’t work, try resizing or renaming the media file. If you are not lucky with this, then you should verify your permissions or disable the plugins and theme temporarily. If you still cannot complete the download, you may want to contact your host.
26- The “Add Media” button is not working
In the traditional WordPress editing program, the add media button is an important feature.
This button allows you to quickly upload new media files or select a file from your media library to add to your post. However, sometimes pressing the button does nothing or it may be missing from the editor completely.
If this is the case, the issue is most likely caused by plugins conflicting with each other or with the theme. You can solve this problem by adding the declaration function (‘CONCATENATE_SCRIPTS’, false) to the wp.config.php file or by troubleshooting potential compatibility errors.
27- Broken media files
If you open your media library and find that all images are completely lost or replaced with a gray file icon, your files may be “broken”.
This can happen for multiple reasons, including:
A problem with your server, such as a performance problem.
Compatibility errors between plugins and / or theme.
Wrong file statements.
Hacking or other attack.
To fix the problem, you can try to reset the file permissions for the Downloads directory to 755. If that doesn’t work, check if there are any conflicts between the extensions. Then, if your images are still down, contact your hosting provider to see if the cause is a server issue.
28- “There was an error cropping the image.”
In the WordPress media library, you can make simple adjustments to the images you upload, such as rotate and crop. While trying to edit this way, you might get the message: “There Has Been an Error Cropping Your Image”.
There are two possible causes for this error. The first reason is that you are working on an old version of PHP, in this case you can simply update it to fix the problem. On the other hand, your server may have lost the necessary GD package. If this is the case, you must follow the appropriate steps to install it depending on your settings.
In case you encounter any problem, you should contact your hosting provider for assistance.
29- Incorrect Facebook Thumbnail Error
Incorrect Facebook thumbnail image
Social media sharing can be an effective way to build your site’s audience. However, it is possible to display a wrong “Thumbnail” thumbnail when sharing your posts to Facebook.
This often happens when you include multiple images from your posts on the Open Graph (OG) tag. Facebook uses this tag to identify the image that is supposed to be a Thumbnail, but when the tag is present on multiple images, the platform becomes confused.
One way to fix this problem is to use the sharing features of Yoast SEO. By setting up Facebook Thumbnail images with this plugin, you can ensure that the correct image is the one containing the OG tag.
Also read the best times of social media publishing and our article about the colors of the ads you use on social media.
The WordPress installation consists of two main parts: its files and its database. While you are likely to handle files on a regular basis, a database is also essential for your site to function properly.
30- “Error Establishing a Database Connection”
In the event that your site is not able to establish a connection to your MYSQL database, it will not be able to retrieve the data needed to display your content. Instead, you will see the mentioned error.
This prevents users from viewing the main interface of your site, and also prevents you from entering your WordPress dashboard. The most common cause of this error is that your database data is incorrect. You can change it in your wp-config.php file.
31- “The WordPress Database Is Corrupt”
“Corrupted or corrupt” in this context applies to WordPress databases and files when they become unusable or have been compromised. This will often result in an error establishing the database connection.
Normally, you will need to restore a backup copy of your database to replace the damaged copy. If this is not possible, you can also fix this error by adding the meta function (`WP_ALLOW_REPAIR`, true) to your wo.config.php file.
PHP is an integrated markup language for WordPress. The issues related to it can prevent you from editing your site or result in intrusive messages and notifications.
32-PHP Errors in WordPress
When there is a problem with your WordPress site PHP, you will see a message or warning at the top of your WordPress dashboard explaining the problem and the files involved.
These messages are intended for developers, so that they can search the site code and redirect the issue. If you do not have PHP experience, your attempt to resolve these errors may lead to more problems for your site.
If this describes your condition, don’t panic. PHP errors usually don’t prevent your site from functioning or users’ access to it.
You will want to contact the developer of any related plugins or themes that might be causing the problem. On the other hand, you can hire a developer to help you fix the error.
33- Fault loss
“Missing a Temporary Folder”
Every time you upload a file to your WordPress site, it is first stored in a temporary directory before moving it to its permanent directory. However, wrong PHP settings on your server may prevent access to these temporary folders, resulting in an error in your WordPress site.
Solving this issue requires accessing your server via FTP and adding the following functionality to your wp.config.php file:
define (‘WP_TEMP_DIR’, dirname (__ file__). ‘/ wp-content / temp /’);
After that you can add a new file named temp to your wp.content directory.
WordPress file errors
From your posts and pages to your own plugins and themes, the WordPress installation contains hundreds if not thousands of files. Errors associated with these essentials can result in content being lost or unavailable.
34- “Destination Folder Already Exists”
When you install a theme or plugin on your WordPress site, a directory is created on your server to store its files. If you tried to install an add-on or template, and a folder with the same name was previously saved on your server, you will see an error stating “The file destination already exists… Installation of the plugin failed”:
The first step to take when encountering this problem is to check to see if the theme or plugin is already installed.
If not, then access your server via FTP and navigate to the wp-content file. Then search among your plugins and themes for the presence of a file with the same name as the item you are trying to install. Once you delete this file, you can try installing again.
35- The WordPress Theme Stylesheet Is Missing
CSS is the markup language that defines the “design” of your site. This could include colors, fonts, and a variety of other elements that make your site interesting.
When it comes to WordPress themes, all CSS codes are contained in a file called “Stylesheet”. If your template design file is not available, your site will not be able to load properly, and you will see the said error.
This error may also occur during the installation process of a template.
This could happen because the template’s design file was not uploaded to your server, or because it was named incorrectly and therefore cannot be found.
To solve the problem, log in to your server via FTP and navigate to template subdirectory.
Then find the Stylesheet template design file. If it does not exist, retrieve it from your template files and upload it to your server. Make sure the file is named style.css and is saved in the correct template directory.
36 – Pluggable.php file errors
The pluggable.php file for WordPress allows users, plugins, and themes to bypass the platform’s core functionality. If the plugin or theme is not encoded correctly, it may cause a conflict with this file.
The problem will appear as a PHP error message on your WordPress dashboard and refer to the pluggable.php file. However, the cause of the problem is not usually in the pluggable.php file itself, it could be in, for example, wp.config.php or function.php.
Instead, you’ll need to find the true location of the problem in the error message. Then go to the relevant file and fix it by removing spaces or blank lines and so on.
37- WordPress files are corrupted
Just as a WordPress database can become corrupted, its files can also become corrupted. This will lead to it being inaccessible, which is a big problem, especially when it comes to essential files.
Corrupted files could be the result of server failure, incorrect file declarations, or a PHP version error. The simplest solution is to restore a website backup. This is a matter of a few clicks in Arahoster.
First, log into your Arahoster dashboard. Go to “Timeline Backups” and click on the copy for which you need to restore a backup. Visit the Explanations Library for additional information on the topic.
Alternatively, you can replace core files by uploading WordPress, deleting corrupted files via FTP, then uploading fresh copies of the zip file. For WordPress.
Visitors access your website using the browsers of their choice. This means that various browser errors can prevent users from accessing your site. Preventing them will help you avoid losing visits.
38- “Not Secure” warning in Chrome.
When browsing the Internet with Google Chrome, you may notice that some pages contain an “unsafe” warning next to their URLs.
This warning appears in the browser when a site is not using an SSL certificate. If your pages cause these messages to appear on your users’ browsers, it could damage your site’s reliability, affect traffic level, SEO results, and conversion rates. To prevent this from happening, you can install an SSL certificate.
Recently, Chrome started showing ERR_SSL_OBSOLETE_VERSION warning messages for sites that don’t use TLS 1.2 or 1.3.
39-“Your Connection Is Not Private” Browser Error
The worst of the “Not secure” warning in Chrome is the “Your connection is not private” error. This error prevents users from accessing your site, due to a problem with your SSL certificate (or not it at all).
If users encounter this page, they can panic about your site for fear that their personal information will be stolen. You can try to prevent this from happening by making sure that the SSL certificate is installed correctly, but this could be a visitor’s issue that users will have to solve on their own.
The redirect loop occurs, often shown as ERR_TOO
_MANY_REDIRECTS Any error Large number of redirects, when there is a misconfiguration of redirects on your server.
For example, this might mean that URL 1 points to URL 2, but URL 2 points again to URL 1, causing unlimited duplication. Users can try to fix this by clearing your cookies and deleting their browser cache. You can also try to determine the nature of the redirect loop, in order to find out the source of the problem, and then solve it.
Like many browser problems, ERR_CONNECTION_REFUSED is usually not caused by something related to WordPress. However, if your users are contacting you because they are unable to access your site due to this message from Chrome, it is helpful if you are able to tell them how to fix the problem.
ERR_CONNECTION_REFUSED error occurs, meaning the connection was rejected, because the user’s browser was unable to contact your site’s server. This could be a server issue, in which case you should check to see if your site is down and contact your hosting provider. Alternatively, you can instruct users to restart their routers and clear browser cache.
The ERR_EMPTY_RESPONSE problem occurs when a user’s browser sends a request to your site and your server is not sending anything. The most common solutions to this problem are to clear your browser cache and reset your network settings.
You may also want to advise users who are experiencing this problem to disable any Chrome extensions they are using and temporarily turn off the anti-virus program.
43 – ERR_PROBE_FINISHED_XNDOMAIN Browser Error
Your DNS is the system that takes your website’s IP address and turns it into a readable domain, like Arahoster.com. If your DNS fails to translate your domain to your site’s IP address correctly, users will see ERR_PROBE_XNDOMAIN Browser Error.
The first steps to solve this problem is to renew your IP address. If that doesn’t work, you could suggest that users disable their anti-virus software or Virtual Private Networks (VPNs) temporarily.
Various WordPress troubleshooting
While many WordPress errors can be traced back to a specific cause, others are more difficult to diagnose. They may have multiple potential assets or trace back to minute details that don’t seem important.
Here are a variety of WordPress issues that don’t fit well into the categories we’ve covered so far.
44- The white screen of death
One of the most common WordPress errors is the White Screen of Death. This error causes your site to display as a blank blank page to its users. This issue might also prevent you from accessing your WordPress dashboard. This error is usually caused by a plugin compatibility issue.
The best course of action to solve the problem is to find and remove the extension that is causing the problem. Other possible causes include code syntax errors, your site’s memory limit, or file declaration errors.
45- Error denying access to the WordPress admin dashboard
Your WordPress dashboard is extremely important for many tasks, including fixing many common WordPress errors. However, sometimes the problems you encounter on your site can prevent you from accessing your WordPress dashboard.
There are many possible causes for this problem. If you can, try to determine if your entry has been blocked due to a separate issue, then take steps to solve the problem at its root. You can also try restoring a backup copy of your site, or disable an FTP plugin if you think it is preventing you from accessing the backend of your site.
46- Cannot connect via SSH or SFTP
Sometimes, WordPress administration or troubleshooting requires direct access to your server. SFTP enables you to access your files, SSH allows for a variety of remote execution tasks.
If you are trying to use SFTP or SSH to access your server but cannot connect, it is possible that you need to delete outdated IP addresses from your known_hosts file.
47- SSH connection refused
In the event that you are trying to connect to your server via SSH, and you see a message that says “Connection denied” on your taskbar interface, the problem is a little different.
Instead of editing the known_hosts files, you’ll need to check a few things about your SSH configuration.
First, make sure that SSH is installed on your server. You should also check your credentials and determine if the port you are using is open.
The problem could also be caused by your firewall settings.
48- Temporarily unavailable due to “Briefly Unavailable for Scheduled Maintenance”
When you run updates on your WordPress site, it temporarily goes into maintenance mode. During this time, anyone trying to access your site will see a message saying something like: “Not available for a while for scheduled maintenance. Check again in a minute.
This is not actually an error, since it should happen, but users can interpret it differently. If they reach out to you about this topic but you’re not experiencing an issue on your part, you would like to recommend that you reload the page.
On the other hand, if you are seeing this message while running updates in WordPress, then your site may be stuck in maintenance mode.
49- WordPress is stuck in maintenance mode
Closing your browser in the middle of an update or running cumulative extension updates may cause your site to be suspended in maintenance mode. In this case, you will see the same
The machine that users see on the front end when running updates.
Fortunately, fixing this problem is very simple. All you have to do is access your site files via FTP and delete the file named (. Maintenance).
After that, you can verify your site and everything should be fine again.
50- Changes are not visible on your live site
If you have made a great effort to make an update on your site, then check the main interface only to see that these updates are not visible, you are sure to feel frustrated. The good news is that the solution to this problem is usually very simple.
Often the problem is in the buffering. First, you can try to clear your browser cache. If the changes are still not visible and you are using an add-on for caching, check its documentation to see how to delete the extension’s cache as well.
51- Failure or loss of posting scheduling
Consistent post scheduling is part of a strong content strategy. WordPress helps with this by giving you the ability to schedule posts to publish on specific dates and times.
Unfortunately, it does not always work as intended, which leads to scheduling errors. In general, the fastest solutions to this problem are either by plugins, such as Scheduled Post Trigger or WPScheduled Posts Pro, or by editing cron functions.
52- Auto update failed
In order to help your site stay on the latest version of WordPress, you may have enabled automatic updating. This can be useful for simplifying this aspect of website maintenance and keeping your site safe, but it can also sometimes lead to problems.
Sometimes the automatic update may fail, in which case your site may stop and become unavailable to users. Performing a manual update instead is the recommended repair method.
53- WordPress import issues
For many reasons, you may find that you need to import the content into your WordPress site. This is a fairly common practice among developers, and different utility programs are often used for the task.
Unfortunately, it is easy for import operations to cause PHP or HTTP to stop. To avoid these problems, you can:
Switch to a faster internet connection.
Recover your files using the WP-CLI command bar interface.
Increase PHP downtime limit.
You may also need to contact your hosting provider for help resolving this issue.
54- WordPress performance issues
Your site’s performance is somewhat proportional to its speed. Fast loading pages give the user a better experience and improve SEO, so it is necessary to monitor and improve the speed of your site routinely.
Pingdom is a useful tool for testing load times from multiple sites.
After scanning your site, Pingdom will give you a list of suggestions for how to improve its performance. Common solutions include compressing images, wiping the cache and activating a CDN.
55- WordPress does not send email
Email marketing is a major strategy for many WordPress sites and it can increase traffic and conversion rates. There are many plugins available that enable you to send email from your WordPress dashboard, and easily integrate email marketing platform into your site’s backend.
Often the reason for not sending your email to your subscribers is your server configuration. It is possible that your host has set limits on the resources that your site can use, preventing e-mail from leaving the server.
If you suspect a server issue, contact your hosting company. You may need to upgrade your plan. It is also possible that the plugin is causing the problem. Check out their support forums and documentation for their common issues or contact a developer for support.
Finally, email sent from WordPress may be spam. If a user contacts you about a lost email, ask them to check the trash files just in case.
56- WordPress code building or programming errors
Code building errors indicate problems with the code itself or the structure of your code. This might include incorrectly used punctuation or other misspellings. In some cases, a bug in the code building can block you from accessing the dashboard and disable your site.
Regardless of the seemingly insignificant root cause, this type of error is very dangerous. This often happens when you paste in code snippets that you stumble upon on the Internet. If you did something similar recently, it is most likely the cause of your problem.
To solve it, go to the site of the code snippet that you pasted with FTP, and correct or remove it.
57- The WordPress sidebar appears below the page content
Sidebars can be useful for displaying key content to users, such as a navigation menu, WordPress search functionality, social media icons and even legal files. If your sidebar looks weird because it appears below the content rather than next to it, you have a problem.
It is often the result of incorrect use of <div> tags in one or more of your template files. Track the source of the problem in order to correct the code. This could also happen due to your site display issues or other issues with your WordPress theme.
58- White text and missing buttons in the visual editor
Your WordPress editor is very important. Adding new content to your site would be much more difficult without it. If you’ve ever opened the Classic Editor to find that all of the buttons are missing from the toolbar and that the text color is set to white, then you might have been upset about the inaccessibility of this function.
Often this error is due to a plugin conflict or a buffering problem. If clearing the browser cache or disabling the plugins did not resolve the issue, you may need to replace some of the core WordPress files.
59- Problems with the RSS Feed
RSS Feed is an easy way to support your site by organizing. They are especially useful in news sites and other content forums. However, RSS errors can appear unprofessional and prevent users from being able to view the content.
These errors may appear due to extra spaces or trailing line breaks with PHP closing tags in the function.php file or plugins. You can track them and remove them to eliminate this problem. You may also need to check plugin and theme compatibility, or you can simply disable WordPress’s default RSS functionality.
60- WordPress failed to open Stream
If you see an error message that says “WordPress Failed to Open Stream,” then this means that WordPress was unable to open a file referenced somewhere in your code.
This error can be caused by a combination of problems, but the message usually tells you where the problem is coming from. Possible responses include:
There is no such file or directory.
The request for permission is denied.
The procedure needed to correct the problem depends on the answer you see. It is possible that there is a missing file, or the permissions are set incorrectly, or that WordPress is having trouble communicating with an external API.
61- Password reset error
If users can register to accounts on your site, they may sometimes need to reset their password. In some cases, the default password reset email provides a link that directs users back to the login page, where they will see a message stating: “This key is invalid or has been used. Please try to reset your password again. ”
Usually, this is a buffering issue. If you have a caching extension installed, make sure to disable caching for the My Account page in the extension’s settings. In this case, inconsistencies with CAPCHA plugins are also reported.
62- Continuous updating of the login page
If pressing the Log In button on your WordPress login page simply refreshes it instead of arriving at your dashboard, then something goes wrong:
This error could be the result of a plugin conflict, wrong WordPress addresses, or a corrupted .htaccess file.
63- WordPress logs you out frequently
Unlike the login page refresh error, this issue allows you to access your WordPress dashboard for a while but all of a sudden it logs out again. Most of the time this error is caused by a problem with your WordPress settings.
If you are facing this issue, it may be due to a mismatch between your WordPress title and your WordPress site address in the global settings.
This can include minor differences, such as whether or not the URLs have www at the beginning. Changing the URLs to match should solve this problem.
If you can’t do this via your dashboard because WordPress keeps logging you out, you can get the job done by modifying the wp-config.php file.
64- “Are you sure you want to do this?”
The most frustrating WordPress errors are the ones that give no indication of what might be causing them. The error “Are you sure you want to do this?” It is one of these errors.
Often times this error occurs because an extension conflicts with other plugins or a template, and it can be resolved by using a standard troubleshooter to fix this problem. If this does not work, you may need to replace your wp-config.php file.
65- “Another update in progress”
Typically, the error “Another update is currently working” appears if you are trying to start updating a plugin or theme while WordPress is still performing a basic update.
This often occurs during basic, automatic security updates. The message should automatically disappear once the first update is finished. If it doesn’t go away, something is wrong. You can fix this issue from phpMyAdmin by deleting the core_updater.lock row from the wp_options table.
66- Moving to trash can error
WordPress lets you delete your posts and pages from your site easily with one click of a button. However, several problems can lead to an error when trying to move the content to the Recycle Bin.
This could be caused by a buffering issue or an add-on conflict. It could also be due to database corruption or incorrect file statements.
67- WordPress installation errors
Although WordPress is known for its simple 5-minute install process, you can still run into problems. Potential issues include a database connection error and a 500 internal server error, which we talked about earlier in this post.
You may also encounter the “Headers Already Sent” message. This is likely due to unnecessary PHP spaces or tags in your code. The message should include the location of the problem and can be resolved by modifying the associated file.
68- The site is experiencing technical difficulties.
This error has become more common since the release of WordPress 5.2. It usually appears during major updates, plugins, or themes.
The error “Site is experiencing technical difficulties” is usually caused by either an error in the PHP memory limit or a conflict with plugins. Your site’s memory can be increased in a number of ways.
To troubleshoot extension conflicts, try disabling all extensions and then reactivating them one
After another to find out which of them is the cause of the error appearing again.
69- Your WordPress site is down or unavailable
Site unavailability may result in lost traffic and revenue. If you are sure that your WordPress site is down, you must first determine whether the cause of the problem is a WordPress bug or your server is experiencing a problem. Symptoms of other WordPress errors might suggest the underlying problem.
If none of these exist, you can try to check the server error logs.
If your server cannot function properly or you have no idea what is happening, you should contact your hosting provider for assistance.
The last thing any WordPress site owner would want is for their site to become unavailable to users or to have problems. This doesn’t only lead to you losing sales, views, search engine results, earnings, or even commissions that you may have earned. At the same time, your site will appear untrustworthy and poorly trusted, and this will damage your brand’s reputation, which can be difficult to fix.
That’s why we’ve collected the most common WordPress errors on one page to help you find the simplest possible solution and get your business back on the right track.
You have questions about WordPress troubleshooting for your site? Ask your questions in the comments section below!