Replies: 2 comments 1 reply
-
Do that. |
Beta Was this translation helpful? Give feedback.
-
I created an account in GitHub and then created a Token. I added the token, it accepted but it gave an the following error: `Cloning failed using an ssh key for authentication, enter your GitHub credentials to access private repos From /home/snipeitapp/.cache/composer/vcs/https---github.com-symfony-service-contracts |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm encountering an issue while upgrading Snipe-IT on my server. The upgrade process runs smoothly until it reaches the Composer dependency update step, where it fails due to a GitHub authentication issue. Here’s the output I’m seeing. Could you please help me to solve this problem?
System Information:
Current Snipe-IT Version: 7.1.16
PHP Version: 8.3.17
OS: Ubuntu 22.04
`snipeitapp@asset:/var/www/snipeit$ php upgrade.php
WELCOME TO THE SNIPE-IT UPGRADER!
This script will attempt to:
Launching using branch: master
Found PHP requirements, will check for PHP > 8.2.0 and < 8.5.0
Proceed with upgrade? [y/N]: y
STEP 1: Checking .env file:
--------------------------------------------------------\n
√ Your APP_KEY is not blank.
√ Your APP_URL is not null or blank. It is set to http://vasset.vepro.com
√ Your APP_URL is set to http://vasset.vepro.com and starts with the protocol (https:// or http://)
√ Your APP_URL (http://vasset.vepro.com) does not have a trailing slash.
STEP 2: Checking PHP requirements: (Required PHP >=8.2.0 - <8.5.0)
√ Current PHP version: (8.3.17) is at least 8.2.0 and less than 8.5.0! Continuing...
FYI: The php.ini used by this PHP is: /etc/php/8.3/cli/php.ini
Checking Required PHP extensions...
√ bcmath is installed!
√ curl is installed!
√ exif is installed!
√ fileinfo is installed!
√ gd is installed!
√ json is installed!
√ ldap is installed!
√ mbstring is installed!
√ mysqli is installed!
√ openssl is installed!
√ PDO is installed!
√ sodium is installed!
√ tokenizer is installed!
√ xml is installed!
√ zip is installed!
STEP 3: Checking directory permissions:
√ /var/www/snipeit/bootstrap/cache is writable
√ /var/www/snipeit/storage is writable
√ /var/www/snipeit/storage/logs is writable
√ /var/www/snipeit/storage/logs/laravel.log is writable
√ /var/www/snipeit/storage/framework is writable
√ /var/www/snipeit/storage/framework/cache is writable
√ /var/www/snipeit/storage/framework/sessions is writable
√ /var/www/snipeit/storage/framework/views is writable
√ /var/www/snipeit/storage/app is writable
√ /var/www/snipeit/storage/app/backups is writable
√ /var/www/snipeit/storage/app/backup-temp is writable
√ /var/www/snipeit/storage/private_uploads is writable
√ /var/www/snipeit/public/uploads is writable
STEP 4: Pulling latest from Git (master branch):
Git is installed.
Already on 'master'
-- No local changes to save
-- Your branch is up to date with 'origin/master'.
-- Already up to date.
STEP 5: Cleaning up old cached files:
√ No bootstrap/cache/compiled.php, so nothing to delete.
√ Deleting bootstrap/cache/services.php. It is no longer used.
√ No bootstrap/cache/config.php, so nothing to delete.
√ No vendor/symfony/translation/TranslatorInterface.php, so nothing to delete.
STEP 6: Updating composer dependencies:
(This may take a moment.)
-- Running the app in production mode.
√ Local composer.phar detected, so we'll use that.
-- Updating local composer.phar
You are already using the latest available Composer version 2.8.6 (stable channel).
Installing dependencies from lock file
Verifying lock file contents can be installed on current platform.
Package operations: 2 installs, 62 updates, 0 removals
0 [>---------------------------] 0 [->--------------------------]
Cloning failed using an ssh key for authentication, enter your GitHub credentials to access private repos
When working with public GitHub repositories only, head here to retrieve a token:
https://github.com/settings/tokens/new?scopes=&description=Composer+on+vasset+2025-03-04+0853
This token will have read-only permission for public information only.
When you need to access private GitHub repositories as well, go to:
https://github.com/settings/tokens/new?scopes=repo&description=Composer+on+vasset+2025-03-04+0853
Note that such tokens have broad read/write permissions on your behalf, even if not needed by Composer.
Tokens will be stored in plain text in "/home/snipeitapp/.config/composer/auth.json" for future use by Composer.
For additional information, check https://getcomposer.org/doc/articles/authentication-for-private-packages.md#github-oauth
Token (hidden):`
Beta Was this translation helpful? Give feedback.
All reactions