WordPress Error Fix

How to Fix the 403 Forbidden Error in WordPress

There is so many painful errors in wordpress. One of those is 403 Forbidden Error in WordPress. This error occurs when you have file permission settings are incorrect or your htaccess is corrupted or your plugins are acting weird. This is one of the painful error in wordpress. Your website was up and running everything is ok but suddenly showing 403 Forbidden Error. In this article we will see how to fix this.

Table of Contents

• What is 403 Forbidden Error in WordPress
• Ways to fix 403 Forbidden Error in WordPress
  • Fixing 403 Forbidden Error by caused plugin
  • Fixing 403 Forbidden Error by caused corrupted htaccess
  • Fixing 403 Forbidden Error by incorrect file permission
• Conclusion

What is 403 Forbidden Error in WordPress

403 Forbidden Error shows when you don’t have permission to visit the directory. So it is very straight forward that 403 mostly occurs for incorrect file permission. You can see this error in several directories. Such as:

• 403 Forbidden – Access denied on wp-admin or WordPress login page.
• 403 Forbidden – during WordPress install.
• 403 Forbidden error when visiting any page on your WordPress site.
• 403 Forbidden error – when you click add post or add plugin or Themes.

Now you know what is 403 forbidden error is and where it could happen. Now lets talk about how to fix this error.

Ways To Fix 403 Forbidden Error in WordPress

Before you start doing any trouble shooting I recommend at first take backup of your website. Now the possible solutions for 403 forbidden errors in wordpress are:

• Troubleshooting Plugins
• Changing htaccess
• File Permission Checking

Let’s speak in details about these methods.

Fixing 403 Forbidden Error by caused plugin

Not every plugin is compatible with your WordPress website. In fact there is several plugins that doesn’t work when you put together with other plugins. To verify which plugin is causing  403 forbidden error on your site:

• Deactivate all plugins that are installed on your WordPress Site.
• Re-activate one of the plugins on your list.
• Visit the site to see if the 403 forbidden error is being displayed.

After deactivating all of your plugins and the 403 forbidden error is still showing, then the problem may not be plugin related. In this case you need to jump to the next section.

Fixing 403 Forbidden Error by caused corrupted htaccess

One of the main reason for 403 forbidden error is a corrupt .htaccess file in your WordPress site. Repairing this file is quite easy. To do this:

• Login your cpanel or FTP
• Navigate to file manager
• Locate the .htaccess file then download it and delete that.
• Now if you can visit your wordpress dashboard then go settings > permalinks >click save

It will generate a fresh htaccess and you will able to see your site without having 403 forbidden error.

If it doesn’t fix your 403 forbidden error then it is not htaccess related. Re-upload old htaccess and jump to the next section.

Fixing 403 Forbidden Error by incorrect file permission

File permission is one of the main reason for this 403 forbidden error.  The folder permissions of any WordPress site should be set to 744 or 755. File permissions should be set to 644 or 640. If these numbers are set incorrectly it causes 403 forbidden Error.

To set file permission correctly you can contact with your hosting provider. Or by doing yourself follow these steps:

• Login to your cpanel or Ftp
• Right click on folders and set the permission to 744 or 755
• Right click on your files and set the permission to 644 or 640.

I think this will help. If above methods doesn’t work for you then you should contact with your host.

Conclusion

I think this post helped you to resolve 403 forbidden error in wordpress. If you need any help about WordPress Error Fixing feel free to comment here

How to Fix Error Establishing a Database Connection in WordPress

Error Establishing a Database Connection in WordPress is a common error in WordPress. Which frightens an users that his site got “hacked” or “broken”. It is a look like of white death error or white screen of death error in wordpress. Because there is nothing without a text “Error establishing a database connection”. This error actually means your wordpress cannot communicate with Database, so your total website goes down. This is a type of error what you should take an action immediately and take lightly to resolve the error establishing connection. Cause it is bad for your SEO and your visitors as well. So

Literature Review

