# Page Not Found

The URL `integrations/existing-integrations/git-sync/why-am-i-getting-a-git-authentication-failed-message` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Why am I getting a Git authentication failed message?](https://gitbook.com/docs/help-center/integrations/integrations-troubleshooting/git-sync/why-am-i-getting-a-git-authentication-failed-message.md)
- [​Nothing happens on GitBook after adding a new file to my repository](https://gitbook.com/docs/help-center/integrations/integrations-troubleshooting/git-sync/nothing-happens-on-gitbook-after-adding-a-new-file-to-my-repository.md)
- [GitBook is creating new markdown files](https://gitbook.com/docs/help-center/integrations/integrations-troubleshooting/git-sync/gitbook-is-creating-new-markdown-files.md)
- [Error when pushing to the repository with protected branch](https://gitbook.com/docs/help-center/integrations/integrations-troubleshooting/git-sync/error-when-pushing-to-the-repository-with-protected-branch.md)
- [Git Sync file size limitations](https://gitbook.com/docs/help-center/integrations/integrations-troubleshooting/git-sync/git-sync-file-size-limitations.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://gitbook.com/docs/help-center/integrations/integrations-troubleshooting/git-sync/why-am-i-getting-a-git-authentication-failed-message.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://gitbook.com/docs/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://gitbook.com/docs/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/docs/help-center/integrations/integrations-troubleshooting/git-sync/why-am-i-getting-a-git-authentication-failed-message.md`).

You may also use `Accept: text/markdown` header for content negotiation.