cancel
Showing results for 
Search instead for 
Did you mean: 

Stuck during installing extension

Stuck during installing extension

I'm having issue installing extensinon.  My Magento version is 1.9.1.0.  I copid and paste the extension key and click Install, but it wouldn't go any further.  It got timeout while the following message:

Operation timed out after 0 milliseconds with 0 out of 0 bytes received

Unknown SSL protocol error in connection to connect20.magentocommerce.com:443

 

How do I resolve this?  It's was working fine before.

 

Shawn

18 REPLIES 18

Re: Stuck during installing extension

Hello @saltyfish 

 

Do you know use of FTP for the extension installation? Try that,

Was my answer helpful? You can accept it as a solution.
200+ Premium Magento 2 Extensions Need help? Hire Magento Developer

Re: Stuck during installing extension

Did you select Magento Connect 1.0 or Magento Connect 2.0? I always seem to have to use 2.0.

Re: Stuck during installing extension

Magento Connect Manager ver. 1.9.1.1

When I use command line to add channel:

 

./mage mage-setup .

 

Running initial setup...
Success
Success
Error:
channel-add: Unknown SSL protocol error in connection to connect20.magentocommerce.com:443

 

Anyone can help me?

Re: Stuck during installing extension

This could be related to the version of curl on your server. If it's a version newer than 7.33.0-3, it's worth asking your server to try downgrading it.

Re: Stuck during installing extension

I have same problem with any extension i try to install. Any solutions yet?

Re: Stuck during installing extension

Hello,
You are using authentication on your server (apache or NGINX)?
If so, disable authentication and try again.

Re: Stuck during installing extension

i have an error when i install extensions this is "Unknown SSL protocol error in connection to connect20.magentocommerce.com:443 "what can i do  "

Re: Stuck during installing extension

Hi,

 

Same problem too ...

 

 

Re: Stuck during installing extension

What PHP version are you running? I had this same issue as the server was running 5.3. I upgraded this to 5.6 and it solved the issue.