To understanding better why this error happens first we need to know how wordpress structured.

WordPress is built with PHP. And most people uses : Mysql Database for wordpress. Though we can use other DB for WordPress that is an advance part.

In very basic WordPress uses PHP for functional work and Mysql to store all of your content in the database. This includes your posts, pages, but also the smaller elements, such as the title of your site, the layout of your widgets, the color settings, and etc. Basically, the MySQL database is where every, even the smallest piece of information about your website, is kept.

WordPress uses php to connects the database (Mysql). Then get the information when it needs and shows in the screen as output.

The Error Establishing a Database Connection actually occurs when PHP cannot connect with the Database. This can happens by:

• Incorrect login credentials: WordPress requires an user name, password and hostname to connect database. If any of these are wrong then it shows this error.
• Corrupted WordPress files: If the core wordpress files got corrupted or it hampers in the mid of any kind of wordpress update then this error could happen. Messing updates can includes plugins update, theme update and core wordpress update and etc.
• Corrupted database: If the database got corrupted by hackers or messing by your plugins then also this error can occur.
• The database server is down: If the hostname I mean the db host is down then PHP cannot able to connect with the database and shows this error in wordpress.

How to fix Error Establishing a Database Connection in WordPress

Before we start we always recommend you to take backup your wordpress website. Once you completed your backup then we can proceed how we can fix this wordpress error.

There is actually several methods to fix this. Such as:

Step 1:  Checking Database Login Credentials

Very first step to fix this error is to check db login credentials. So, we already know that to connect with database wordpress needs db_name, db_user db_passwords, db_host.

Check Database Credentials in cPanel

• Database Name: The first thing to check is the database name. To do this you will need to login to phpMyAdmin in cPanel under the Databases section.

After signing in to the phpmyadmin you will see your database name:

• Resetting Database Username and Password: If you already know the database username and password then jump into the next section. If you doesn’t know the database username and password then continue reading. To reset your database from cpanel navigate to database section and click on MySQL Databases. 

Now check the username of database which one is assigned to your wordpress website’s database.

Now scroll down to the “Current Users”. And click “Change Password”.

Now generate your passwords:

Now check those at your wp-config.php file. To do that check underneath.

Mysql Database Name: In wp-config.php file fiind this code:

// ** MySQL settings ** //
/** The name of the database for WordPress */
define('DB_NAME', 'xxxxxx');

Check your DB name if it is correct. If it is wrong then change this. It will solve your problem.

 

Mysql Database User name: In wp-config.php file find this code:

 

/** MySQL database username */
define('DB_USER', 'xxxxxx');

Check if the DB user name is correct.

Mysql Database Password: In wp-config.php file find this code:

/** MySQL database password */
define('DB_PASSWORD', 'xxxxxxxxx');

Check if he database password is correct. If it doesn’t change it. Then fix this.

 

Mysql Host Name: In wp-config.php file find this code:

/** MySQL hostname */
define('DB_HOST', 'localhost');

Check if the Host name is correct or not.

Here is an example below of what the file looks like when opened.

Step 2:  Checking Corrupted Theme or Plugin

We already seen to check corrupted database to solve this error. WordPress has massive collection of themes and plugins. In your WordPress website you must have a theme and some plugin to maintenance your WordPress website. So it is a very common scenario that plugins or theme causes so many unknown problems.

• Checking corrupted theme: At first login to your Cpanel or Login to you FTP. Then “wp-content” Now rename the folder named  : “themes” to anything such as: “themes1″. Now hit your wordpress dashboard url in the browser such as “yourwebsite.com/wp-admin” see if it is accessible. If the wordpress admin dashboard is accessible then navigate to “Appearance > Themes” and activate a default theme such as “Twenty Sixteen”. Then hit your website if you still see the error then check your corrupted plugins.
• Checking corrupted plugins: At first login to your Cpanel or Login to you FTP. Then “wp-content” Now rename the folder named  : “plugins” to anything such as: “plugin1″. Now hit your wordpress dashboard url in the browser such as “yourwebsite.com/wp-admin” see if it is accessible. If the wordpress admin dashboard is accessible then navigate to “Plugins” and activate one by one and check which one is the culprit. It will solve your Error Establishing a Database Connection problem.

