cancel
Showing results for 
Search instead for 
Did you mean: 

Error running composer install

Error running composer install

I added my access key to auth.json and executed composer install and I receive the following error after it appears to complete to 100%:

 

The "https://repo.magento.com/archives/magento/ringphp/magento-ringphp-1.0.0.0-beta106.zip" file could not be downloaded (HTTP/2 404 ):
"This might just be a temporary issue, please try again in a moment. If the problem persists, please contact your Adobe Account Manager to confirm that your license entitlement has not expired."

 

Any help would be greatly appreciated.

 

3 REPLIES 3

Re: Error running composer install

It looks like you are trying to install magento/ringphp/magento-ringphp.
However, when I searched for the vendor ringphp, I couldn't find any results on Adobe Marketplace or Google.
Could you provide me with more information about this extension or vendor?

Regarding the message you received, I think the file may no longer exist. You can try removing the package information from composer.lock.


composer.lock
Then run 

composer clear-cache
composer require  ringphp/magento-ringphp

 

 

In addition, to install extensions from the Magento repository, make sure you have added the username and password in auth.json.

 

{
  "http-basic": {
    "repo.magento.com": {
      "username": "6740f88b3e493a2905a36450711b4214",
      "password": "*******************************"
    }
  }
}




Mageplaza | Top-Rated Magento Extension and Solution Provider


Should you have any questions or concerns, feel free to contact us via consultant@mageplaza.com

Re: Error running composer install

This is what I am facing still as well. Though, I could not find the the exact solution for it. But one of my friend is using and installing it with ease. 

Re: Error running composer install

Hello @lavoiee2017,

The error you're encountering when running composer install—specifically the HTTP/2 404 error for a package like magento/ringphp—suggests an issue with accessing the Magento repository (repo.magento.com).

This can happen for several reasons, such as incorrect authentication, an expired license, a temporary glitch with the repo, or a mismatch in your setup. Since you’ve already added your access keys to auth.json.


Verify Your auth.json Credentials

Even though you’ve added your keys, a small typo or misplacement could cause the 404 error. Magento requires valid public and private keys from your Adobe Commerce (Magento) Marketplace account.

 

  • Check Format: Your auth.json should look like this (typically located in your Magento root directory or ~/.composer/):
{

  "http-basic": {

    "repo.magento.com": {

      "username": "<your-public-key>",

      "password": "<your-private-key>"

    }

  }

}


Replace <your-public-key> and <your-private-key> with the keys from your Magento Marketplace account (find them under My Profile > Access Keys).

 

Double-check there are no extra spaces, quotes, or typos. If unsure, regenerate new keys on the Marketplace, update auth.json, and save.

 

The error message hints at a potential license issue: "contact your Adobe Account Manager to confirm that your license entitlement has not expired." This is common with Adobe Commerce (Enterprise) editions, less so with Open Source.


Are you using Magento Open Source or Adobe Commerce (Enterprise/Cloud)? If it’s the latter, your organization’s license might have lapsed, affecting repo access.

 

For Open Source: The keys should work indefinitely unless revoked. Try generating a new pair on marketplace.magento.com.

 

For Enterprise/Cloud: Contact your Adobe Account Manager or check your account status on the Adobe Commerce portal to ensure your license is active.

 

The 404 for magento/ringphp-1.0.0.0-beta106.zip might indicate that this specific version isn’t available anymore, or your composer.json is requesting an outdated or unavailable package.

If it’s an old version, update your composer.json to use a newer Magento version or compatible dependency:

 

composer require magento/product-community-edition:<latest-version> --update-with-dependencies.

 

If the issue is resolved, click Kudos and accept it as a solution.