Could not read from remote repository. Please make sure you have the correct access rights

[jasperf]

Never had this before

[staging]  error  in update_code.php on line 90:
[staging] run cd ~/staging.site.com/.dep/repo && (/usr/bin/git remote update 2>&1)
[staging] err mesg: ttyname failed: Inappropriate ioctl for device
[staging] Fetching origin
[staging] Host key verification failed.
[staging] fatal: Could not read from remote repository.
[staging] Please make sure you have the correct access rights
[staging] and the repository exists.
[staging] error: Could not fetch origin
[staging] exit code 1 (General error)

We normally grab latest code from Github and update server.

I tried git_tty: true inj deploy.ymland

Host staging.app.com
  UserKnownHostsFile /dev/null
  IdentityFile ~/.ssh/id_rsa
  StrictHostKeyChecking no
  ForwardAgent yes

in ~/.ssh/config but still got

[staging] err mesg: ttyname failed: Inappropriate ioctl for device
[staging] Fetching origin
[staging] Host key verification failed.
[staging] fatal: Could not read from remote repository.
[staging] Please make sure you have the correct access rights
[staging] and the repository exists.
[staging] error: Could not fetch origin
[staging] exit code 1 (General error)
task deploy:failed
task deploy:unlock

also all my releases were wiped!

ll
total 20
drwxrwxr-x  5 forge forge 4096 Nov 17 11:20 ./
drwxr-xr-x 12 forge forge 4096 Nov 17 11:04 ../
drwxrwxr-x  3 forge forge 4096 Nov 17 11:20 .dep/
lrwxrwxrwx  1 forge forge   10 Nov 16 07:11 current -> releases/9/
lrwxrwxrwx  1 forge forge   11 Nov 17 11:20 release -> releases/13/
drwxrwxr-x 12 forge forge 4096 Nov 17 11:20 releases/
drwxrwxr-x  5 forge forge 4096 Nov 17 11:04 shared/

and

release$ ll
total 8
drwxrwxr-x  2 forge forge 4096 Nov 17 11:20 ./
drwxrwxr-x 12 forge forge 4096 Nov 17 11:20 ../

@antonmedv What to do?

here full deploy.yml:

import:
  - recipe/laravel.php
  - contrib/php-fpm.php
  - contrib/npm.php

config:
  application: 'site-app'
  remote_user: forge
  deploy_path: '~/{{hostname}}'
  repository: '[email protected]:site/site-app.git'
  php_fpm_version: '8.0'
  keep_releases: '10'
  shared_files: 
    - '.env'
    - '.transip_private_key'
    - 'storage/app/exact.api.json'
  shared_dirs:
    - 'bootstrap/cache'
    - 'public/uploads'
    - 'public/published'
    - 'storage/framework/cache'
    - 'storage/framework/sessions'
    - 'storage/framework/views'
    - 'storage/logs'
    - 'storage/tls'
    - 'storage/app/public'
    - 'storage/app/modules'
  writable_dirs:
    - 'public/uploads'
    - 'public/published'
    - 'storage/framework/cache/data'
    - 'storage/logs'
    - 'storage/tls'
    - 'storage/app/public'
    - 'storage/app/modules'

hosts:
  prod:
    hostname: 'site.com'
  staging:
    hostname: 'staging.site.com'

tasks:
  deploy:
    - deploy:prepare
    - deploy:vendors
    - artisan:storage:link
    - artisan:view:cache
    - artisan:config:cache
    - artisan:optimize
    - artisan:migrate
    - artisan:queue:restart    
    - artisan:horizon:terminate
    - deploy:publish

after:
  deploy:symlink: php-fpm:reload
  deploy:failed: deploy:unlock

Could have sworn we used agent forwarding before. Not sure what the issue is now failing all and deleting all releases.

Did try

git_tty: true
 ssh_type: native

no dice either and still: [staging] err mesg: ttyname failed: Inappropriate ioctl for device

Read #2641 but no proper solution there yet.

[msplu]

Hi, have you tested your SSH connection with github on your staging server?

[jasperf]

and when one more time

ssh -T [email protected]
Warning: the ECDSA host key for 'github.com' differs from the key for the IP address '140.82.121.4'
Offending key for IP in /home/forge/.ssh/known_hosts:18
Matching host key in /home/forge/.ssh/known_hosts:31

so perhaps I need to remove the key on line 18 @msplu ?