Step 3:  Check if the database has been corrupted.

WordPress database is a very complex thing. There is so many things that many of the developers doesn’t know. This is a very rare situation an user can face. To fix this open you “wp-config.php” file. Then add these lines of code:

define('WP_ALLOW_REPAIR', true);

If you don’t understand where to add check the image.

Now in browser hit this url “https://yourdomain.com/wp-admin/maint/repair.php“. Note: in yourdomain put your domain name.

Then a window will appear. Choose “Repair Database” from there.

After running the repair of the database above, ensure that you remove the line of code you added to your wp-config.php file, otherwise anyone could run the repair.

If no error, great! If the error’s still there, next step is:

Step 4: Re-upload WordPress Core files

The next possible reason you might be seeing the error establishing a database connection message is that your wordpress core files have become corrupt.

So to fix this first backup your wp-config.php and wp-content folder.  Then go to wordpress.org and download latest version of wordpress.

Unzip this file on your computer. Inside, you need want to delete the wp-content folder, as well as the wp-config-sample.php file.

Now paste your wp-content folder and wp-config.php file here. Then upload through your FTP or Cpanel. It will solve the wordpress error.

Step 5: Contact your Host

If you see no troubleshoot is solving the problem last step is contact your hosting provider. They have the access in PHPMYADMIN. They can check if the database server is down. When they up the DB server then the problem will solve automatically

How To Avoid This Error In Future?

• Take a good hosting provider
• Back up daily.

I hope this tutorial help you to solve the Error Establishing a Database Connection in WordPress! And as always, feel free to reach out to me if you’re having some tough time with an error establishing a database connection.

How to Fix WordPress Posts or Page showing 404 Error

In WordPress you will see a lot of errors. Though it is a very powerful cms.  The biggest frustrating thing is getting 404 errors when you already have those Page or Post in your WordPress website.

Generally with this error an user can access their WordPress admin area, their blog’s main page, but when accessing a single posts they get a 404 Not found error.

Things like the white screen of death when you upload images, update themes or plugins which can also happen.

Today we will show you how to fix 404 errors in wordpress.

Why this 404 error occurs when you already have that page or post in your WordPress

It is the output of conflict in mod_rewrite in Apache. If it is not enabled or if it is not configured properly it cannot rewrite your URL to use your selected permalinks.

How to fix WordPress posts or page returning 404 error

There is actually two possible solution. Those are:

• Resetting your Permalinks
• Resetting your .htaccess

Resetting your Permalinks

A permalink is a permanent URL for your posts, categories, files and other comparative pages. It’s the one of a kind connection that coordinates to a particular, comparing post.

When you install WordPress, It automatically setup a default permalink for you, however, you can choose the permalink types by your own in wordpress later on.

If in any means Apache extension mod_rewrite disabled or there is conflicting between apache extension with your theme or plugin then your links stops working.

So resetting permalinks will works in most scenario. To do that please follow these steps:

• Go to Settings » Permalinks
• Select Plain and click Save Changes.

 

• After saving then select your previous permalink that you had and click Save changes.

It will reset your permalink settings and you should able to see your posts without having 404 error.

If this doesn’t fix then please continue to the article:

Resetting your .htaccess

 

To reset your .htaccess login in your cpanel or FTP. Then:

• Rename your .htaccess file to .htaccess_old
• Create a new .htaccess file.
• For single installations of WordPress paste these lines of codes:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - 
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php 
</IfModule>
# END WordPress

• For subdirectory installations of WordPress Multisite, use the code below:

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - 

# add a trailing slash to /wp-admin
RewriteRule ^(+/)?wp-admin$ $1wp-admin/ 

