cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade v2.1.9 to v.2.2.0

   Did you know you can see the translated content as per your choice?

Translation is in progress. Please check again after few minutes.

Upgrade v2.1.9 to v.2.2.0

I wanted upgrade my magento v2.1.9 to 2.2.0 but there is a little issue.

 

i run this command in my ssl consol : ( i'm on OVH HOST ) so

php composer.phar require magento/product-community-edition 2.2.0 --no-update
php composer.phar update

and after this there is two line :

Loading composer repositories with package information

                                                                                                                        
  [Composer\Downloader\TransportException]                                                                              
  The "https://repo.magento.com/packages.json" file could not be downloaded: failed to open stream: Connection refused  

so i tried to insert my credentials in magento admin, but when i saved i have this issue :

Unknown SSL protocol error in connection to repo.magento.com:443 

I'm completely lost. do you have an idea to help me ?

thanks.

3 REPLIES 3

Re: Upgrade v2.1.9 to v.2.2.0

Hi @fredeviviand,

 

I'm not sure if there is a relation but there are another users saying they have issues trying to perform upgrdes.

Is this issue still happening for you?

Re: Upgrade v2.1.9 to v.2.2.0

Yes, i'm still in Magento 2.1.9 .

I can't upgrade, i always have this error.

php composer.phar require magento/product-community-edition 2.2.0 --no-update
php composer.phar update

//ERROR
[Composer\Downloader\TransportException]                                                                              
  The "https://repo.magento.com/packages.json" file could not be downloaded: failed to open stream: Connection refused

 

Do you have an idea ?

Re: Upgrade v2.1.9 to v.2.2.0

No, no idea at all.

I was investigating a little bit and I've found similiar issues related with certificates and php versions (and not a problem with Magento itself...)

Sorry, I'm out of ideas.