This article walks you through troubleshooting some of the most common Git issues on Pagoda Box.
Confirm Correct Key in Pagoda Account
The first thing you'll want to check is that the SSH key you've added to your Pagoda Box account matches the contents of ~/.ssh/id_rsa.pub exactly.
Also ensure that there are no hard returns in the key.
Next you'll want to test your connection with our GIT server.
If you don't get the above success message, run this command to see what information GIT is trying to use to connect.
TerminalSSH Debug Info
From the results, check the following items:
- Trying correct server (git.pagodabox.com)
- Trying correct port (22)
- Trying correct key files(.ssh/identity, id_rsa, & id_dsa)
Most issues are related to your key files. If you're getting a "Permission denied (publickey)" error when you try to push to the pagoda repo, its likely due to SSH not being able to find your keys because they're not in the default location. The following are possible reasons that would occur.
SSH Keys Generated Using Different User
Keep in mind that SSH keys are user specific. If you generated keys using "sudo ssh-keygen", then those keys will only be available to sudo. So you can either run all your GIT commands as sudo(not recommended) or regenerate SSH keys for your user and paste the new public key(id_rsa.pub) into your Pagoda Box account.
SSH Keys in Non-Default Location or using Non-Default Name
If your key is not at the default location(~/.ssh/) or it's using a Non-Default Name(id_rsa), move/rename it or run the following command to make SSH aware of it's existence.
TerminalAdd SSH Key Path
If your Pagoda Box authentication information is different from your machine account information, you’ll need to modify your SSH configuration file(~/.ssh/config).
You may also need to update the permissions on your .ssh folder and its contents. The SSH application will ignore secret files that are too permissive.