Title: Internal Server Error
Last modified: August 31, 2016

---

# Internal Server Error

 *  [smartedge](https://wordpress.org/support/users/smartedge/)
 * (@smartedge)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-398/)
 * Hello,
 * We are having the below error on our website . We noticed that each time we experience
   this issue our CPU and memory resources on our c panel get used up.
 * We have escalated this issue to our web host and they told just to upgrade to
   an higher plan with more memory and CPU resources .
 * We experiencing this issue again after the upgrade and i will like to know how
   i can figure out exactly what is causing all our resources to be used up.
 * i will appreciate your assistance .
 * Regards,
    Olumide.
 * Internal Server Error
 * The server encountered an internal error or misconfiguration and was unable to
   complete your request.
 * Please contact the server administrator at [webmaster@smartedgebusiness.com](https://wordpress.org/support/topic/internal-server-error-398/webmaster@smartedgebusiness.com?output_format=md)
   to inform them of the time this error occurred, and the actions you performed
   just before this error.
 * More information about this error may be available in the server error log.
 * Additionally, a 500 Internal Server Error error was encountered while trying 
   to use an ErrorDocument to handle the request.

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Moderator [James Huff](https://wordpress.org/support/users/macmanx/)
 * (@macmanx)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-398/#post-7167496)
 * Internal server errors (error 500) are often caused by plugin or theme function
   conflicts, so if you have access to your admin panel, try deactivating all plugins.
   If you don’t have access to your admin panel, try [manually resetting your plugins](https://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F)(
   no Dashboard access required). If that resolves the issue, reactivate each one
   individually until you find the cause.
 * If that does not resolve the issue, try switching to the Twenty Sixteen theme
   to rule-out a theme-specific issue. If you don’t have access to your admin panel,
   access your server via [SFTP or FTP](https://codex.wordpress.org/FTP_Clients),
   or a file manager in your hosting account’s control panel, navigate to `/wp-content/
   themes/` and rename the directory of your currently active theme. This will force
   the default theme to activate and hopefully rule-out a theme-specific issue.
 * If that does not resolve the issue, it’s possible that a `.htaccess` rule could
   be the source of the problem. To check for this, access your server via SFTP 
   or FTP, or a file manager in your hosting account’s control panel, and rename
   the `.htaccess` file. If you can’t find a `.htaccess` file, make sure that you
   have set your SFTP or FTP client to view invisible files.
 * If you weren’t able to resolve the issue by either resetting your plugins and
   theme or renaming your .htaccess file, we may be able to help, but we’ll need
   a more detailed error message. Internal server errors are usually described in
   more detail in the server error log. If you have access to your server error 
   log, generate the error again, note the date and time, then immediately check
   your server error log for any errors that occurred during that time period. If
   you don’t have access to your server error log, ask your hosting provider to 
   look for you.
 *  Thread Starter [smartedge](https://wordpress.org/support/users/smartedge/)
 * (@smartedge)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-398/#post-7167548)
 * Hello,
 * Thanks for the hint. Below is the error log from our Cpanel .Can you advice on
   what we need to fix ?.
 * [full day’s error log removed]
 *  Moderator [James Huff](https://wordpress.org/support/users/macmanx/)
 * (@macmanx)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-398/#post-7167597)
 * That log is much too broad, it’s impossible to tell which one is causing the 
   Internal Server Error.
 * You need to view the error in your browser, note the date and time, then check
   the log for the error at that specific date and time.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Internal Server Error’ is closed to new replies.

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 3 replies
 * 2 participants
 * Last reply from: [James Huff](https://wordpress.org/support/users/macmanx/)
 * Last activity: [10 years, 2 months ago](https://wordpress.org/support/topic/internal-server-error-398/#post-7167597)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics