Magento2 Composer install is not working. I'm getting an error when installing the composer in an existing project:
You need valid credentials from your Amasty account. It could be that the credentials you're using have expired..
Log into your Amasty account to check, and make sure you've added your amasty keys to auth.json
Related
When installing Backpack for Laravel's PRO add-on, I have the token, I followed all the steps, but after composer require backpack/pro it errors:
Downloading backpack/pro (1.1.1)
Failed to download backpack/pro from dist: The "https://backpackforlaravel.com/satis/download/dist/backpack/pro/backpack-pro-xxx-zip-zzz.zip" file could not be downloaded (HTTP/2 402 )
And then:
Syncing backpack/pro (1.1.1) into cache
Cloning failed using an ssh key for authentication, enter your GitHub credentials to access private repos
Head to https://github.com/settings/tokens/new?scopes=repo&description=Composer+on+DESKTOP-BLABLA+2022-07-14+1559
to retrieve a token.
What did I do wrong? How can I install it?
That is a general Composer error - "file could not be downloaded". The error itself doesn't give too much information, but we can make an educated guess.
99% of the people who report this error have the same problem - they do not have access to that package version. They bought updates until 1.0.13 (for example), so they DO NOT have access to the latest version (1.1.1 in this example). What you can do, in that case, is lock the installation to the latest you have access to, for example
composer require backpack/pro:"1.0.13"
Alternatively, you can purchase more access on the Backpack website. Or contact the team if there's a mistake.
--
How do you find out what's the last version you have access to?
(1) Whenever the error above happens, Backpack will send you an email, with details and instructions. Check your email, it will also include the latest version you have access to.
(2) Your Tokens page will show more details. For each token you have, it will say when it stops giving you access to updates. If it doesn't say the last version directly, you can corroborate that last day with the changelog, to determine what's the last version that you have access to.
--
Why the ugly, general error? Because Composer doesn't allow vendors to customize the error, unfortunately. Backpack's server returns a better error message, but Composer doesn't show it.
Trying to send email using Jenkins- using the email notification plugin, using ssl option.
Initially was getting bad id/pwd error- also got login blocked alert emails from google.
So enabled the less secure apps. The error changed to javax.mail.AuthenticationFailedException: 534-5.7.14
I do not have 2-step auth enabled in gmail.
Read a couple of posts here suggesting - need to use 2-step auth method with gmail - is that the way to go?
How do I install older plugin?
I downloaded the older Mailer plugin 1.23 (wget) it is a .hpi file. But in my plug folder only has jpi files. What it is supposed to be?
Do I just go to the console and uninstall the current plugin and just copy this hpi file to /plugins folder?
Able to install the .hpi finally
Advanced installation
The Update Center only allows the installation of the most recently released version of a plugin. In cases where an older release of the plugin is desired, a Jenkins administrator can download an older .hpi archive and manually install that on the Jenkins master.
From the web UI
Assuming a .hpi file has been downloaded, a logged-in Jenkins administrator may upload the file from within the web UI:
Navigate to the Manage Jenkins > Manage Plugins page in the web UI.
Click on the Advanced tab.
Choose the .hpi file under the Upload Plugin section.
Upload the plugin file.
After uploading .hpi from local system using the GUI) - the Mailer plugin version shows the new older Mailer version 1.23. But you have to reconfigure it.
But still same error:
javax.mail.AuthenticationFailedException: 534-5.7.14
support.google.com/mail/answer/78754 q128sm12098788pga.24 - gsmtp. checking the google support link - I think am doing everything as suggested
I'm trying to deploy using firebase 3.0.0 latest CLI version.
Unfortunately I get this errors:
Error: Unable to authorize access to project XXXX
Note: This version of the Firebase CLI is only compatible with projects upgraded
to the new Firebase Console. To access firebase.com apps, you will need to
use a previous version: npm install -g firebase-tools#^2.1
Any ideas?
As a matter of fact I was trying to deploy to a custom domain that was not yet verified.
My bad :(
Sorry guys.
I believe you need to upgrade your project to the new Firebase at firebase.google.com. If you haven't you should check out the announcements at Google I/O 2016.
I am getting the error as could not find file while trying to install from main menu help and install new software and adding the appropriate site.
Please check if you are using proxy and if the proxy details are correct. if it fails even with correct proxy. You can try offline install
https://docs.jboss.org/author/display/SWITCHYARD/Installing+Eclipse+Tooling
In magento application , when i click on magento connect
it will goes to error page with url as :
http://mysite.com/downloader/?return=http%3A%2F%2Fmysite.com%2Findex.php%2Fadmin%2F
How to overcome this issues?.
After an upgrade of Fishpig / Magento WordPress Integration I was unable to access Magento connect Manager for about 2 months. I had to uninstall it through FTP (download the extension to get information about every file and folder in your Magento installation.)
After removing FishPig you will see a scary error but do not worry as you can just clean the cache using agento-cleanup.php.