# Page Not Found

The URL `files/nBiOy1SBDw39xlPeY4bj` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Emby/Jellyfin](https://streamsmanager.gitbook.io/streams-manager/troubleshooting/emby-jellyfin.md)
- [Overview](https://streamsmanager.gitbook.io/streams-manager/plex-bans/overview.md)
- [Specific plan is not showing up on the checkout page](https://streamsmanager.gitbook.io/streams-manager/troubleshooting/specific-plan-is-not-showing-up-on-the-checkout-page.md)
- [How Streams Manager enforces download limits?](https://streamsmanager.gitbook.io/streams-manager/faq/how-streams-manager-enforces-download-limits.md)
- [Subscriptions & trials settings](https://streamsmanager.gitbook.io/streams-manager/configuration/settings/subscriptions-and-trials-settings.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://streamsmanager.gitbook.io/streams-manager/troubleshooting/emby-jellyfin.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://streamsmanager.gitbook.io/streams-manager/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://streamsmanager.gitbook.io/streams-manager/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., `/streams-manager/troubleshooting/emby-jellyfin.md`).

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