Common WordPress Errors
82 / 100

If you’ve got your business website built off of WordPress, you’ll presumably run into some common WordPress errors. You’re also faced with one immediately , otherwise you wouldn’t have found your way here.

Don’t worry. the chances are in your favor. Having built your site with WordPress, you’ve got other users who have skilled an equivalent WordPress errors and have presumably found a fix.

WordPress has been around within the Content Management space for quite 15 years now. it’s the foremost popular content management system available. WordPress is predicated on the highest of PHP and MySQL.

It gives users different features enabling them to make interactive and responsive sites during a short period. WordPress supports different plugins which have made web development faster and easier.

If you’ve got been using WordPress for quite a while now, you’ll have noticed a couple of errors and problems that are common with every WordPress site. These errors are likely to occur in every WordPress.

In this article, we’re breaking down ten of the foremost common errors WordPress users run into with easy fixes you’ll do yourself.

But first, a word to the wise…


WordPress Site Admin Credentials
Text Editor (Sublime, Notepad, etc.)
FTP Client (FileZilla, Cyberduck, etc.)
cPanel Credentials

Backup your site!

Some of the processes we’ll share with you today require a touch of tinkering on the backend which may cause God knows what tragicomedies. You’ll prevent an honest deal of potential stress if you backup your site before you create any changes.

Your web host usually offers a variation of such a service, but you’ll roll in the hay yourself by using WordPress plugins. Though it’ll cost you a touch of cash , Vaultpress may be a light but mighty solution. However in most cases, UpdraftPlus’ free plugin works just fine. There’s also the choice of doing it manually if that tickles your fancy.

Regardless of which process you accompany , it’s essential that you simply have a WordPress backup in situ before you are trying anything.

To alleviate any longer problems during this process, you would possibly also want to try to to some WordPress troubleshooting and pinpoint exactly what you’re trying to repair .

With all that said, let’s dive in!

Most Common WordPress Errors

1. WordPress Error Establishing a Database Connection
The Problem:

‍This error occurs when WordPress has trouble connecting to your site’s MySQL database server. Your database is where all of your files live. If WordPress can’t hook up with it, your site is presumably getting to be down.

‍The Solution:

‍Check if wp-config.php checks out

The wp-config.php file contains your login credentials and other essential details about WordPress.

Make sure your username, password, database name, and therefore the host server is correct. To do so, mount over to your root directory and locate the wp-config.php, access it, and confirm this code has your correct credentials in it.

define(‘DB_NAME’, ‘database_name’);
/** MySQL database username / define(‘DB_USER’, ‘username’);/* MySQL database password */
define(‘DB_PASSWORD’, ‘password’);
/** MySQL hostname */
define(‘DB_HOST’, ‘localhost’);

Doing this resolves the difficulty in most cases.

Reach bent your host for help

If the error persists, it’s possible that something has gone south together with your MySQL servers otherwise you may need reached their maximum size. In either case, it’d be time to contact your web host and invite a fast fix.

2. 500 Internal Server Error

The Problem:

‍This is one among the foremost common errors WordPress users face, largely because it means something went south together with your server and WordPress doesn’t know exactly what it’s .

You can easily detect this problem once you get an “Internal Server Error” or “500 Internal Server Error” once you go online to your WordPress site.

The Solution:

‍As you’ll imagine, there are variety of the way you’ll set about fixing this error.

Check your .htaccess file

The .htaccess file is your friend. It helps your site skills to function by directing it with rewrite rules. But it also can be an enormous pain because it makes changes whenever you add new functions to your site. As such, it can get corrupted and cause you to urge the dreaded error.

Luckily, there’s a fast fix.

Go to your FTP client and locate the .htaccess enter your root directory. If you can’t see it, you’d want to enable “force show hidden files”.

Once you’ve located the file, rename its filename into .htaccess_old. Reload your site.

If that fixes the error, go re-save your permalink structure (in Settings > Permalinks) to get a replacement .htaccess file.

Increase your PHP memory limit

SEs (Internal Server Errors) also can flow from to insufficient memory in your wp-config.php file. during this case, the straightforward fix is to extend the PHP memory.

To do this, access your wp-config.php file and add the subsequent line:

define(‘WP_MEMORY_LIMIT’, ’64M’).

This strip of code will tell WordPress to extend your site’s memory limit to 64MB. Other variations of this code are set to 128MB and 256MB if your situation and hosting provider permits. you ought to also paste the code just before the road that says “That’s all, stop editing! Happy blogging.”

It’s worth noting that not all web hosts allow its users to extend their sites’ memory limit on their own, during which case you’ll got to ask them to try to to it for you.

Remotely deactivate all plugins

Sometimes a nasty plugin can trigger an indoor Server Error. This happens when plugins are incompatible together with your current WordPress version or when plugins are corrupted and vulnerable within the first place.

Don’t panic. you’ll easily fix this.

