If you cannot connect to external resources (such as GitHub) but your GitHub permissions are correct, use the following procedure to test your SSH key:
In the following commands, replace [/path/to/key] with the full path to your SSH key.
Determine if the encrypted file in your acquia-pipelines.yaml file can access your GitHub repository with the following command:
ssh -i [/path/to/key] -vvv [email protected] The -vvv switch forces verbose output, which can indicate if GitHub accepted your SSH key.
Confirm if your SSH key requires a passphrase because the key is encrypted. Although newer encrypted SSH keys are indistinguishable from non-encrypted keys, use the following command to test older SSH keys:
head -n2 /path/to/keyAfter you execute the command, review its output, which will appear similar to the following:
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED