End-of-Life (EoL)

Troubleshoot a Remote Repository Definition

contentrepository dev-prod dev prod remote repository repo Follow these steps to troubleshoot a remote repository definition.
The following instructions describe how to troubleshoot when defining a remote repository.
dial TCP Error Message
If a
dial tcp...
error message appears, when defining your remote repository and loading the list of repository branches.
  1. Contact your system administrator to enable connectivity. This may occur due to connectivity issues, such as a closed port or a proxy that is not enabling the connection.
Invalid SSH URL Error
An Invalid SSH URL error label appears, when defining your remote repository and entering the Repository URL.
  1. Ensure the URL is not the HTTPS version. Currently only SSH connections are supported (and only from the server itself, no engine support).
  2. Ensure the URL ends with `.git` such as `ssh://git@content.demisto.com:20017/~/my-project.git`.
Permission Denied Error
A permission denied error appears, when attempting to fetch the repository branches. This occurs because currently Cortex XSOAR supports only `RSA PRIVATE KEY`.
  1. Ensure you have set the correct passphrase and are using the correct key type.
  2. Navigate to the directory in which you saved the private key file.
  3. Open the private key file in a text editor and verify that the file begins with
    If the file does not begin with this text, regenerate the private key and add the -m pem flag. For example:
    ssh-keygen -t rsa -b 4096 -C "your_email@example.com" -m pem
Internal Server Error
internal server error. Something went wrong.
error message appears, when attempting to fetch the repository branches.
  1. In the server log files, search for
    Host keyverification failed
    error message.
  2. Connect to the server by SSH.
  3. Run the following command:
    ssh-agent bash-c "ssh-add ~/key; git clone [url]"
  4. Copy the file
    ~/.ssh/known_hosts to /var/lib/demisto/

Recommended For You