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:

1. Determine if the encrypted file in your acquia-pipelines.yaml file can access your GitHub repository with the following command:

   copy

   ssh -i [/path/to/key] -vvv [email protected]                                                                                                                                           

   The -vvv switch forces verbose output, which can indicate if GitHub accepted your SSH key.

2. 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:

   copy

   head -n2 /path/to/key

   After you execute the command, review its output, which will appear similar to the following:

   copy

   -----BEGIN RSA PRIVATE KEY-----
   Proc-Type: 4,ENCRYPTED