RewriteCond %{REQUEST_FILENAME} -f 
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - 
RewriteRule ^(+/)?(wp-(content|admin|includes).*) $2 
RewriteRule ^(+/)?(.*\.php)$ $2 
RewriteRule . index.php 

• If install WordPress in subdomain, use this instead:

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - 

# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ 

RewriteCond %{REQUEST_FILENAME} -f 
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - 
RewriteRule ^(wp-(content|admin|includes).*) $1 
RewriteRule ^(.*\.php)$ $1 
RewriteRule . index.php 

Once you saved the files the rewrite rules will be flushed and you should see your posts.

Fixing Custom Post Types

If you are having the errors in your custom post types. Then you need to check custom post types unique  slug and title.

If two or more posts contains same title or slug, then you should change those. Because only one post can have that title and slug so be sure to change the others to something unique.

Further Troubleshooting

If it stills appear the error then you can change the .htaccess file permission to 600 or 777.

If you think it is causing for your theme then simply activate a pre packaged theme like twenty sixteen. Then check a single post if it is fixed.

If you think it is causing for your plugin then deactivate all plugin and check. Then activate one by one which one is the main culprit for this 404 error.

Get Help From an Expert:

There is a lot of wordpress expert available if the steps don’t changes the scenario of the error.

You can get a help of hand for resolving the issue by our super 24 / 7 support team. Our expert team replies immediately for any kind of wordpress errors. To do that simply go to our Request a quote page and submit.

How To Fix The White Screen Of Death In WordPress

The ‘White Screen of Death’ (WSoD) is a very much reported WordPress error which can originate from various diverse causes, and is just as irritating as its blue-colored Windows error. What makes this error so troublesome is the total absence of any error messages when it happens, which can make it a bad dream to investigate.

Gratefully, the WordPress people group is nothing if not resourceful, and after some time they have found how to handle the most widely recognized the White Screen of Death. Because of the natureof this error, Fixing it will regularly expect you to investigate your WordPress install start to finish with a specific end goal to discover the offender or problem.

Before we dig into the investigating procedure, how about we pause for a minute to go over the most well-known reasons for the WSoD.

What’s the reasons of  White Screen of Death?

Regardless of the lack of data showed on the WSoD, after some time the WordPress has described the list of regular suspects down to the accompanying:

• Memory limit set by your hosting service, which is most often seen in shared hosting.
• Theme not connected in proper way with one of your plugins or vice versa.
• A poorly coded theme or plugin causing an error when WordPress is updated.
• A compatibility issue between plugins.
• Auto upgrade issues.
• Maintenance mode freeze.

We’ll discuss more details regarding each one of those possible reasons in their own scenarios while covering the troubleshooting process.

Step by Step Troubleshooting

Since the WSoD usually affects the WordPress admin panel, We suggest use FTP to connect with your wordpress website.

1. Check Your Memory Limit

It is one of the most common errors you might run into while using WordPress and it’s very easy to fix, so open that FTP and let’s get to work!

• Connect to your FTP server
• Look for the wp-config.php file
• Then right-click on it and choose the View/Edit option.

 

• • Add the following line within the main PHP tags:

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

Save and close the file and check if the error still on your site.

2. Check Your Plugins

• Rename the plugins folder to anything

Then check if the error is not there then login to wp-admin

• Active plugin one by one and check which one is creating problems.

3. Check Your Theme

• Back up and Remove the activating theme.

Check if fixed then change the theme or update the theme according to new WordPress updates.

Wait – what if none of these steps fixed your White Screen Of Death? Then it’s time to break out the magnifying glass.

4. Check Your Logs

In this situation, the WordPress debug mode is your Microscope – it will enable you to look on error logs, which should enable you to pinpoint the source of the. (In even, If r the past sections solved your little White Screen of Death issue, knowing how to turn on the debug mode can come in truly helpful.)

• Open FTP manager again
• View/Edit wp-config.php
• Add this line after DB password: define(‘WP_DEBUG_LOG’, true);

Conclusion

