Skip to content

How to Fix WordPress Internal Server Error

How to fix internal server error on WordPress. This happens to all of us.

We all hate it. And this is not just an issue with beginners. With these solutions, you would be able to fix your site without losing your hair.

WordPress Internal Server Error

Please note that this will require you to have access to your server or your hosting package server.

Here are some of the troubleshooting tactics.

It’s usually the .htaccess file that is corrupted. Here’s how you can resolve the problem.

  • Rename the current .htaccess file to something else
  • For this, use the File Manager app in your web hosting account’s dashboard
  • Locate the file, right click it, select the option to edit or rename, and change the name. Name it to something like ‘.htaccess-old’
  • Revisit your WordPress website and see if the problem is solved
  • If it is solved, go to Settings > Permalink and click ‘Save’ without making any changes here
  • This action will generate a new .htaccess file

If the above did not work, you may need to increase PHP memory limit. Here are some steps you can try to fix this error.

  • Make a blank file named php.ini with either Notepad or your code editor of choice.
  • Type in this code in the file
    memory=64MB (You could increase it to 256 if you want)
  • Save the file
  • Upload the file to your website’s /wp-admin/ folder. You can do so using FTP or just drag and drop it onto your server.

If you receive a message that explicitly states a PHP memory limit related error, then the above steps will be very useful.


It is either an issue with your .htaccess file or your php memory limit. But…there is another culprit that could be causing this…a plugin conflict that changes the .htaccess file details. If you are not sure what your .htaccess file should look like normally, here is an example of a default one:

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

I hope this helps you. If you found other methods of resolving the issue, please let me know in the comments below.

Join to get updates

Similar Posts

What is a Landing Page?

Many times a web-developer or a business is faced with making the decision to create a landing page. But what is it and why create one?

Read More »
API Link chain

What Is An API

Have you ever wondered what API really means and what it’s supposed to do? Find out in this post.

Read More »
No more posts to show