> 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/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/remote-repositories-in-cortex-xsoar/troubleshoot-a-remote-repository-configuration.md).

# Troubleshoot a Remote Repository Configuration

Troubleshoot Cortex XSOAR 6.15 remote repository configuration and content workflow issues.

You can troubleshoot the following issues:

* [Troubleshoot a Remote Repository Definition](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/remote-repositories-in-cortex-xsoar/troubleshoot-a-remote-repository-configuration/troubleshoot-a-remote-repository-definition.md)
* [Troubleshoot Editing and Pushing Content](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/remote-repositories-in-cortex-xsoar/troubleshoot-a-remote-repository-configuration/troubleshoot-editing-and-pushing-content.md)
* [Troubleshoot Content Issues](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/remote-repositories-in-cortex-xsoar/troubleshoot-a-remote-repository-configuration/troubleshoot-content-issues.md)
* [Troubleshoot a Remote Repository with an HTTP Proxy](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/remote-repositories-in-cortex-xsoar/troubleshoot-a-remote-repository-configuration/troubleshoot-a-remote-repository-with-an-http-proxy.md)

**FAQs**

**Question: Which services are supported?**

Answer: Working with remote repositories is Git-based. Any service that supports this protocol can be used, for example, GitHub, GitLab, Bitbucket, etc. In addition, on-premise repositories are also supported.

**Question: Does Cortex XSOAR remote repository configuration support GPG signing?**

Answer: yes

1. Connect to the environment on which you are experiencing the issue using SSH.
2. Run the following commands:
   * `git --global config user.signingKey KEYID` where KEYID is your key ID.
   * `git --global config commit.gpgSign true`

**Question: Can I limit permissions for pushing content?**

Answer: Yes. See [Edit and Push Content to a Remote Repository](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/remote-repositories-in-cortex-xsoar/edit-and-push-content-to-a-remote-repository.md).

**Question: Can I edit content in my production environment?**

Answer: No. When working in a remote repository configuration, content can only be edited in the development environment.

**Question: Can I validate my development environment with SSH public key authentication?**

Yes. A remote repository can be validated using SSH public key authentication with a certificate.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/remote-repositories-in-cortex-xsoar/troubleshoot-a-remote-repository-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.