What you would like to try to to is to deactivate your plugins and reactivate them one by one until you notice which one causes the error.

I will sometimes lock you out of the wp-admin, during which you’ll need to do that remotely. attend your FTP client, locate the wp-content folder, and rename your plugin folder into “plugins_old”.

This will deactivate all of your plugins and obtain obviate the error, supplying you with access to the backend of your site. There, simply reactivate plugins individually and see which one(s) are causing the matter .

Reach bent your host if you’ve exhausted all the choices above, it’s time to contact your web host and ask them to try to to it for you from their end. Most web hosts are going to be happy to try to to it for you.

3. WordPress’ White Screen of Death

The Problem:

‍The dreaded White Screen of Death has made hearts dropp in WordPressers’ chest since it first afflicted WordPress sites. WSOD, as users wish to call it, makes your site disappear to point out only a white screen with nothing in it. Think Windows’ Blue Screen of Death but far scarier.

There are variety of things which will cause this, but with no error message to point out , it’s hard to pinpoint.

‍The Solution:

‍As such, users have pointed to variety of solutions. We’ve listed the foremost popular ones below.

Increase your PHP memory limit

Depending on your hosting, your WordPress site will have different memory limits and is therefore susceptible to different memory issues.

When you run into a WSOD error, your initiative should be to extend your site’s memory limit.

Read abreast of our guide within the “Internal Server Error” section.

Remotely disable all of your plugins

Sometimes alittle faulty plugin can take your whole site down. to seek out out which one causes the difficulty , remotely disable all of your plugins via an FTP client and reactivate them one by one to seek out out which is that the culprit.

Read abreast of our guide disabling plugins within the “Internal Server Error” section.

Use the default theme

A corrupted or faulty theme also can be the culprit for a WSOD error. If you’ve installed a replacement theme and got the error, it’d just be the one that’s causing the difficulty .

In this case, you’d want to use the default theme.

If you can’t access your backend, you’ll need to set the theme remotely using your FTP client of choice.

Similar to the method of deactivating plugins, you’ll got to rename your themes folder into “folder_old”. Doing this may automatically set your site with the default theme and put your site copy .

Enable debug mode

If none of the above fixes work, try enabling the debug mode. To do so, find the wp-config.php in your site’s root directory and add this line:

define(‘WP_DEBUG’, false);

In most cases this may resolve the difficulty .

Reach bent your host for help

If the aforementioned solutions don’t work, seek the assistance of your web host in fixing the error.

You should be seeing a pattern here. There’s only such a lot troubleshooting you’ll do on WordPress. If these errors persist, it’s knowing reach bent your hosting provider for technical support, or better yet, hire a developer if you discover yourself on the deep end.

4. WordPress 404 Errors

The Problem:

‍Another common WordPress issue is posted returning 404 errors.

This error is typically triggered when your .htaccess file is deleted or its rewrite rules have are corrupted. This causes your single post pages to return as 404 errors, with the remainder of your site perfectly accessible.

The Solution:

‍While it definitely sounds serious, the fix for 404 Errors is straightforward and easy .

You only got to attend your permalinks settings (Settings > Permalinks) and hit “Save Changes” to get a replacement .htaccess file with the right rewrite rules.

5. Locked Out of WordPress Admin (wp-admin)

The Problem:

‍Getting locked out of the WordPress admin is more common than you think that . It’s easy to lose track of login credentials for many sites we log into a day . There’s no shame in it—even the simplest folks forget their WordPress passwords too.

But what if the recovery email doesn’t work for a few reason? It sounds pretty alarming, but don’t pull all of your hair out just yet. There’s a reasonably easy solution for this.

The Solution:

‍If you’re unable to access the WordPress backend, you’ll got to reset your password inside the database through PHPMyAdmin. The interface for PHPMyAdmin is typically located in your provider’s instrument panel .

Once you’re in, find your site’s database and locate the wp_users table.

Find your username within the user_login column and click on “Edit” on the left-hand side.

On subsequent screen, find a field called “user_pass”. Change that to your required password. Under the “Function” column, tick the menu and set it to MD5. Click “Save Changes” and you’re good to travel .

You should be ready to login to your site using the new password you’ve created.

6. WordPress Error: Connection Timed Out

The Problem:

‍You’ll typically get a “Connection Timed Out” error when your site takes a really while to load only to urge a mistake that it’s not available.

This simply means your server isn’t handling the load of your site all that well. this is often quite common in cheap, shared hosting plans where you share limited resources with other users.

The Solution:

‍Like within the White Screen Of Death error, there are a few of main solutions to repair this issue.

Increase your PHP memory limit

The most common fix for this error is increasing your site’s memory limit. By giving it a much bigger memory allocation, you’re making it easier for your site to try to to its heavy-lifting.

Read abreast of our guide within the “Internal Server Error” section.

Remotely disable all of your plugins

Plugins also can cause timed-out connections.