At first the White Screen of Death can be very scarry, thanks to some degree because of seeming like a death metal collection. In any case, once you’re mindful of the variables which may cause it and have experienced the way toward investigating your site again from it, you’ll be more than arranged to handle anything that WordPress may toss at you.

Just remember, if you ever run into the White Screen Of Death, be sure to:

1. Check your memory limit.
2. Check your plugins.
3. Check your themes.
4. If all else fails, activate the WordPress debug mode and check your logs.

How to fix ERR_TOO_MANY_REDIRECTS in WordPress

If you have a WordPress website. You will experience a different types of problems and errors. ERR_TOO_MANY_REDIRECTS is one of the common errors that we face regularly. In this post, we will explain what makes this error and how fix it.

What Is ERR_TOO_MANY_REDIRECTS?

ERR_TOO_MANY_REDIRECTS (or redirect loop) is an error that is appeared to you and your site traffic when your site stalls out on an infinite loop of redirections. This implies the site continuously sending you back to the among URLs and demonstrate the ERR_TOO_MANY_REDIRECTS error when it doesn’t find an output.

When this happens, your browser will show an error page like this one.

 

The error can be happen by many different types of reason. It usually occurs when you changes some settings on WordPress core files. Modifying parts of your theme, Plugin conflicting behaviors, or when there’s an issue on your web server.

How To Fix It

To fix this ERR_TOO_MANY_REDIRECTS error I have outlined this in several steps. Such as:

1. Delete Website Cookies
2. Clear WordPress Cache
3. Disable And Re-Activate Plugins
4. Check CDN and HTTPS Settings
5. Check For Server Issues

   1. Delete Website Cookies

If you have corrupted or outdated cookies can in many cases prompt the ERR_TOO_MANY_REDIRECTS error to show up. So it’s best to begin your troubleshooting procedure by clearing out the site cookies put away on your browser.

If you have corrupted or outdated cookies can in many cases prompt the ERR_TOO_MANY_REDIRECTS error to show up. So it’s best to begin your troubleshooting procedure by clearing out the site cookies put away on your browser.

You can erase all cookies from your browser by clearing browser history. If you need to keep the cookies identified with different sites, follow the steps beneath to erase the cookies of a particular site.

Step 1: Copy and paste the following link in your Chrome address bar to navigate to the Cookies section of Chrome settings “chrome://settings/content/cookies”

Step 2: Then choose See All Cookie Data.

Step 3: Search for the website in the Cookie search bar and delete any cookies related to the website.

To delete cookies in Firefox, go to Settings >> Privacy and Security and then choose Manage Data. From the pop-up window, you’ll be able to browse all stored cookies and delete the cookies related to your website.

Also, try clearing the browser cache as well.

   2.Clear WordPress Cache

Some times you will be able to visit WordPress wp-admin dashboard in the reign of ERR_TOO_MANY_REDIRECTS error. If you can login to your wp-admin dashboard, you can fix this error by erasing your WordPress site cache.

The procedure for erasing cache in WordPress caching plugins, including WP Super Cache, WP Rocket, W3 Total Cache and etc. Follow these steps:

 

Step 1: Login to your WordPress dashboard.

Step 2: Then click on the Clear Cache button to delete the cached files.

   3. Disable And Re-Activate Plugins

If you can’t access your WordPress admin dashboard, you can try disabling all the plugins. You can do this in two methods. Such as

• From Cpanel
• From FTP

From Cpanel: Simply login to your cpanel. Navigate to file manager then go to wp-content. And rename the plugins to anything.

From FTP: Simply login to your FTP. Navigate to wp-content. And rename the plugins to anything.

This will disable all of the plugins on your website. Don’t worry, you won’t lose any of your data. Once you have access to your WordPress admin dashboard, you can rename the folder to its default and enable all the plugins one by one until you discover which plugin is causing the issue.

   4. Check CDN and HTTPS Settings

