I am using XAMPP. I'm trying to download a free extension from Magento Connect and I'm getting the following error:

community/ET_*****: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure

  • Not an answer, but a nudge in the right direction. google for the message - this is an issue with ytour server configuration. see: blog.techstacks.com/2010/03/…
    – ProxiBlue
    Commented Feb 21, 2015 at 11:18
  • You can also just manually edit downloader/lib/Mage/HTTP/Client/Curl.php and add “$this->curlOption(CURLOPT_SSL_CIPHER_LIST, ‘TLSv1′);” after “$this->curlOption(CURLOPT_SSL_VERIFYHOST, 2);”
    – aivo
    Commented Feb 21, 2015 at 11:35
  • 1
    @aivo editing core and lib is highly discouraged Commented Feb 21, 2015 at 17:13
  • @ReidBlomquist that would normally be true, but please explain how to write a module that works on downloader/lib/ please? This isn't app/core/ or lib/. Plus editing core and lib is how Magento patches work. They don't back up the patched files so you can revert and the patched files are overwritten, often requiring reapplying the patches over several upgrades to avoid regression failure. Commented Feb 21, 2015 at 18:03
  • It seems that Magento finally got around to Poodle fixes and disabled SSLV3 on Magento Connect. But in a left-hand, right-hand disconnect type thing, forgot that the downloader/ software they provide has SSLV3 hardcoded into some curl requests it uses and didn't provide a patch. Commented Feb 21, 2015 at 18:05

2 Answers 2


This is our problem. Magento Connect has different hardware. Please wait a bit and we'll get it sorted.


This is because Magento now blocks SSLv3 on their servers, but Magento downloader (./mage as well), using curl tries to use SSLv3. Here is a blog post that solves this issue along with a patch file. https://www.dwdonline.com/blog/fix-magento-error14077410ssl-routinesssl23_get_server_hellosslv3-alert-handshake-failure.html

This will fix the issue and allow you to install all extensions again. And no, it's actually because your server is configured properly - but Magento downloader isn't.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.