Read abreast of our guide disabling plugins within the “Internal Server Error” section.

Use the default theme

Your site can also get timed-out connections due to theme issues.

Read abreast of our guide disabling plugins within the “White Screen of Death Error” section.

7. “Upload: did not Write File to Disk” Error in WordPress

The Problem:

‍If you’re seeing the WordPress error “Upload: did not write file to disk” when uploading files to your media library, it means your site’s permissions are set incorrectly. This blocks you from writing files on your server, including adding new files.

The Solution:

‍To fix this error, you’ll need an FTP client. This process will look a touch different, except for the sake of example, we’re using FileZilla.

First, connect your site to your FTP. Locate the wp-content folder. Right-click, then select file permissions.

A panel called “Change file attributes” should crop up . Change it to the subsequent settings:

  • Owner permissions: Read, Write, Execute
  • Group permissions: Read, Execute
  • Public permissions: Read, Execute
  • Numeric value: 755
  • Recurse into subdirectories: Yes
  • Apply to directories only: Yes
  • Click okay to save your settings

This on its own can resolve the difficulty . If it doesn’t, repeat the method once more , this point modifying the panel with the subsequent settings.

  • Owner permissions: Read, Write, Execute
  • Group permissions: Read, Execute
  • Public permissions: Read, Execute
  • Numeric value: 644
  • Recurse into subdirectories: Yes
  • Apply to files only: Yes
  • Click okay to save your settings

If the matter persists, it’d be time to contact your web host and have it fixed for you.

8. WordPress Fatal Error: Allowed Memory Size Exhausted

The Problem:

‍We’ve talked tons about memory issues earlier during this article. So this error shouldn’t make your knees tremble. Even so, to be greeted with such a selected sort of error as written below is nerve-wrecking.

Fatal error: Allowed memory size of 33554432 bytes exhausted

(tried to allocate 2348617 bytes) in

/home4/xxx/public_html/wp-includes/plugin.php on line xxx

But don’t panic! this is often easily fixable.

The Solution:

‍Because WordPress relies on memory to efficiently run its functions all at an equivalent time, your server would require allocated memory sizes to different applications including PHP.

By default, WordPress sets your limit sub-64MB. So, using the method we’ve taught within the “Internal Server Error” section above, edit your wp-config.php file and add the subsequent code:

define( ‘WP_MEMORY_LIMIT’, ‘256M’ );

As mentioned before, confirm that the code is pasted just before the road that says “That’s all, stop editing! Happy blogging.”

9. WordPress Sidebar Showing Below Content

The Problem:

‍Nothing quakes one’s OCD mind quite seeing all the work you set in your WordPress theme get mangled by having your sidebar shown below your content. It’s ugly, wonky, and doesn’t make a really good impression to your customers.

But why does this happen?

It can mean one among two things:

1.) your theme files are corrupted, or

2.) your HTML is invalid.

The Solution:

‍To fix this, you would like to work out which of the 2 causes are making your sidebar appear below your content.

If it’s due to your theme, a simple fix is to form sure that your theme is updated to its latest version. you’ll do that by getting to Appearance > Themes.

If that doesn’t resolve the difficulty , you would possibly want to see the theme’s style.css file, which you’ll access via Appearance > Editor. you would possibly have set sizing properties to your content and sidebar areas that confuse your site and causes it to put the sidebar below the content.

If it’s due to your HTML, check for a few tags. These tags tend to form your site’s layout an entire mess if there’s too many of them are baked into your HTML. you’ll use an HTML validar to assist detect which tags are causing the difficulty .

10. “Briefly Unavailable For Scheduled Maintenance” Error after a WordPress Update

The Problem:

‍When you get the “Briefly unavailable for scheduled maintenance” error, it’s not really a mistake . Technically, it’s a notification page. This usually happens once you update your WordPress to a replacement version.

Users get this error when WordPress has a tough time pushing some changes thanks to slow servers and low memory issues. Sometimes, WordPress will find it hard to urge your site out of maintenance mode, hence the difficulty .

The Solution:

‍There’s a simple fix to the present . Whenever you update your site, WordPress creates a .maintenance file which indicates that your site is in maintenance mode. If you delete this enter your root directory, your site will finally be out of maintenance mode.

Do note that you simply need to confirm that WordPress has successfully updated your WordPress before doing this. If you delete the .maintenance file and therefore the update didn’t undergo , deleting the file might cause you some issues to your site.

Error-proofing your WordPress site

WordPress has been a present to tons of online entrepreneurs like yourself. Anyone patient enough to tinker around this great CMS can most definitely get the hang of it. But that doesn’t mean it’s perfect, either.

If you’re using WordPress, it’s easier to reconcile with the very fact that you’ll encounter errors like those listed above.

What’s great with WordPress is that, backed with a thriving user base and a helpful open community, these errors will nearly always have a fix available somewhere.


Please enter your comment!
Please enter your name here