Title: Causing Server Errors
Last modified: April 10, 2020

---

# Causing Server Errors

 *  Resolved [mylilmule](https://wordpress.org/support/users/mylilmule/)
 * (@mylilmule)
 * [6 years, 1 month ago](https://wordpress.org/support/topic/causing-server-errors/)
 * Ever since the upgrade, I get 500 Server Errors on some of my archived posts 
   or whenever I try and add a new page. It has some good features, but sadly I 
   can’t keep it.

Viewing 1 replies (of 1 total)

 *  Plugin Contributor [James Huff](https://wordpress.org/support/users/macmanx/)
 * (@macmanx)
 * [6 years, 1 month ago](https://wordpress.org/support/topic/causing-server-errors/#post-12657567)
 * Internal server errors (error 500) are often caused by plugin or theme function
   conflicts, so if you have access to your Dashboard, try deactivating all plugins.
   If you don’t have access to your Dashboard, try [manually resetting your plugins](https://wordpress.org/support/article/faq-troubleshooting/#how-to-deactivate-all-plugins-when-not-able-to-access-the-administrative-menus)(
   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 Twenty theme 
   to rule-out a theme-specific issue. If you don’t have access to your Dashboard,
   access your server via [SFTP or FTP](https://wordpress.org/support/article/ftp-clients/),
   or a file manager in your hosting account’s control panel (consult your hosting
   provider’s documentation for specifics on these), 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 specific time 
   period. If you don’t have access to your server error log, ask your hosting provider
   to look for you.

Viewing 1 replies (of 1 total)

The topic ‘Causing Server Errors’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

## Tags

 * [Crashes](https://wordpress.org/support/topic-tag/crashes/)

 * 1 reply
 * 2 participants
 * Last reply from: [James Huff](https://wordpress.org/support/users/macmanx/)
 * Last activity: [6 years, 1 month ago](https://wordpress.org/support/topic/causing-server-errors/#post-12657567)
 * Status: resolved