> 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/streaming/how-to-fix-streaming-timeout-errors.md).

# How to Fix Streaming Timeout Errors

{% hint style="danger" %}
Error Message: The server is not responding. Please try again after a few minutes
 (Error code: 10506)
{% endhint %}

Broadcasters communicate with various system layers to establish stable streaming environments. Error 10506 occurs when the response to the **"Go Live"** request (API) exceeds the allotted time, usually caused by temporary network instability or communication being blocked by security settings. Use this guide to resolve timeout issues and start broadcasts smoothly.

***

#### 1. Retry and Restart APP

#### 1. Immediate Solutions: Retry and Restart

Temporary network fluctuations or system resource issues can occasionally cause timeouts.

#### Solution

1. **Retry Connection:** Please press the **Go Live** button again. If it is a simple temporary network fluctuation, it can be resolved by retrying alone.
2. **Restart Application:** Close the app completely and relaunch it. Relaunching initializes background processes and can improve communication status.
3. **Reboot PC:** If the issue persists after restarting the app, restart your computer to clear system resources and reset network adapters.

***

#### 2. Check Network Environment

Stable and high-speed connections are essential for successful API communication and high-quality streaming.

#### Solution

1. **Check Stability:** Ensure the internet connection is active and stable without frequent drops.
2. **Verify Bandwidth:** Perform a speed test to confirm **Upload bandwidth** is sufficient for the currently set streaming bitrate.
3. **Use Wired Connection:** If using Wi-Fi, switch to a **wired Ethernet (LAN) connection** if possible. Wireless connections are more susceptible to packet loss and latency.
4. **Disable VPN and Proxy:** Turn off active VPNs or proxy settings. These configurations can complicate data paths and delay API response times.

***

### 3. Review Firewall and Security Software

Security programs may mistakenly identify network requests as potential threats and block communication.

#### Solution

1. **Allow App through Firewall:** Check Windows Firewall settings under Allow an app or feature through Windows Defender Firewall to ensure the app is selected.
2. **Temporarily Disable Security Software:** Try starting the broadcast after temporarily disabling antivirus or security software. If the broadcast starts successfully, add the app to the exclusion or whitelist in your security program.

***

### 4. Temporary Server Traffic

Even if local settings are correct, responses may be delayed due to temporary load on the platform or service servers.

#### Solution

* **Wait and Retry:** Service servers or streaming platform servers may be temporarily busy. If your network and settings are verified, please **wait a few minutes** and attempt to start the broadcast again.

[Desktop](/desktop/overview.md), [Guides](/desktop/guides.md), [Error Solution](/desktop/guides/error-solution.md), [Streaming](/desktop/guides/streaming.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guide.prismlive.com/desktop/guides/error-solution/streaming/how-to-fix-streaming-timeout-errors.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.

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.