It also can be happened by SSL settings. Most of the time it’s happened by an expired SSL certificate or a misconfigured SSL plugin.

   5. Check For Server Issues

If above methods are unable to fix your issue, now it’s time to check the server.

Most of the time this error can be happened by a corrupted .htaccess file. You need to replace the htaccess with WordPress default htaccess.

Step 1: First, login to your server using an Cpanel or FTP client. You’ll find the .htaccess file on the main folder of your website.

Step 2: Take a backup of .htaccess then click on edit or Rename this file to something else (eg .htaccess-bad).

Step 3: Then create a new .htaccess and paste the code below.

 # BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - 
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php 
</IfModule>
# END WordPress 

This is the default code for the .htaccess file. You can follow the instructions on the codex for more information.

If it doesn’t help contact with your hosting provider. And tell them the issue they will remove apache cache and resolve it for you.

Conclusion

To perform any of the methods I recommend you to back up your wordpress website. Cause in any case something got broken you can have backup and reuse.

Errors come suddenly and give us a lot of stress. Just keep calm and perform the actions carefully to fix this

How to Fix the 500 Internal Server Error in WordPress

Maybe the most confusing WordPress error that an amature may run over is “Internal Server Error”, or now and then “500 Internal Server Error”.

This error generally shows up when there is something incorrectly in the server inside, but the server can’t distinguish where the issue is. Since the error message does not demonstrate where you should search for the error, it is basically up to you to make sense of this.

Why Internal Server Error in causes WordPress?

Internal server error isn’t particular to WordPress. It can occur with any site running on a web server. Because of the non specific nature of this error, it doesn’t provide any clue to the developer or server administrator.

Requesting that how fix an internal server error resembles requesting that you are in hospital for treatment of your illness, but you don’t know where is your illness.

Internal server error in WordPress is often occurs by plugin or theme functions. Other possible reasons of internal server error in WordPress that we know of are: corrupted .htaccess file and PHP memory limit.

We have also seen a lot of people claiming they got internal server error only showing up when they are trying to access the admin area of WordPress while the rest of the site works fine.

Now, Let’s wrap up this thing and let’s troubleshoot the internal server error to see what is the possible reasons and the possible fixes.

1. 1. How to Fix 500 Internal Server Error on WordPress Website
   2. Create a WordPress Backup
   3. The .htaccess File Error Fix
   4. Increase PHP Memory Limit
   5. Theme/Plugins Audit
   6. New wp-admin and wp-content
   7. Hosting Provider

Create a WordPress Backup

You can backup in three ways. Such as:

• Via Cpanel
• Via SFTP
• Via Third-Party Plugin

Via Cpanel

This is so easy you can do it in the time it takes to brew a mug of coffee. Here’s the procedure:

• Login to your web host and navigate to cPanel. For most web hosts, the cPanel is usually the first page you encounter when you login
• Navigate to the File Manager, which should lead you to your public_html or Home directory
• From here, just locate your WordPress directory. This is the folder you want to backup
• Unfortunately, you can’t download the WordPress folder in File Manager without first compressing it. Worry not though, compressing a folder needn’t be challenging
• Click on your WordPress directory, and select Compress from the menu bar. Alternatively, right-click on the folder and choose Compress from the drop-down options menu that appears
• Choose the compression type e.g. ZIP, Tar, GZIP etc from the dialog box that opens. I always go with a ZIP archive
• Then just hit the Compress File(s) button and wait for the process to run its course. Your server will save your compressed WordPress folder
• Click on the archive you just created and choose Download from the menu. Alternatively, right-click on the archive and choose Download.
• Choose a secure location on your hard disk and save your backup
• And that’s it!

The .htaccess File Error Fix

The main thing you ought to do while investigating the internal server error in WordPress is check for the .htaccess file.

You can do as such by renaming your principle .htaccess fileto something like .htaccess_old. To rename the .htaccess file, you should login to your site utilizing FTP or File Manager application in your hosting cPanel dashboard.

