> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-multi-tenant-guides/6.14/configure-multi-tenant/remote-repositories-for-multi-tenant-deployments/troubleshoot-a-remote-repository-configuration/troubleshoot-a-remote-repository-definition.md).

# 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, do the following:

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 HTTP/SSH URL Error**

An Invalid SSH URL error label appears, when defining your remote repository and entering the Repository URL.

1. 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 **`-----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`**

**Internal Server Error**

The **`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 PATH/TO/PRIVATE/KEY; git clone GIT_SSH_URL"`

   For example: `ssh-agent bash -c "ssh-add ~/.ssh/my_id_rsa; git clone ssh://git@ssh.github.com:443/myusername/myreponame.git"`
4. Copy the file `~/.ssh/known_hosts to /var/lib/demisto/`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-multi-tenant-guides/6.14/configure-multi-tenant/remote-repositories-for-multi-tenant-deployments/troubleshoot-a-remote-repository-configuration/troubleshoot-a-remote-repository-definition.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.