[msplu]

Ok also remove 140.82.121.4 please and retry

[jasperf]

Does seem to work

ssh -T [email protected]
Warning: Permanently added the ECDSA host key for IP address '140.82.121.4' to the list of known hosts.
Hi jasperf! You've successfully authenticated, but GitHub does not provide shell access.
forge@app-staging:~/staging.site.com/current$ ssh -T [email protected]
Hi jasperf! You've successfully authenticated, but GitHub does not provide shell access.

so will try another deployment. Do not understand why the releases were deleted though.

[jasperf]

Hmm @msplu thank you very much for your help!

I was able to deploy. Only now I see release 16 besides all the others that end at 9 which is odd:

rwxrwxr-x  5 forge forge 4096 Nov 17 12:03 ./
drwxr-xr-x 12 forge forge 4096 Nov 17 12:00 ../
drwxrwxr-x  3 forge forge 4096 Nov 17 12:03 .dep/
lrwxrwxrwx  1 forge forge   11 Nov 17 12:01 current -> releases/16/
drwxrwxr-x 12 forge forge 4096 Nov 17 12:01 releases/
drwxrwxr-x  5 forge forge 4096 Nov 17 11:04 shared/
forge@app-staging:~/staging.sitecom$ cd releases/
forge@app-staging:~/staging.site.com/releases$ ll
total 48
drwxrwxr-x 12 forge forge 4096 Nov 17 12:01 ./
drwxrwxr-x  5 forge forge 4096 Nov 17 12:03 ../
drwxrwxr-x 15 forge forge 4096 Oct 23 07:23 1/
drwxrwxr-x 15 forge forge 4096 Nov 17 12:02 16/
drwxrwxr-x 15 forge forge 4096 Oct 23 09:42 2/
drwxrwxr-x 15 forge forge 4096 Nov  3 07:29 3/
drwxrwxr-x 15 forge forge 4096 Nov  3 08:45 4/
drwxrwxr-x 15 forge forge 4096 Nov  6 09:21 5/
drwxrwxr-x 15 forge forge 4096 Nov  6 09:32 6/
drwxrwxr-x 15 forge forge 4096 Nov  8 10:21 7/
drwxrwxr-x 15 forge forge 4096 Nov 15 07:51 8/
drwxrwxr-x 15 forge forge 4096 Nov 16 07:12 9/

Will also check production for possible Github connectivity issues briefly now.

[jasperf]

Hmm , production no such conflicts:

ssh -T [email protected]
Hi jasperf! You've successfully authenticated, but GitHub does not provide shell access.

Odd but glad about that.

[jasperf]

@msplu FYI Production I just now also had the same issue:

[prod]  error  in update_code.php on line 90:
[prod] run cd ~/site.com/.dep/repo && (/usr/bin/git remote update 2>&1)
[prod] Fetching origin
[prod] Host key verification failed.
[prod] fatal: Could not read from remote repository.
[prod] Please make sure you have the correct access rights
[prod] and the repository exists.
[prod] error: Could not fetch origin
[prod] exit code 1 (General error)

So again did something similar. I removed the offending key. Then I did ssh-keygen -R 140.82.121.3, was told key was not there. Next I did ssh -T [email protected] and added key:

ssh -T [email protected]
Warning: Permanently added the ECDSA host key for IP address '140.82.121.3' to the list of known hosts.
Hi jasperf! You've successfully authenticated, but GitHub does not provide shell access.

Once I did that I could deploy again with agent forwarding:

forge@app-prod-w-2:~/site.com/releases$ ll
total 28
drwxrwxr-x  7 forge forge 4096 Nov 19 04:38 ./
drwxrwxr-x  5 forge forge 4096 Nov 19 04:40 ../
drwxrwxr-x 15 forge forge 4096 Oct 25 10:08 1/
drwxrwxr-x 15 forge forge 4096 Nov  5 03:03 2/
drwxrwxr-x 15 forge forge 4096 Nov 16 05:02 3/
drwxrwxr-x 15 forge forge 4096 Nov 16 08:30 4/
drwxrwxr-x 15 forge forge 4096 Nov 19 04:40 6/
forge@app-prod-w-2:~/site.com/releases$ date
Fri Nov 19 04:44:03 CET 2021

again one release skipped but because I knew what to do I did not do several failed attempts.

Do start to wonder if a deploy key is better...