When you associated, the .htaccess file will be situated in a similar directory where you will see folders like wp-content, wp-admin, and wp-includes.

When you have renamed the .htaccess file, try to visiting your site to check whether this solved the issue. In the event that it did, at that point give yourself a gesture of congratulations since you fixed the internal server error.

Before you proceed onward with different things, ensure that you go to Settings » Permalinks page in WordPress administrator zone and tap the spare catch without rolling out any changes. This will create another .htaccess file for you with appropriate rewrite rules to guarantee that your post pages don’t return a 404 error.

On the off chance that checking for the .htaccess file arrangement did not work for you, at that point you have to keep perusing this article.

Increasing PHP Memory Limit in WordPress

When a client makes a demand it is dealt with by PHP and triggers a procedure which eventually renders the HTML at client end. PHP memory is allocated to run this procedure. Another method for settling the 500 internal server error is by expanding the PHP Memory Limit. Your host and WordPress set the PHP memory limits by default. When you watch a memory drop, the server consequently shows a 500 internal server error. To stay away from such disparity, just increase the PHP memory limit in WordPress and check whether your site works fine or not.

Probably the most widely recognized methods for increasing a WordPress site’s PHP memory limits is by adjusting the code in one of these files:

• Functions.php File
• .htaccess File
• PHP.ini File
• wp-Config.php File

Functions.php File

• Login to your Cpanel or FTP.
• Navigate like this: wp-content>themes>yourtheme>functions.php
• Add these code at the very bottom of your functions.php:

@ini_set(‘upload_max_size’ , ’64M’);
@ini_set(‘post_max_size’, ’64M’);
@ini_set(‘max_execution_time’, ‘300’);

After this try to visit your website if that is fixed by 500 interval error otherwise continue to other methods which is already described in this post.

.htaccess File

• Navigate to .htaccess and add those following lines of code in that.

php_value upload_max_filesize 64M
php_value post_max_size 64M

After this try to visit your website if that is fixed by 500 interval error otherwise continue to other methods which is already described in this post.

PHP.ini File

If you don’t have any php.ini  file in your file manager then create one through your cpanel or ftp. Then add these lines in your php.ini:

memory_limit = 64M
upload_max_filesize = 64M
post_max_size = 64M
file_uploads = On

After this try to visit your website if that is fixed by 500 interval error otherwise continue to other methods which is already described in this post.

WP-Config File

Open Wp-Config.php file. Under the wp_debug paste those line:

define(‘WP_MEMORY_LIMIT’, ’64M’);
ini_set(‘post_max_size’, ’64M’);
ini_set(‘upload_max_filesize’, ’64M’);

Check your site if the problem is fixed otherwise pursue to the next method.

Theme/Plugins Audit

Corrupted or outdated themes/plugins can cause issues which leads to errors in WordPress website. They are considered as a security risk as if not updated with latest WordPress security patches.

• At first update wordpress core
• Activate a default theme (E.G. Twenty Twelve) then check the site if it is fixed.
• If it doesn’t fix then navigate to the plugins
• Select all and deactivate all plugins then check the site if it s fixed or not.

New wp-admin & wp-includes

If the plugin/theme deactivation doesn’t fix the internal server error, at that point it is worth re-install the wp-admin and wp-includes folder from a fresh WordPress install

This won’t corrupt any of your data, however it might solve the issue on the off chance that any file was corrupted or removed.

• First you will need to visit the WordPress.org website and click on the Download button.
• Connect your site using cpanel or ftp
• Uplaod “wp-admin” and “wp-includes” folder

Ask your Hosting Provider

If all techniques failed to fix internal server error on your website, then it is time to get some more help. Contact your web hosting support and they will be able to check the server logs and locate the main reason of the error.

 

Concluding Thoughts

We hope you discovered this guide accommodating and that you could solve your “WordPress 500 internal server error” issue. Have you made any other method to dispose of this issue? It would be ideal if you share your answers with us in the gave comment area beneath. I am certain, it will be useful for other people, who are confronting this issues.