WordPress is a fantastic tool for those with no technical experience who want to create and manage a simple website.
While WordPress offers many impressive features, it also has several significant flaws. You may encounter many issues as you continue using it.
This is what pushed us to create this ambitious article that hopes to cover all WordPress errors and how to troubleshoot them.
Let’s get started.
How to fix briefly unavailable for scheduled maintenance How to fix memory exhausted error in WordPress How to fix the upload_max_filesize error in WordPress How to fix the DNS_PROBE_FINISHED_NXDOMAIN error How to fix common cache issues in WordPress How to fix the 500 internal server error in WordPress How to fix the 502 bad gateway error How to fix the 401 unauthorized error in WordPress How to fix the 403 forbidden error in WordPress How to fix the 404 error on WordPress posts and pages How to solve the 405 error in WordPress How to fix 413 requests entity too large error in WordPress How to solve the 429 too many requests error How to fix “There has been a critical error on your website” in WordPress How to fix the “Your connection is not private” error How to fix the ERR_CONNECTION_TIMED_OUT error How to fix the “Error establishing a database connection” issue How to fix the “Sorry, you are not allowed to access this page” error How to fix the cURL error 28 in WordPress How to solve the white screen of death in WordPress How to fix the missed schedule post error in WordPress How to fix the “Fatal error: Maximum execution time of 30 seconds exceeded” How to fix the updating failed or publishing failed error in WordPress How to fix the “Upload: Failed to write to disk” WordPress error (file and folder permissions error) How to fix the ERR_TOO_MANY_REDIRECTS error in WordPress How to fix the “WordPress could not establish a secure connection” error How to fix the Elementor white screen of death when editing a post or page How to fix the “Sorry, this file type is not permitted for security reasons” error How to fix the mixed content error in WordPress How to fix the “Parse error: syntax error” in WordPress How to fix the “Warning: Cannot modify header information” in WordPress How to solve the “ECONNREFUSED — Connection refused by server” error How to fix the “Missing a temporary folder” error in WordPress 1. How to fix briefly unavailable for scheduled maintenance When you use the built-in WordPress update system in your dashboard to update core software, plugins, or themes, WordPress puts your site into “maintenance mode” so the appropriate files may be securely updated.
Anyone trying to access your WordPress site while it’s in maintenance mode will receive the message “Briefly unavailable for scheduled maintenance.”
So the notice isn't a mistake — it's expected to be there only for a little time.
Here are ways to fix this:
Method 1: Using the cPanel File Manager If you can use the cPanel (which largely depends on your web host provider), you can solve this easily.
Just hop on the cPanel and click on the “File Manager ” app.
By default, the file manager app doesn't show hidden files. So you need to enable it first by going to “Settings ” and checking the “Show Hidden Files ” option.
After that, navigate to the “public_html ” folder.
Then, all you have to do is find the .maintenance file, right-click on it, and remove it.
Take note that before you delete the .maintenance file, you should wait out for a bit until the update finishes.
If you don't have access to a cPanel, then try this next method.
Method 2: Using FTP By using a file transfer protocol application like Filezilla
For example, there is an option under the “Server ” menu to “Force showing hidden files ”.
On other applications, this is usually available in the “View” menu. (If you can't locate this option, look through your application's documentation.)
Once turned on, the “.maintenance ” file should appear in the list. Remove it to put an end to this issue.
Normally, that should solve the issue.
Method 3: Using the Terminal If you use an SSH connection to view your server's files, you can view hidden files by typing this command:
ls -a With the terminal, you don't need to list a directory to delete files.
All you have to do is navigate to your WordPress root folder and enter the following command:
rm .maintenance 2. How to fix memory exhausted error in WordPress Memory exhausted issues are frequently caused by a plugin, theme, or other script exceeding the default allocated memory size limit on your WordPress installation.
The solution here is simple — you just need to increase your PHP memory limit.
There are two ways to do this, one is to increase the memory limit right in the WordPress platform via the wp-config.php file. The other is for the server limit via the cPanel.
Method 1: Increase your PHP memory limit To do so, go to your WordPress site's wp-config.php file and make the necessary changes.
It's in the base folder of your WordPress site, and you will need to use an FTP program or your web hosting control panel's file manager to access it.
Next, you need to paste the code below in the wp-config.php file:
Define ( 'WP_MEMORY_LIMIT', '256M' ); It could be anywhere as long as it’s before the line that says “That's all, stop editing! Happy publishing.”
What the code above does is tell WordPress that the PHP memory limit should be increased to 256 MB.
When you're finished, save the changes and re-upload your wp-config.php file to your server. You should now be able to access your WordPress site without the memory exhausted error.
By the way, if this doesn’t work for you, it’s possible that your hosting provider doesn’t allow users to increase the PHP memory limit.
If that’s the case, you need to contact support to manually increase the PHP memory limit of your website.
Method 2: Via the cPanel This method is even easier and will directly increase the server memory limit.
To do this, navigate to your web host’s cPanel and find and click on the “Select PHP Version ” option under the “Software” category.
On the next page, go to the “Options ” tab.
Once there, find the “memory_limit ” option and select your preferred limit from the dropdown options.
After you click on an option, the cPanel will automatically save your selection.
With both methods, the issue should now disappear.
3. How to fix the upload_max_filesize error in WordPress Most hosting companies limit the amount of PHP RAM that may be used to execute applications and scripts.
That causes the uploaded file to exceed the upload max file size limit in PHP.
When you upload a file that exceeds the limits defined by your web server, you will get a php.ini error on your WordPress site.
As you may expect, the solution entails increasing the default upload max file size limit.
Here are some methods to fix this problem:
Method 1. Edit the .htaccess file The quickest fix is to increase your PHP resource limits by tweaking the .htaccess file.
Using an FTP application or the cPanel's file manager (see error #1 method #1), locate the .htaccess file in the root folder and edit it out.
Then, add the following code near the top of the file before the line that says “# BEGIN WordPress”:
php_value upload_max_filesize 256M Save the changes and if the error persists, try adding these lines into the .htaccess file:
php_value post_max_size 256M
php_value memory_limit 512M
php_value max_input_time 180
php_value max_execution_time 180
It should look something like this:
As long as your web hosting company supports adjusting the PHP limits, you may change to any value you like.
You may also find the maximum allowed limitations by looking at your website's PHP information.
Method 2. Edit the wp-config.php file Another way to fix this issue is by tweaking the wp-config.php file in your root directory.
Paste the following code anywhere before “That's all, stop editing! Happy publishing.”
@ini_set('upload_max_size' , '256M' ); Like this:
Save the changes and refresh your web browser. Then, try to upload the file again and see whether or not the issue would still appear.
Method 3: Via the cPanel There’s a hidden gem inside the cPanel where you can change the maximum upload file size (even up to 1 GB).
Within the cPanel, find the “Select PHP Version ” app (under the “Software” category).
On the next page, go to the “Options ” tab.
The last setting on the page should be “upload_max_filesize ”. Click the dropdown and select the maximum file size you want to set.
Note that selecting the maximum upload filesize doesn’t mean you will be able to quickly upload large files.
4. How to fix the DNS_PROBE_FINISHED_NXDOMAIN error The cause of DNS_PROBE_FINISHED_NXDOMAIN error is usually due to a DNS misconfiguration or issue.
The domain name system connects domain names to actual web servers to guide internet traffic.
This basically turns the worded website address – such as darrelwilson.com – into a computer-friendly server IP address like 516.4.132.8.
Looking at the process:
When a user types a URL into their browser, DNS connects that URL to the IP address of the real server. This is known as DNS name resolution, and it entails the system asking several nameservers to determine a server's real IP address. If DNS fails to repair the domain name or address, then you will get the DNS_PROBE_FINISHED_NXDOMAIN error.
Here are two easy methods to fix this:
Method 1: Release and renew the IP address Because this is frequently a client-side DNS issue, the first thing you should do is attempt to release and renew your computer's IP address.
This includes cleaning your local DNS cache, which is comparable to the cache in your browser.
For Windows users:
Open up the command prompt application by pressing the Windows logo key + R . Then type “cmd ” and hit the enter key on your keyboard. Once the command prompt is open, enter the following code and hit the enter key:
ipconfig /release That command will release your current IP address.
After that, enter another command and hit the enter key:
ipconfig /flushdns That will flush your local DNS cache. After doing this, you should see a “Successfully flushed the DNS resolver Cache” message on the command prompt.
Lastly, type the following command hit the enter key to renew your IP address:
ipconfig /renew You should also think about resetting your IP settings and Winsock catalog. Just enter the following commands on the prompt:
netsh int ip set DNS
netsh winsock reset
Another way to flush and renew your DNS is simply by disabling your network adapter and re-enabling it.
Method 2: Reset Chrome flags Obviously, this only works if you’re the Chrome browser (or any of the Chromium browsers).
At times, Chrome settings or experimental features can be changed or altered accidentally.
You can reset these back to default by inserting chrome://flags into the URL bar of your browser.
Once there, click on the “Reset all ” button and restart your browser.
There are other “mini-fixes” available as well, but both methods should solve the issue unless there’s a deeper issue inside.
5. How to fix common cache issues in WordPress There are numerous cache plugins for WordPress right now that are free, and they may help you improve speed in various areas of your website.
Caching on your website is one of the most efficient ways to speed up the loading of your pages and provide material to your users.
People are likely to run across cache troubles as these caching techniques get more complicated.
Method 1: Clearing your plugin cache Some of the most typical caching issues users might have when using a cache plugin include the following:
Being unable to view the recent post or page modifications Being unable to view changes made using the customizer The majority of cache problems are resolved by simply emptying the cache.
This is normally done using the cache plugin's settings page, which you can find on your WordPress website.
For example, in the WP Super Cache plugin
You will see a “Delete Cache ” button to press.
More or less, you will find a similar button to press on various cache plugins.
Method 2: Enable caching in wp-config.php You can enable or disable the native WordPress object cache inside the wp-config.php file, so navigate to it first with an FTP application or on the cPanel's file manager (see error #1 method #1).
Then, paste the following code anywhere before “That's all, stop editing! Happy publishing.”
define('WP_CACHE', true); Like this:
Once you’re done, make sure to re-upload the file to your website server.
Note that this caching method is also referenced within the WordPress Codex
6. How to fix the 500 internal server error in WordPress The 500 internal server error website is enough to throw anyone into a panic.
When your website goes down, you lose out on potential traffic and sales. It can also negatively impact your search engine optimization (SEO) efforts if it's offline for a while.
Fortunately, fixing this error is quite simple even without technical know-how.
Method 1: Create a new .htaccess file This time, you would definitely need a file transfer protocol application like FileZilla
Right after you start accessing your website server, you will be facing the root directory, which is typically called public_html .
If you don’t see your .htaccess file, make sure that hidden files are viewable by enabling the “Force showing hidden files ” feature under the “Server” menu.
When you see the .htaccess file on the root folder, right-click on it and change its name to “.htaccess.bak ”.
Renaming the .htaccess file and adding a new extension to it basically deletes it from your site.
To create a new one, go to your WordPress admin area.
Hover over “Settings ” and select “Permalinks ”. Scroll down to the bottom of the page and click on the “Save Changes ” button.
This should automatically create a new .htaccess file on your website server.
Method 2: Increase your PHP memory limit WordPress will attempt to increase your limit if you begin exceeding it, but it can only go as high as the limit your host has placed on your server.
This limit is often lower for shared hosting plans, though this should hardly be a surprise seeing shared plans are the cheapest type of web hosting plans .
The bottom line is, you need to increase your PHP memory limit in WordPress and refresh your site to test whether or not this is causing the 500 internal server error.
We discussed this in the second section of this article, but the gist of it is this:
Open your website’s wp-config.php . Edit it out and add the code that would tell WordPress to increase your website’s memory limit. Save the changes made on the file. Refresh your website and see whether or not this solves the 500 internal server error.
7. How to fix the 502 bad gateway error The 502 bad gateway error is a more common issue — which happens when there’s an invalid response from the website server.
It actually happens all the time on the internet — not only on WordPress sites — but also on prominent services like Gmail, Twitter, and Cloudflare.
Here are two methods that could help:
Method 1: Try to reload the page first Before you try any fixes when you’re facing the 502 bad gateway error, one thing you should try is to give it a minute or two and refresh the page .
The rationale for this simple method is that the server or host might be overloading, which could happen if you’re trying to change multiple things at once on your website.
If this is the case, then the website should come back in a few minutes.
While you’re at it, you could also use a different browser and check out the page to confirm it’s not a browser-specific issue.
You can also hit up downforeveryoneorjustme.com
Method 2: Flush the DNS Resolver Cache The other possible reason is that there might be a DNS issue in your domain and it is what’s causing the 502 error.
For example, it’s possible that the DNS server is not responding properly.
In addition, if you recently migrated your WordPress site to another web host, the domain and website might not have fully propagated yet, which could take hours to happen.
Note that the speed of migration could depend on the time-to-live (TTL) value found on your DNS records.
Because of this, one of the fixes you can try is flushing your DNS resolve cache.
In Windows, open up the command prompt application and enter the following code:
ipconfig /flushdns The command prompt application should show a “Successfully flushed the DNS resolver Cache” message after you hit the enter key.
If this didn’t work and you have a feeling that this is more of a DNS issue, see error #4 of this article.
8. How to fix the 401 unauthorized error in WordPress Out of all the possible issues you could face, the 401 error is one of those errors that might temporarily give you a heart attack.
After all, how could you get an “unauthorized error” if you’re the owner, right? It’s hard to imagine you could get locked out of your WordPress website.
To solve this, you may have to temporarily remove the password protection feature on your WordPress admin. Unfortunately, this is only possible if you can access the cPanel of your site.
Solution: Remove the password protection feature temporarily If you can, log in to your cPanel and look for the “Files ” category. In it, you should see “Directory Privacy ”. Now, click on it.
Once you open it, you will see all the files and folders on your hosting account. Browse to your wp-admin directory and find the “public_html ” folder.
There should be an “Edit ” button or action that you can click for that folder.
The control panel should now display the password protection settings.
Simply uncheck the box next to the “Password protect this directory ” option and click on the “Save ” button.
With this, you have successfully disabled the password protection for your WordPress admin directory.
Unfortunately, this makes your website vulnerable to hacking attacks. So make sure to put up the password protection right away after you reset it.
This works with most web hosting plans, except for managed web hosting. If you don’t have access to the control panel, contact your hosting provider and ask them to do this manually.
9. How to fix the 403 forbidden error in WordPress You could face the 403 forbidden error in WordPress while trying to log in to the admin dashboard, visiting a certain page, or rarely, while installing/updating WordPress.
This error could be due to multiple things. But usually, it’s because of incorrect file permissions or faulty/corrupt files.
Fortunately, you should be able to fix the 403 error on your own.
Here’s how:
Method 1: Scan for faulty plugins There are plenty of high-quality WordPress plugins
The best way to tackle this issue is through trial and error. That means deactivating all of your plugins and re-activating them one by one until you find the culprit.
To get started, hover over the “Plugins ” link on your dashboard and go to the “Installed Plugins ” page.
Then, click the top checkbox to select all plugins, choose “Deactivate ” from the dropdown menu, and click on the “Apply ” button.
Once all the plugins are deactivated, you should be able to access the page if a plugin was causing the issue.
Afterwards, you can re-activate the plugins individually and refresh the page that’s showing the error after re-activating a plugin. Adding the faulty plugin back should cause the error to reoccur.
Method 2: Reset the .htaccess file due to possible corruption If your hosting provider uses an Apache web server, your .htaccess file might be causing the 403 forbidden error.
The .htaccess file controls basic configuration settings for your WordPress site, and a small change or mistake can damage it.
To fix this, you will need to reset your .htaccess file. Before you proceed, I recommend making a backup of your site first.
Once you’re ready, open your file transfer protocol client of choice and locate your .htaccess file. If you can’t find it, then you need to enable the feature of the FTP client to see hidden files.
Note that you can also use your cPanel's file manager (see error #1 method #1) if your web host provider supports it.
The next step is simple — delete the .htaccess file.
Next, go to your WordPress dashboard. Go to the “Settings ” menu and navigate to the “Permalinks ” page.
You don’t have to make any changes here. All you have to do is scroll down and click on the “Save Changes ” button.
This will automatically generate a new .htaccess file for your site.
10. How to fix the 404 error on WordPress posts and pages When you talk about WordPress issues, it’s impossible not to include the classic 404 error, which is one of the most talked-about errors in the web development world.
Many people know this error by the name of “Page not found”. Basically, the browser is telling you that it can’t find the post or page that you’re trying to go to.
Now, before you try a fix that we recommend, you should first check whether or not you entered the correct link. This error could have easily been caused by a typo.
Solution: Reset the permalink structure If not, you could try to reset the permalink structure of your website, which follows similar steps to method 2 of the previous error.
That is, go to the permalinks option in your WordPress admin. Hover your mouse over the “Settings ” link and click on the “Permalinks ” option.
While here, remember the permalink structure your website is using at the moment.
That’s because you will need to change the structure temporarily to reset the permalink settings and change it back again in a moment.
Select the “Plain ” option and click on the “Save Changes ” button at the bottom of the page.
The page will reload after you hit the button.
Then, you can go ahead and choose your previous permalinks structure and save your changes once more. This will reset your WordPress permalink structure and hopefully solve the issue.
But in case it didn’t, the other angle you can look at here is possible DNS issues. For that, check on error #4 of this article.
11. How to solve the 405 error in WordPress The 405 error (usually with a “Not Allowed” message) is a little different than the 404 error:
The 404 error tells you that the browser couldn’t find the page you want to access. On the other hand, the 405 error means the browser did find the page, but there was something wrong with the HTTP method used. Basically, it tells you that the server acknowledges the request method but it may not be supported by the target resource.
Two simple solutions you can try are the following:
Method 1: Check the link The first thing you should do here is to check if you entered the correct link.
Like with the previous error, entering the wrong link is the most common cause that 405 error occurs.
The reason is simple — for security purposes, the servers do not allow anyone to access wrong or “improper” links so users don’t end up on the wrong pages or pages that are non-existent.
That’s why before you panic, make sure that you enter the correct URL of the page you want to visit.
Method 2: Deactivate plugins and themes If the first method didn’t work, then there’s a chance that the problem lies with new plugins and themes.
As you may know already, plugins play a vital role in your site as they add new features and functionalities that are not available out-of-the-box.
At the same time, the theme you’re using allows you to not need any coding knowledge at all. Without it, you may have to hire an expensive developer to create a good-looking site.
Unfortunately, the plugins and themes you have might be the ones creating the problem. Both features add extra functionalities that change the way your website looks and operates.
This is why deactivating and uninstalling plugins and themes might be able to help.
To start, click on the “Plugins ” link on your WordPress dashboard and go to the “Installed Plugins ” page from there.
You will see all the plugins you have installed on this page.
Then, start deactivating each plugin one at a time. Below each plugin name, you will see a “Deactivate ” button you can click.
After deactivating each plugin, check the page again and see whether or not the error still persists.
This could take some time if you have lots of plugins. On the other hand, this will tell you exactly which plugin is causing the error.
After doing this with the plugins and you found nothing, try to deactivate your active theme.
Hover over the “Appearance ” menu and navigate to the “Themes ” page.
Technically, you can’t have a website that has no active theme. So to do this, simply activate another theme on your website.
Try and refresh the page you’re trying to access to see if this method solved the issue.
12. How to fix 413 requests entity too large error in WordPress The 413 error occurs only when you try to upload a file that’s bigger than the max upload limit of your website.
Basically, the server will not be able to upload the file as it violates the limit, which then triggers the 413 error.
In some ways, this is similar to error #2 of this article, so you would see similar methods (though not exactly the same).
Method 1: Increase upload file size limit via the functions file The first solution you can try is adding a set of codes to the functions.php file of your theme.
Generally, you should find it under the theme folder of your currently active theme under the wp-content folder.
Note that you can also use the cPanel's file manager (see error #1 method #1) if your web host provider supports it.
Then, at the bottom, paste the following codes:
@ini_set( 'upload_max_size' , '64M' );
@ini_set( 'post_max_size', '64M');
@ini_set( 'max_execution_time', '300' );
Note that it’s possible to increase the upload_max_size and post_max_size values and make them bigger than the size of the file you want to upload.
At the same time, you must tweak the max_execution_time according to how long it might take for the server to upload the file.
Don’t forget to re-upload the file to the server or save the changes if you’re editing it from your website’s code editor.
Method 2: Increase upload file size limit via the .htaccess file If the method earlier didn’t work, you can add another set of codes to the .htaccess file.
Make sure to add the following code near the top of the file before the line that says “# BEGIN WordPress”:
php_value upload_max_filesize 64M
php_value post_max_size 64M
php_value max_execution_time 300
php_value max_input_time 300
It looks like this:
Now, this should work but only if your web hosting company allows you to change the PHP limits.
13. How to solve the 429 too many requests error The 429 error is one of those errors that may drive you nuts — simply because it doesn’t give you too many details as to why the error occurred.
But typically, the 429 error happens when someone is trying to navigate to a specific page many times in a short period.
On the back-end, it triggers the server’s rate-liming security feature, useful in instances when a hacker tries to visit your WordPress admin login page and repeatedly tries to break in.
So what can you do? You’re not the one that’s causing it so the best thing to do is change the default login URL of your WordPress admin.
Solution: Change or hide your default WordPress URL The most likely cause of the 429 error you’re facing is a brute-force attack by someone who’s attempting to log in to your website admin.
To solve this, you need to change the default URL of the login page. When they refresh, they will instead get a 404 error or another message, depending on the plugin you use.
If you didn’t know yet, the default login page of your website usually ends with /wp-admin. Easy to remember, right? Unfortunately, this is the same for every website out there…
Until you change it, that is — and the easiest way to do that is to use a plugin called WPS Hide Login
You can either download it from the WordPress plugins directory or find it from the “Plugins ” page of your website and install it from there.
Once you activate the WPS Hide Login plugin, configure it by clicking on the “Settings ” link from your admin dashboard and then to “WPS Hide Login ”.
Enter the URL extension you want to use for your website’s login page on the “Login url ” field. Then, you can redirect the user to a certain page — like the 404 error page.
Make sure to remember your website’s new login page. You won’t be able to log in yourself if you won’t be able to locate it.
After that, the error should go away on its own as the attacker realizes he or she can no longer find the login page.
14. How to fix “There has been a critical error on your website” in WordPress It’s alarming especially for new users to encounter the “There has been a critical error on your website” issue.
That’s because visitors may not be able to visit the site and in some cases, you may not even be able to get to the admin dashboard yourself.
This error happens where there’s a PHP error on the site and the script stopped running — causing what process it was running to stop.
Unfortunately, there is no standard fix for this since you need to understand what happened first.
Method 1: Check the error logs Fortunately, there are error logs you can check right in your website server. Although you can use your hosts file directory, you can also use any file transfer protocol application you have or the cPanel's file manager (see error #1 method #1).
Whatever you use, you will find an error_log file right in the wp-admin directory of your website.
On this file, you should find four kinds of errors:
On each log, you will see the kind of error that happened. The only errors you should take note of are those that have a parse or data label, which you need to fix.
Now, if you can’t locate the error_log file, you would need to contact your web hosting provider and ask for the log.
In case you really can’t get hold of the error_log file, try the method below:
Method 2: Debug WordPress In case you didn’t know, there is actually a debugging system built right inside WordPress itself. It could help you identify errors triggered by plugins, themes, and the core software itself.
However, you may need to activate it first.
Using the cPanel's file manager (see error #1 method #1) or a file transfer protocol client, access the wp-config.php file from your root directory.
Then, scroll through the file and find the codes below:
define ( ‘WP_DEBUG’, false );
define ( ‘WP_DEBUG_DISPLAY’, false );
define ( ‘WP_DEBUG_LOG’, false );
define ( SCRIPT_DEBUG’, false );
Note that the “false” value means the feature is deactivated. Change the “false” into “true ” on all four lines to activate the feature.
Basically, here’s what each line of code does:
The WP_DEBUG will activate the debug mode. The WP_DEBUG_DISPLAY will display the debug messages. The WP_DEBUG_LOG will save the error details in a file called debug.log. The SCRIPT_DEBUG will run the dev versions of the JavaScript and core CSS files of your website. Note that if you can’t find these lines on the wp-config.php file, you can also copy the codes here to the file and change all the “false” values to “true”.
Once the debug mode is enabled, reload your website. Now, every time you get an error, you should see the details above the error message.
Naturally, you should learn more about the error that’s causing the “There has been a critical error on your website” issue.
Once you fix the underlying issue, the error should go away on its own. Feel free to deactivate the debug mode once the issue has been resolved.
15. How to fix the “Your connection is not private” error The “Your connection is not private” error is a common issue that users face.
Now, this could be a security issue on the website’s side, which could be triggered if the website doesn’t have a valid SSL certificate, which validates the website’s authenticity and security.
If everything is working fine on the website and you’re sure that the website has a valid, unexpired SSL certificate, then the issue may be coming from your end.
Fortunately, this issue isn’t that hard to fix.
Method 1: Clear your browsing data first The first thing you should do when facing this error is to delete the stored data first from your own browser. This will temporarily delete files like cookies, cache, and images.
Now, different browsers may have different names, but the steps are generally the same.
For example, if you’re using the Google Chrome browser or any Chromium browsers, you should find the “History ” page first (shortcut is “ctrl” + “h”).
You will then see a “Clear Browsing Data ” option on the left side that you can click.
Make sure to check the boxes under the “Basic ” tab and select the “All time ” option on the “Time range ” dropdown.
Click on the “Clear data ” button to continue deleting your browsing data.
If this didn’t work, try this one out:
Method 2: Check your antivirus or internet security suite There are a lot of cases when an antivirus software or security application blocks SSL connections, which would have triggered the error.
All antivirus or security software should have an option to disable the SSL scanning feature or even the security feature itself.
For example, in the Microsoft Defender application, there’s a “Virus & threat protection settings ” page where you can disable security features.
There’s also a “Firewall & network protection ” page that might do the trick.
If you really can’t find where you can disable the feature, then feel free to disable or temporarily delete/uninstall the antivirus software and visit the website again.
If the error doesn’t appear anymore, then it’s likely your security program is causing the problem.
16. How to fix the ERR_CONNECTION_TIMED_OUT error There are two primary reasons why the “ERR_CONNECTION_TIMED_OUT” error occurs:
Your local network connection is experiencing some sort of problem. Your website server is overloading, which usually happens when you reach your memory limit. Before you do anything, make sure that your local connection is working fine. If you suspect you’re having connection problems, restart your router first.
Sometimes, you may have to disable the security program on your computer, which may be causing some connection problems (see the previous error of this article).
Once those are out of the way and the error still persists, try out this method first:
Method 1: Disable your proxy server settings If you’re using a VPN or a proxy server, it may be the one that’s causing the problem.
That’s because a proxy server acts like a bridge or a middleman between your website and the device, usually for the purpose of making yourself anonymous.
Because of that, the proxy server may be blocking the connection unintentionally.
To solve this, disable any VPN software you’re using and reset the proxy settings on your computer.
If you’re on Windows, find “Internet Options ” in your control panel under the “Network and Sharing Center ” settings.
Once you click on it, you will then see a new window that shows you the internet properties. Go to the “Connections ” tab and click on “Local Area Network (LAN) Settings ”.
Then, uncheck all the proxy settings here and refresh the website.
If the error disappears and you really need to use a proxy server, then you may need to reconfigure the settings or find another provider.
You can also use another DNS server to see if it works — as the one Google offers for free
Method 2: Check the local hosts file in your computer If the method above worked, you may need to check the local hosts file on your computer. In this file, you will find the DNS entries related to specific IP addresses.
Basically, your goal is to check that the website you’re trying to visit isn’t listed on this file.
If you’re using Windows, you will have to open the notepad application as an administrator. Simply search for the application, right-click on it, and click on the “Run as administrator ” option.
Once the notepad is open, go to the “File ” tab and navigate to the location below and open it up:
C:\Windows\System32\drivers\etc\ If you see your website on the list, delete it from the file and save it.
Most likely, this should solve the problem. If it happens again after some time, simply repeat the process you did.
17. How to fix the “Error establishing a database connection” issue The “Error establishing a database connection” issue is one of the fatal ones you could ever face. When this happens, visitors wouldn’t be able to access your website.
From the name itself, this error occurs when there’s a problem with the database connection and your website isn’t able to access it anymore.
Since the database contains information about your pages and posts, your website will not work.
To fix this, try these methods:
Method 1: Check your database credentials The most likely culprit for this error is wrong database credentials, which could happen after migrating to a new web host.
Fortunately, this is easy to check as long as you can access your website files using a file transfer protocol client or the cPanel's file manager (see error #1 method #1) .
First, find the wp-config.php file on the root directory of your website and open it up.
Scan through the file and look for these lines:
// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define( 'DB_NAME', 'name of database' );
/** MySQL database username */
define( 'DB_USER', 'username' );
/** MySQL database password */
define( 'DB_PASSWORD', 'password' );
/** MySQL hostname */
define( 'DB_HOST', 'localhost' );
Like this:
Ensure that you have the correct database name and host information. Then, check the username and password of your database credentials and make sure they’re accurate.
If you see a typo, or anything different, make sure to correct it first and save the changes.
After that, refresh the website and see if the database connection error is now gone.
Method 2: Repair your WordPress database If the problem persists, then it’s possible that your database has been corrupted. Fortunately, it’s quite easy to fix this, as long as the data is intact.
With a file transfer protocol client or your host’s file directory, open the wp-config.php file (discussed in the previous method) and add the code below:
define('WP_ALLOW_REPAIR', true); Make sure to reupload the file back to your server or save the changes if you’re using a code editor inside your hosting provider.
To proceed, visit the page below:
http://www.yourwebsitedomain.com/wp-admin/maint/repair.php You should then see some options to repair your database.
For starters, click on the “Repair Database ” button and wait for a while until WordPress finishes repairing your database.
Now that your website’s database is fixed, you shouldn’t see the error anymore.
18. How to fix the “Sorry, you are not allowed to access this page” error It’s scary when you’re the owner or admin of the website and suddenly, while trying to log in to the admin dashboard, you would see “Sorry, you are not allowed to access this page”.
This error is quite easy to under — it literally means your permission settings prohibit you from accessing a certain page.
For this reason, the first thing you should do is check your permission settings:
Method 1: Check that you have the correct permission If you could still log in to the WordPress dashboard and you notice some features are missing, it’s likely that your role was changed.
While on the dashboard, navigate to the “Users ” link and go to the “All Users ” page and check the “Role ” section.
If you can’t see the “Users” page at all, that means you’re not a website administrator anymore, which could be problematic if you’re the only one who manages your site.
Before you panic, visit your web host dashboard and see if there’s a way you can return to a previous backup (this could be problematic if your web host doesn’t automatically create backups).
If that didn’t fix the issue but you can still log in to your site’s control panel, then you may have to manually add a new administrator credential.
Method 2: Create a new admin user First off, go to your site’s cPanel and look for phpMyAdmin, which is under the “Databases ” group.
Now, go to the wp_users table and navigate to the “Insert ” tab.
The next step is to fill in our new admin account information.
After that, click on the “Go ” button and you will immediately see the new user information in the table.
Remember the ID of the new admin account and go to the wp_usermeta table.
Once there, click on the “Insert ” button and use fill the fields with these information:
Unmeta_id : No need to add anything here as the system will automatically fill this out.User_id : Paste or enter the ID from the wp_users table.Meta_key : Enter the value “wp_capabilities”.Meta_value : This should be a:1:{s:13:”administrator”;s:1:”1″;}This gives the new user administrator privileges, which you could use to log in to your WordPress admin dashboard.
Before you go, delete your old account. It’s possible that someone got hold of it or it may have been corrupted.
19. How to fix the cURL error 28 in WordPress Every time the cURL error 28 happens, it’s usually accompanied by a message that tells you what may have happened. The most common ones include “Connection timed out” or “Operation timed out”.
The term cURL stands for “client URL”, and is a software utility that WordPress uses to manage data requests.
Now, when the data requests timeout or there’s a failure in responding back to the server on time, WordPress will display the cURL error 28, and the Site Health report will show you a critical issue.
As for the specifics, there are various reasons why the data requests time out. Sometimes, it could be a security plugin that causes the problem — or it could be an SSL issue.
Here are ways to fix this issue:
Method 1: Disable your WordPress security plugin temporarily It’s possible that there’s a problem with a specific security plugin, or that some data has been corrupted. But this issue could happen with any security plugin.
First, go to the “Installed Plugins ” page of your WordPress admin dashboard. Below the security plugin, you should see a “Deactivate ” link you could click on.
After you disable the plugin, go to the “Site Health ” page of your website and check if the method resolved the issue.
If it did, check the firewall logs of the security plugin and find out which API requests were blocked.
From here, you can then adjust the firewall settings to solve the issue.
Method 2: Configure your SSL settings properly Having a valid SSL certificate is a good practice. But if it’s set up properly, your server might block some data requests.
Similarly, not having an SSL certificate for your website at all would still lead to data requests failure too.
If at the start you had to install the SSL certificate yourself, you may have to do this again and reinstall the certificate.
Otherwise, you should contact your hosting provider and ask them to re-install it for you.
If this method didn’t solve the cURL error, you need to ask for help from your hosting provider since the problem may be due to the hosting environment.
For example, it’s possible that your host’s DNS servers may have a problem resolving requests, which triggers the cURL error 28.
20. How to solve the white screen of death in WordPress People started calling this issue “the white screen of death in WordPress” since that's the only thing you see in most browsers when this error occurs.
On some browsers, however, you may see a message that says “This page isn’t working”.
This frustrates many users since the white screen doesn’t really give you any clues or any warning messages.
However, this error is likely related to memory limits or PHP limits. It’s also possible that it could be related to a plugin or theme.
Before you try any of the methods below, try to deactivate your plugins first or change your theme to see if it solved your problem.
Here are some useful fixes you can try:
Method 1: Clear your browser and plugin cache If you notice that you still have access to the WordPress admin dashboard, even if the front-end is showing you the white screen, then clearing the cache might solve the problem.
First off, clear off your browsing data and see if it works. If you don’t know how, I discussed the steps in error #15.
Then, empty your WordPress cache. If you’ve got a cache plugin installed, there’s always an easy option on its settings that enables you easily clear out the cache.
For example, if you’re using the WP Super Cache plugin, you would see a “Delete Cache ” button on the top admin toolbar as well as on its settings page.
After clearing out the cache, go and check the front-end. If the front-end is back to normal, then it’s a cache problem.
If not, try this other method:
Method 2: Increase the text processing ability of PHP There are instances when the white screen of death happens because the PHP text processing ability had a problem with a long post or page.
Fortunately, this doesn’t mean you shouldn’t post long content anymore — and you really should when there’s an opportunity.
All you have to do is to add a little code on your wp-config.php file using a file transfer protocol client or the cPanel's file manager (see error #1 method #1).
When you’re ready to edit the wp-config.php file, paste the following code anywhere inside:
ini_set('pcre.recursion_limit',20000000);
ini_set('pcre.backtrack_limit',10000000);
It should look like this:
After adding the code, make sure to save the file or upload the file back to the server. Refresh the page you’re trying to visit and it should be fine now.
21. How to fix the missed schedule post error in WordPress If you’re one of those people who plan out their pages and posts to publish and schedule them in advance, then it’s understandable to get frustrated when you encounter the missed schedule post error.
WordPress uses a technology called “Cron” to enable users to publish posts in advance. If the cron jobs conflict with the hosting environment or some plugins, then it could cause the error.
The good news is that the solution may be simpler than you think. Or, if that doesn’t work, you can always find a turnaround to schedule posts in advance.
Method 1: Check your time zone settings First things first — the issue may be as simple as having the incorrect settings.
The problem is, if your time zone is wrong, your cron jobs may not be having any problems. They’re working as intended, but only at the wrong time.
To check your time zone settings, simply hover your mouse on the “Settings ” menu and click on the “General ” option right on your admin dashboard.
Scroll down a little bit and you will see the timezone setting. Check whether or not the correct timezone is selected and if not, change it.
If you changed the settings, don’t forget to click on the “Save Changes ” button at the bottom of the page.
In addition, clear out both your browser cache and your WordPress data cache. If you’re not sure how to do it, check out the explanation in error #20 of this article.
Method 2: Install the Scheduled Post Trigger plugin The truth is, you don’t need to face every technical problem head-on. Sometimes, you simply have to find a workaround.
For example, if you’re experiencing the missed scheduled post error due to some problems with cron jobs, then you can simply use a plugin to do the work for you.
One plugin you can use is the Scheduled Post Trigger
You can download the plugin from the directory and upload it to your site and find it directly from your admin dashboard.
The way this plugin works doesn’t directly solve the problem. Instead, it checks for any missed scheduled posts and publishes them at the right time.
To make this work though, you still need to make sure that you have set the correct timezone in WordPress since the plugin relies on this data.
22. How to fix the “Fatal error: Maximum execution time of 30 seconds exceeded” If you’ve been trying to do some updates on your theme or plugins, then you might have experienced the “Fatal error: Maximum execution time of 30 seconds exceeded”.
No need to panic and think that something got broken. This is normal and usually happens while the system is running a PHP script and it exceeds the time limit.
The time limit was put there to serve as a security measure so people with ill intentions won’t be able to abuse your server.
Method 1: Increase the maximum execution time Starting with WordPress 5.2, you may receive an email from WordPress every time a “fatal error” is detected and provide you with more information on what caused it (like a plugin or theme).
If a plugin or theme caused it, then you can always deactivate or uninstall the cause of the problem and the issue should go away on its own.
On other hand, if you don’t want to let go with the plugin or theme, you must access your .htaccess file using an FTP client or the cPanel's file manager (see error #1 method #1).
Then, add the following code to the file:
php_value max_execution_time 300 If you use an FTP client and the Notepad++ application to edit the file, then it should look like this:
If you find this a little hard, you can also try out this next method.
Method 2: cPanel max_execution_time setting Within the cPanel, there’s an option that allows you to easily change the maximum execution time.
Find the “Select PHP Version ” option first on your cPanel.
Once you found it, navigate to the “Options ” tab.
Then, find the “max_execution_time ” setting and increase its value. The cPanel will automatically save the changes.
After doing any of the methods above, reload the page you’re trying to visit and the error should be gone.
23. How to fix the updating failed or publishing failed error in WordPress Are you editing a page or a post and you suddenly see an “Updating failed” message at the top?
This is a common error that users face when trying to update the website. The primary culprit of this is the WordPress REST API.
Basically, the REST API (a programming method) has a problem in sending and receiving requests to and from the WordPress database.
This is usually observed when updating or publishing a post or page using WordPress Gutenberg.
Here are things you can do to solve this issue:
Method 1: Check your internet connection and site URL Loss of internet connection is the most common reason why the REST API failed.
When this happens, WordPress won’t be able to save any changes you made, which is why it’s recommended to keep on saving your work every now and then.
That’s why before you attempt anything else, check that you have an internet connection. If you have, the next thing is to check the URL settings of your website.
To do so, go to the WordPress admin dashboard first, then hover over “Settings ”, and click on the “General ” option.
On the general settings, you will see a field for WordPress address and for the site address. Make sure that they’re exactly the same.
If not, change it and make sure to click on the “Save Changes ” button at the bottom of the page.
On the other hand, if you have a working internet connection and your WordPress URL and site address are the same, try the method below:
Method 2: Check the REST API status If you have been using WordPress for a while now, then you should already know that it has a site health tool.
The good thing about this tool is that although it doesn’t fix the problem per se, it shows you important information regarding the performance and security of your website.
To check it out, hover your mouse over the “Tools ” menu and click on the “Site Health ” option right on your WordPress admin dashboard.
If there’s some problem with the REST API, you should see a message that says “The REST API encountered an unexpected result”.
You could also see some information on what happened during the REST API call. Solve this issue and the error should go away on its own.
If the problem still persists, try installing the Classic Editor
24. How to fix the “Upload: Failed to write to disk” WordPress error (file and folder permissions error) Were you in the process of uploading an image or a file when the “Upload: Failed to write to disk” error happened?
If so, that’s actually good news. That’s because this error is related to file permissions and should be an easy fix.
There’s really no telling why this issue suddenly pops out, but it’s commonly caused by misconfigured permissions that might have spontaneously happened.
Solution: Configure the wp-content folder’s permissions correctly To do this correctly, you need to use a file transfer protocol client like FileZilla. Some hosts may have a file directory feature. Unfortunately, they’re not as robust as an FTP client.
Using an FTP client, navigate to your site and right-click on the wp-content folder, and select the “File permissions ” option.
A new window will pop up where you can see the file attributes for the wp-content folder.
Follow these series of steps:
On the numeric value field, enter “775 ”. Check the box for the “Recurse into subdirectories ” option. Check the box for the “Apply to directories only ” option. Click on the “OK ” button. This will correctly configure the file permission for the directories inside the wp-content folder. The next step will be about the files.
Once again, right-click on the wp-content folder , select the “File permissions ” option, and follow these steps:
On the numeric value field, enter “664 ”. Check the box for the “Recurse into subdirectories ” option. Check the box for the “Apply to files only ” option. Click on the “OK ” button. Configuring the file permissions correctly should solve the problem.
However, in the event the problem still occurs, don’t delay contacting your hosting provider. You could even ask them to clear out the temporary files directory, which might help solve the problem.
25. How to fix the ERR_TOO_MANY_REDIRECTS error in WordPress The “ERR_TOO_MANY_REDIRECTS” error in WordPress is a troublesome one simply because it prevents visitors from visiting your website and may even lock you out.
Basically, this error is caused by misconfigured misdirection, which could be caused by a number of things like plugin problems or even as simple as cache issues.
By the way, depending on the browser you’re using, you may see another error like “The page isn’t redirecting properly”.
To solve this error, try these methods:
Method 1: Clear your browser cookies and cache Before you try everything else, try visiting the website first using a different browser than the one you’re currently using.
If it turns out that you can visit the website with a different browser, then the issue is more like from your web browser cookies.
To solve it, simply find the option in your browser to clear your browsing data. It looks like this in Google Chrome and other Chromium browsers:
If you’re not sure how to do this, visit error #15 of this article.
Method 2: Fix your WordPress URL settings One of the problems with this error is that you may get locked out of the admin dashboard.
Usually, you can see the URL settings within the general settings:
If that’s the case, your only choice is to use a file transfer protocol application like FileZilla or the cPanel's file manager (see error #1 method #1) if you can access it to go through the server files.
Now, head over to the theme folder of your active theme (found inside /wp-content/themes/”active theme”).
Once you find the file, download and edit it using a notepad application.
On the bottom of the file, add the following code — but make sure to replace the URL with your site’s address:
update_option( 'siteurl', 'https://yoursiteaddress.com' );
update_option( 'home', 'https://yoursiteaddress.com' );
Make sure to save the file and reupload it to the server. Reload your website and it should be fine now.
If the problem still persists, contact your web hosting provider. There’s a possibility that the problem may be on the server-side.
26. How to fix the “WordPress could not establish a secure connection” error The “WordPress could not establish a secure connection” error is a common problem users face when trying to install or update new plugins and themes.
Under the hood, WordPress has a system that automatically checks for new updates (the one that’s showing you notifications when a plugin or theme needs an update).
The error happens when the system fails to connect with the WordPress.org website and is unable to check for new updates — which means there’s a problem with the hosting or server.
This is also important to know — but if you’re on a shared hosting plan, your server may be under attack. If that’s the case, all you need is to wait for a few minutes.
Solution: Check and update your server’s host file For this step, you need to connect to your server. If you don’t want to mess with your server, you could contact your web hosting provider and ask them to do it for you.
Those who use Mac or Linux don’t have any problems with this. Unfortunately, for Windows users, you need to install the program PuTTy to use secure shell access (SSH) properly.
In addition, you need the following information from your hosting provider:
Hostname or IP address Server’s admin credentials Once you’re inside the server, input the following command:
sudo nano /etc/hosts This opens up the hosts file where you can check if it has the correct IP address for WordPress.org.
For that, enter the following command:
66.155.40.202 api.wordpress.org Whether or not the hosts file has the correct IP address, the command above will make certain the file has the right IP address.
Now, save your changes and visit your website again. Try the update once again to see if the error has been resolved.
27. How to fix the Elementor white screen of death when editing a post or page Many Elementor users report a white screen of death while editing a page.
While the white screen doesn’t tell you anything, you can take comfort in the fact that the guys behind Elementor know the two main causes of this error:
Lack of memory Code-related Unfortunately, the only way to know which of the two caused the error, you need access to the error logs, which are discussed more fully in error #14 of this article.
Once you know what caused the issue, only then will you be able to fix it.
Method 1: Increase the memory limit The first thing you can try is to increase the memory limit via the wp-config.php file using a file transfer protocol client or the cPanel's file manager (see error #1 method #1).
Basically, you need to edit the wp-config.php file and add the code below:
Define ( 'WP_MEMORY_LIMIT', '256M' ); Like this:
If you need more information on this, go back to error #2 of this article where I discussed how to fix the memory exhausted error.
In addition, you can also try out Elementor’s built-in feature for server configurations.
Simply visit the Elementor settings page and go to the “Advanced ” tab and make sure to “Enable ” the “Switch Editor Loader Method ”.
Don’t forget to save the changes.
If the problem still persists and it’s still related to lack of memory, you need to contact your hosting provider since they may have their own way of limiting memory usage.
Method 2: Solve the underlying issue If the error log doesn’t say anything about memory issues, then it’s usually almost something related to the underlying code.
Fortunately, Elementor has a fatal error guide you can check, which serves as
If it’s not documented and you don’t see the term “Elementor” in the error logs, then it’s likely that the problem is related to some other plugin or theme.
The error logs may show you which plugin is causing it. If that’s the cause, try disabling it while you edit the page (or find an alternative plugin to use).
If the error logs have no information on which specific plugin or theme, then you may need to disable each one.
28. How to fix the “Sorry, this file type is not permitted for security reasons” error The “Sorry, this file type is not permitted for security reasons” error is an easy issue to solve — and one that doesn’t need any technical know-how.
From the name itself, this error happens when you try to upload a file that WordPress doesn’t support.
The feature is there for your own benefit so others may not be able to upload a malicious file to your website.
Here are ways to fix this issue:
Method 1: Check for misspelling in the file extension Have you tried to upload a similar file before without any problem? If so, it’s possible that the problem may be that you misspelled the file type extension.
The file extension from WordPress may sound restrictive, but it actually supports most file types:
Images : .ico, .png, .jpg, .gif, .jpegDocuments : .pdf, .psd, .doc, .docx, .ppsx, .pps, .pptx, .ppt, .xls, .xlsxAudio : .ogg, .wav, .mp3, .m4aVideo : .mp4, .3g2, .m4v, .3gp, .mpg, .ogv, .mov, .avi, .wmvThat’s why if you have uploaded a similar issue before, then you may need to check the spelling of the file extension.
You can either check the file properties before uploading the file or enable the view file name extension on the file explorer program you’re using.
Method 2: Install the File Upload Types plugin If you really want to upload a file that WordPress doesn’t support, then you can install the File Upload Types
You can either download the plugin files from the WordPress directory or search and install them directly from your WordPress admin dashboard.
Once you have it installed, hover your mouse over the “Settings ” link and then click on the “File Upload Types ” option.
On the next page, all you need to do is check the box of the file type you want to upload.
Don’t forget to click on the “Save Settings ” button at the bottom of the page.
After this, you should be able to upload the file you want to upload without any problems at all. You can then enable/disable the file type from the same settings page.
29. How to fix the mixed content error in WordPress The mixed content error is a harmless issue in regards to the website’s functionality. However, it may negatively affect your website’s SEO and how people view your website.
Basically, you will be seeing this error if you have incorrect HTTPS or SSL settings, which verifies your website’s security.
If you haven’t installed any SSL certificates yet or your hosting plan doesn’t provide a free one, head over to the Let’s Encrypt
Now, if you already have a working SSL certificate and you’re still seeing the mixed content error, then it’s time to use a fix:
Solution: Install the Really Simple SSL plugin The easiest way to solve this problem is through a plugin like Really Simple SSL
To start, make sure to either download and upload the plugin files or search for them from the admin dashboard.
Once you find it, install and activate it on your website.
Then, visit the plugin’s settings page. Hover your mouse over the “Settings ” link and then click on the “SSL ” option.
Once you’re on the settings page, all you have to do is make sure “Mixed content fixer ” is enabled and click on the “Activate SSL ” button.
If you have an SSL certificate, this should automatically fix the issue.
There are also other settings you can try like “Fire mixed content fixer with different method” in case the problem still persists.
30. How to fix the “Parse error: syntax error” in WordPress When you’re more comfortable with WordPress, it’s normal to experiment and try out different things — including pasting code in templates.
Now, if you’re facing the “Parse error: syntax error” while trying to load a page, don’t panic.
The most likely culprit is the new code you added. There’s a small mistake in the code you used which may have messed up the code syntax.
If you weren’t locked out of the admin dashboard, you can always delete the new code you used. But if you’re locked out, your only choice is to use a file transfer protocol client.
Solution: Use an FTP client and delete or correct the code Fortunately, the fix for this is quite easy. Simply use a program like FileZilla and connect with your website server.
Once there, find the file that caused the problem and delete or correct the code that’s causing the error.
For example, you can immediately download the functions.php file from your active themes folder and make the changes.
Just don’t forget to reupload the file to save the changes you made.
It’s also easy to spot which file is causing it and on what line since the error usually mentions this to help you in fixing it.
The “Warning: Cannot modify header information” is one of the easiest errors in WordPress to solve.
This error appears when there’s a faulty or incorrect code right in your page header. The error message you see will contain the origin of the error as well as the line #.
Rarely, a plugin that touches header code might also be causing the problem, which you will know too right inside the error message.
Solution: Edit the page header Since the error occurs in the page header, you can actually use the theme editor tool in WordPress or use an FTP client and a notepad application to edit the code.
If the problem is code-related, it’s most likely due to whitespace or a misplaced print or echo statement.
For example, if the message indicates the error is in the functions.php file, simply go to your active theme’s folder and open the file from there.
Note that you can also use the cPanel's file manager (see error #1 method #1) if you web host provider supports it.
Simply do the fixes — like erasing whitespace — and save the changes you made.
After this, the error should go away on its own. If you find it hard to spot the error, ask someone who understands PHP code.
32. How to solve the “ECONNREFUSED — Connection refused by server” error The “ECONNREFUSED — Connection refused by server” error isn’t a WordPress error per se, but one that you might encounter while using an FTP client like FileZilla.
From the name itself, the problem is that the file transfer protocol program isn’t able to connect with the server.
Fortunately, this is easy to solve. However, make sure that before you try any fixes, you enter the correct host value, username, password, and port number.
Method 1: Disable your firewall or antivirus application It’s possible that the firewall or antivirus program in your computer is blocking the connection between the FTP client and your website’s server.
Check your firewall or antivirus and see if you can find the option to disable it temporarily.
For example, with Microsoft Defender, you simply have to go to the “Firewall & network protection ” page and disable the firewall from there.
Unfortunately, if you really can’t find the option in the firewall program you’re using, you may have to uninstall it for a while and see if it solves the problem.
Method 2: Configure the network configuration wizard in FileZilla If you’re using FileZilla, then you may need to edit the network configuration wizard.
On the client, click on the “Edit ” tab and select “Network configuration wizard ” from the choices.
A “Firewall and router configuration wizard ” window will pop up. Nothing much to do on this window — click on the “Next ” button to proceed.
On the next page, select the “Passive (recommended) ” option as the default transfer mode. Then, check the box for the “Allow fallback to other transfer mode on failure ” option.
Then, click on the “Next ” button to continue.
On the next page, select the “Use the server’s external IP address instead ” option and click on the “Next ” button.
Select the “Get the external IP address from the following URL ” option and make sure it has the value below and click on the “Next ” button.
http://ip.filezilla-project.org/ip.php Lastly, select the “Ask operating system for a port ” option on the next page without changing any other options and click on the “Next ” button.
The next window will allow you to test the configuration. Simply click on the “Test ” button to see if the changes worked out in your favor.
If you don’t see any errors during the test, then try and connect with your server again. The connection should work out fine now without the error.
33. How to fix the “Missing a temporary folder” error in WordPress The “Missing a temporary folder” error is a problematic one since you won’t be able to do a lot of things like updating the WordPress core, plugins, themes, or even uploading images.
In the back end, this error is caused by misconfigured PHP settings on your hosting that specify the address of the temporary folder to be used.
Fortunately, it’s quite easy to solve this.
Solution: Define the temporary folder For this, you need to access the wp-config.php file using a file transfer protocol client like FileZilla or the cPanel's file manager (see error #1 method #1).
If you’re using an FTP client, you need a notepad application to edit it.
Add the following code to the file:
define('WP_TEMP_DIR', dirname(__FILE__) . '/wp-content/temp/'); Like this:
Make sure to re-upload the file back to the server to save the changes.
After that, go to the wp-content folder in your server and add a new folder inside it with the name “temp ”.
After this, you can now go back to the admin dashboard and try updating a plugin or theme and uploading an image. It should be fine now.
Have more errors to share? That’s about it! We hope this guide will serve as the ultimate troubleshooting manual in WordPress. Unfortunately, we may not know all the errors there are to know about.
That’s why we highly encourage you to leave a comment or question when you experience an error that’s not listed in this article.
We will be updating this guide as we get new errors or issues to help you out in your WordPress journey.
דירה דיסקרטית בחולון
Everything is very open with a really clear clarification of the issues. It was definitely informative. Your site is extremely helpful. Many thanks for sharing!
blocked drains burnham
After loⲟкing օvеr a number of the blog articles on your blog, I
honestly apρreciate your way of blogging. Isaveed as
a favorite it to mmy bookmaгk wegρage list and will be checking back in the
near future. Take a look at my web sіte too and let me know ʏour opinion.
Here is my wｅb bⅼog :: blocked drains burnham
blocked drains wokingham
What’s ᥙp, I wznt to subscribe for this weblog to obtain mostt up-to-date
updates, thus where can i do it ploеase assist.
Have a look aat my web blog :: blocked drains wokingham