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.
If a
dial tcp...
error message appears,
when defining your remote repository and loading the list of repository
branches.
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.
An Invalid SSH URL error label appears, when defining your remote
repository and entering the Repository URL.
Ensure the URL is not the HTTPS version. Currently only
SSH connections are supported (and only from the server itself,
no engine support).
Ensure the URL ends with `.git` such as `ssh://git@content.demisto.com:20017/~/my-project.git`.
A permission denied error appears, when attempting to fetch the
repository branches. This occurs because currently Cortex XSOAR
supports only `RSA PRIVATE KEY`.
Ensure you have set the correct passphrase and are using
the correct key type.
Navigate to the directory in which you saved the private key
file.
Open the private key file in a text editor and verify that
the file begins with
-----BEGIN RSA PRIVATE KEY-----
.
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
The
internal server error. Something went wrong.
error
message appears, when attempting to fetch the repository branches.
In the server log files, search for
Host keyverification failed
error
message.
Connect to the server by SSH.
Run the following command:
ssh-agent bash-c "ssh-add ~/key; git clone [url]"
Copy the file
~/.ssh/known_hosts to /var/lib/demisto/
.
