Title: 500 Server error after update
Last modified: June 18, 2017

---

# 500 Server error after update

 *  [StickyPixels](https://wordpress.org/support/users/stickypixels/)
 * (@stickypixels)
 * [9 years ago](https://wordpress.org/support/topic/500-server-error-after-update-2/)
 * After upgrading to 3.5.16 my dashboard died. Everything looks just fine when 
   visiting the website from ‘outside’, but as soon as I log in I immediately get
   a 500 Server Error, on both the website and the dashboard.
    Had to ftp my old
   version (3.4.37) back to get into dashboard again.
 * What weird voodoo has crept into Customizr?

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

 *  Theme Author [presscustomizr](https://wordpress.org/support/users/nikeo/)
 * (@nikeo)
 * [9 years ago](https://wordpress.org/support/topic/500-server-error-after-update-2/#post-9238551)
 * Hi [@stickypixels](https://wordpress.org/support/users/stickypixels/), we are
   working on a fix for this problem.
    Thank you for reporting it and I apologize
   about this. Best regards
 *  Theme Author [presscustomizr](https://wordpress.org/support/users/nikeo/)
 * (@nikeo)
 * [9 years ago](https://wordpress.org/support/topic/500-server-error-after-update-2/#post-9238879)
 * The problem has been fixed in the latest version.
    Thank you and sorry about 
   this !

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

The topic ‘500 Server error after update’ is closed to new replies.

 * ![](https://i0.wp.com/themes.svn.wordpress.org/customizr/4.4.24/screenshot.png)
 * Customizr
 * [Support Threads](https://wordpress.org/support/theme/customizr/)
 * [Active Topics](https://wordpress.org/support/theme/customizr/active/)
 * [Unresolved Topics](https://wordpress.org/support/theme/customizr/unresolved/)
 * [Reviews](https://wordpress.org/support/theme/customizr/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [presscustomizr](https://wordpress.org/support/users/nikeo/)
 * Last activity: [9 years ago](https://wordpress.org/support/topic/500-server-error-after-update-2/#post-9238879)
 * Status: not resolved