> For the complete documentation index, see [llms.txt](https://guide.prismlive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.prismlive.com/desktop/guides/error-solution/others/handling-stream-key-or-channel-access-issue.md).

# Handling Stream Key or Channel Access Issue

Windows, Mac

{% hint style="danger" %}
Error Message: Could not access the specified channel or stream key, please double-check your stream key. If it is correct, there may be a problem connecting to the server.
{% endhint %}

The error you experienced corresponds to the OBS\_OUTPUT\_INVALID\_STREAM error case in OBS. And it means that your stream settings are invalid or not compatible with the streaming platform you're trying to connect to.

***

This guide will help you understand the possible causes and how to fix them step by step.<br>

## 1. Invalid Server URL

The server address you're trying to stream to might be incorrect, outdated, or no longer supported.

Try the following steps:

* Double-check the RTMP or RTMPS URL from your streaming platform (e.g., YouTube, Twitch, Facebook).
* Make sure you’ve copied and pasted the full server URL correctly into PRISM.
* Example (YouTube):
  \
  rtmp\://a.rtmp.youtube.com/live2

## 2. Incorrect Stream Key

The stream key is a unique code that links PRISM to your specific live stream. If it’s wrong, the stream won’t connect.

Try the following steps:

* Go to your streaming platform and find the current stream key.
* Copy the exact stream key and paste it into the PRISM stream settings.
* Be careful not to include any extra spaces before or after the key.

## 3. Codec or Resolution Issues

Your video settings might not match what your streaming platform supports.

Try the following steps:

* Try using common settings like:
  * Video codec: H.264 (AVC)
  * Audio codec: AAC
  * Resolution: 1920x1080 or 1280x720
  * Bitrate: 2500–6000 kbps, depending on platform recommendations.
* Check the platform’s documentation for the exact requirements.

## 4. Unsupported Streaming Protocol

Some platforms support only certain protocols (e.g., RTMP or RTMPS).

Try the following steps:

* Check whether your platform supports RTMP or requires RTMPS (secure RTMP).
* Update the protocol in PRISM accordingly.
* Example: Facebook Live requires RTMPS, not plain RTMP.

<br>

Restart PRISM after making changes to ensure new settings are applied. If you're using a custom RTMP server, make sure it’s online and reachable from your network. Some platforms require enabling streaming permissions — check your account settings.

[Desktop](/desktop/overview.md), [Guides](/desktop/guides.md), [Error Solution](/desktop/guides/error-solution.md), [Others](/desktop/guides/error-solution/others.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guide.prismlive.com/desktop/guides/error-solution/others/handling-stream-key-or-channel-access-issue.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 `automate deployments from our CI pipeline` 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.