> 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-content-issues.md).

# Troubleshoot Content Issues

The following instructions describe how to troubleshoot issues with your content.

**Missing Content**

After enabling the remote repository feature or updating content, some content is missing. To resolve this issue, restore the content backup package that was created when you enabled the feature or updated content.

1. Copy the content package from the server to your local machine using the **`scp`** command.

   The backup is located at `/var/lib/demisto/backup/content-backup-*`
2. In Cortex XSOAR, navigate to Settings → About → Troubleshooting → Custom content → **Import** and upload the content package.

**Missing Content History**

When using characters that are not UTF-8, the version history is not available.

1. Connect to the environment on which you are experiencing the issue using SSH.
2. Run the following **`git config --global core.quotepath off`** command.

**Repository Connection Error**

When attempting to commit content to the remote repository, the following error appears:

<sub>Another git process seems to be running in this repository, e.g.an editor opened by 'git commit'. Please make sure all processes are terminated, then try again. If it still fails, a git process may have crashed in this repository earlier: remove the file manually to continue.) 2020-09-15 15:34:15.9433 error VC: failed to add objects files 'automation-GetMLModelEvaluation.yml, automation-DBotMLFetchData.yml, automation-DBotBuildPhishingClassifier.yml, automation-DBotPreProcessTextData.yml, automation-SanePdfReports.yml, automation-CommonServerPowerShell.yml, automation-GetIndicatorsByQuery.yml, automation-GetIncidentsByQuery.yml, automation-SaneDocReports.yml, automation-DBotSuggestClassifierMapping.yml, automation-DBotTrainTextClassifierV2.yml' to index (source: /home/circleci/.go\_workspace/src/github.com/demisto/server/util/versioncontrol/versioncontrol.go:1631)(error: exit status 128fatal: Unable to create '/var/lib/demisto/versionControlRepo/.git/index.lock': File exists.</sub>

This can occur if the server was stopped during Git execution.

Delete the **`index.lock`** file located in the **`/var/lib/demisto/versionControlRepo/.git/`** directory to solve the issue.

**Content Installation Error**

When installing content from the content repo, a message similar to the following appears:

<sup>Could not create incidenttype with ID 'Phishing' and name 'Phishing'. Version (oldVersionNumber) is not compatible with environment version (versionNumber) \[Content Pack: \<contentPackName>] (100018)]</sup>

{% hint style="info" %}

### Note

Before implementing the following solution, ensure that the content item from the error message is not detached. If the item is detached, after you re-attach it, the change will show up in the local changes under items and not packs.
{% endhint %}

1. In your development environment, upgrade the relevant content pack, or re-install the content pack from Marketplace → Installed content packs → **Version history**.
2. Push the content pack that was updated as well as the relevant items from the **Items** tab in local changes in the development environment.
3. In your production environment, pull your content.


---

# 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-content-issues.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.