Title: Warning: session_start(): Cannot find save handler &#039;memcache&#039; &#8211; session startup
Last modified: August 31, 2016

---

# Warning: session_start(): Cannot find save handler 'memcache' – session startup

 *  Resolved [giwrgos88](https://wordpress.org/support/users/giwrgos88/)
 * (@giwrgos88)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/warning-session_start-cannot-find-save-handler-memcache-session-startup/)
 * Hello, I’m having an issue when changing the php version of my server from 5.4
   to 5.6 even to 7. When I’m changing the version and visiting the wp-admin I’m
   getting the following error messages
 * Warning: session_start(): Cannot find save handler ‘memcache’ – session startup
   failed in /var/sites/*****/****/public_html/wp-content/plugins/custom-sidebars/
   inc/external/wpmu-lib/functions-wpmulib.php on line 69
 * Warning: session_start(): Cannot find save handler ‘memcache’ – session startup
   failed in /var/sites/*/******/public_html/wp-content/plugins/custom-sidebars/
   inc/class-custom-sidebars-explain.php on line 55
 * Then when I’m chancing back the version to 5.4 the warning disappeared.
    I have
   spoke with the server admin and told me that memcache is enable on the server.
 * Can anyone help me?
 * [https://wordpress.org/plugins/custom-sidebars/](https://wordpress.org/plugins/custom-sidebars/)

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

 *  [Bojan Radonic – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support4/)
 * (@wpmudev-support4)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/warning-session_start-cannot-find-save-handler-memcache-session-startup/#post-7181226)
 * Hey there giwrgos88,
 * How are you doing today?
 * You’re probably using memcache for session storage so it’s quite possible that
   there is a wrong settings in you php.ini file, this is a common error.
 * Please check the php.ini file or have your hosting provider to that for you and
   check if you have the following there:
 * session.save_handler = memcache
 * this will cause the problem, the correct value should be “memcached” (with d 
   in the end).
 * Hope this helps 🙂
 * Cheers,
    Bojan
 *  Thread Starter [giwrgos88](https://wordpress.org/support/users/giwrgos88/)
 * (@giwrgos88)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/warning-session_start-cannot-find-save-handler-memcache-session-startup/#post-7181229)
 * I’m doing well,how about you? I will try to correct it, thanks a lot
 *  [Bojan Radonic – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support4/)
 * (@wpmudev-support4)
 * [10 years, 2 months ago](https://wordpress.org/support/topic/warning-session_start-cannot-find-save-handler-memcache-session-startup/#post-7181230)
 * I’m doing great, thanks for asking 🙂
 * Please let me know how that goes!
 * cheers,
    Bojan

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

The topic ‘Warning: session_start(): Cannot find save handler 'memcache' – session
startup’ is closed to new replies.

 * ![](https://ps.w.org/custom-sidebars/assets/icon-256x256.png?rev=1414065)
 * [Custom Sidebars - Dynamic Sidebar Classic Widget Area Manager](https://wordpress.org/plugins/custom-sidebars/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/custom-sidebars/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/custom-sidebars/)
 * [Active Topics](https://wordpress.org/support/plugin/custom-sidebars/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/custom-sidebars/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/custom-sidebars/reviews/)

## Tags

 * [memcache](https://wordpress.org/support/topic-tag/memcache/)
 * [session_start](https://wordpress.org/support/topic-tag/session_start/)

 * 3 replies
 * 2 participants
 * Last reply from: [Bojan Radonic – WPMU DEV Support](https://wordpress.org/support/users/wpmudev-support4/)
 * Last activity: [10 years, 2 months ago](https://wordpress.org/support/topic/warning-session_start-cannot-find-save-handler-memcache-session-startup/#post-7181230)
 * Status: resolved