Check your environment
If your environment is inactive or the deployment has failed, you can’t log in to it. To make sure the environment is active and the deployment has succeeded, check it usingupsun environment:list or in the Console .
Redeploy your environment
If you have just added your SSH key or made changes to access rules, you need to redeploy your environment before you can access it using SSH keys. You can do this in the Console, by runningupsun redeploy, or by pushing an empty git commit:
Check your public key
Make sure your public key has been uploaded to your user account. Check it in the Upsun Console.SSH key can not be duplicated
A given SSH key pair can only be linked to a single user account. If you add an already used SSH key to another account, you see the error:SSH key can not be duplicated.
Generate a new pair of SSH keys for the second user account you want to add.
Check your SSH agent
Check that your key is properly added to your SSH agent. This is an authentication agent that manages your private key.-
Run
ssh-add -lin your terminal:You get output similar to the following: - Check that the file exists and that the file name or comment matches your private key file.
-
If you don’t see your private key file, add your private key:
Specify your identity file
If your identity (SSH key) associated with Upsun isn’t in a default file name (as may be explained in your SSH software manual, for example), you may have to append a specification like the one below so that the SSH software finds the correct key.upsun stands for a hostname.
Each different hostname you connect to Upsun at may have to be specified in the host line, separated by spaces.
Check your Git integrations
If your project is integrated with another Git provider (such as GitHub), that provider controls Git operations. Make sure you have added your public SSH key to your provider and that your user there has access.Generate SSH debug information
If your private key and public key both look OK but you don’t have any luck logging in, print debugging information. These lines often give clues about what’s going wrong. Run the SSH command with the-v option, like so:
MFA-related error message
If you haven’t enabled MFA on your user account and try to SSH into an environment that is protected by MFA, you get the following error message:- Enable MFA on the (bot) user account associated with the token.
- Generate a new access token, and then replace its value in your workflow that requires the token (such as updating a GitHub workflow secret variable).