How to Connect a Copado Version Control Repository in Copado

Updated 1 week ago by Copado Solutions


SSH authentication with Copado Version Control is only available if your backend server is on the Copado Google Cloud Platform (CopaGCP). Otherwise, follow the steps in the HTTPs section.
Internal SSH

To leverage the best connection speeds, we recommend authenticating your Git Repository in the Copado application using the internal infrastructure SSH. In this case, all the traffic between the Copado Application and Copado Version Control remains within our infrastructure without going through the public internet. 

To authenticate using the internal SSH, follow these steps:

  1. In Copado, create a new Git Repository record.
  2. Give your repository a name.
  3. Select the desired source format.
  4. Select SSH in Authentication Type.
  5. Since Copado Version Control is hosted within the Copado infrastructure, and in order to benefit from the fastest connection speed to your repository, don’t use the repository SSH URI provided on the repository page. Instead, build the SSH URI as described below:



  1. <clientName> with your Copado Version Control registered client name. You can get it from the repository page by selecting SSH and copying it from the URI provided.
  2. <username> with your username
  3. <repoName> with the repository name
  4. Example:
    1. <domainName> = acme
    2. <username> = SalesOperations
    3. <repoName> = CRM


  1. Now you need to create a new pair of keys. To do so, click on Create SSH Keys.
  2. Scroll down to the Current Keys related list.
  3. Click on the View link next to the file and copy the content.
Current Keys related list
  1. In Copado Version Control, click on your profile and select Settings

Settings in Copado Version Control

  1. Click on SSH/GPG Keys
  2. On the Manage SSH Key section, click on Add Key.
    Add Key
    1. Give your key a name.
    2. Paste the public key that was copied into the Content box. 
    3. When ready, click on Add Key.
Fill information for Add Key
External SSH

Alternatively, and although not recommended, you can use the external SSH connection. In this case, the traffic between Copado Application and Copado Version Control will go through the public internet.

To authenticate using the external SSH, review the HTTPS vs SSH Authentication article to connect your repository via SSH. In this case, disregard the instruction to open Port 22.

Alternatively, if you want to connect to Copado Version Control locally through your IDE, please follow the process described in this article.


If your backend server is on Heroku, then use the HTTPs authentication protocol to connect to Copado Version Control.

Please review the HTTPS vs SSH Authentication article to connect your repository via HTTPS.

How did we do?