Read the first digit first
Every standard error has three digits, and the first one tells you where to look:
- 4xx codes (400 to 499): the request was refused. The server is working, but it won’t serve what the app asked for: the login is wrong, the address points to nothing, or access is blocked. These are usually fixable by correcting a login, a link or a setting.
- 5xx codes (500 to 599): the server had a problem. Your request was fine, but the server or something in front of it failed. There’s little you can change at home, apart from waiting and trying again.
Codes that don’t appear in the web standards, such as 456 or 458, come from particular server platforms. We mark those clearly below.
The error code table
| Code | Standard meaning | What it usually means for IPTV | Who can fix it |
|---|---|---|---|
| 401 | Unauthorized | The login wasn’t accepted | Usually you: check the username, password and server. See authorization failed |
| 403 | Forbidden | The server knows the request but won’t serve it to you: account, IP or app restrictions | You or the provider |
| 404 | Not Found | The channel, film or playlist address doesn’t exist on that server | Usually you: refresh the playlist or fix the address |
| 405 | Method Not Allowed | The app asked in a way the server doesn’t accept, often a wrong address format | You: check the server address |
| 429 | Too Many Requests | The app asked too often and was paused | Wait, then try again |
| 451 | Unavailable for Legal Reasons | Access blocked for a legal reason, often by a network-level block | Not fixable in the app |
| 456 / 458 | Not standard | Used by some IPTV platforms for connection or access limits | Check the limits with your provider. See too many connections |
| 500 | Internal Server Error | The server failed while handling the request | The provider |
| 502 | Bad Gateway | A server in the chain got a bad answer from the one behind it | The provider; retry later. See server unavailable |
| 503 / 504 | Service Unavailable / Gateway Timeout | The server is overloaded, down for maintenance or too slow to answer | The provider; retry later |
| 509 | Not standard (“bandwidth limit exceeded”) | The account or server hit a bandwidth limit | The provider |
| 511 | Network Authentication Required | Your network wants you to log in first, typically hotel or public Wi-Fi | You: sign in to the Wi-Fi |
| 512 / 513 | Not standard | Platform-specific server errors | The provider |
| 521 | Not standard (used by Cloudflare) | The website or server behind Cloudflare is down | The provider |
What to do with any code
- Write down the exact number and message. “Error 403” and “403 Forbidden, access denied” can point to different fixes on some apps.
- Try another channel and another device. If the error appears on one channel only, the fault is with that stream. On every channel and every device, it’s the login or the server.
- Try mobile data. An error that disappears on mobile data points to your home network or broadband provider, not to the service.
- Restart properly. Close the app completely, restart the router and the device, and try again. See the troubleshooting guide for the full routine.
If the code is a 5xx one, or it appears on every device and every connection, the fix is at the provider’s end. Our server unavailable guide explains how to confirm that before you contact them.
Errors that aren’t numbers
Some of the most common messages have no number at all:
- “Authorization failed” or “invalid credentials”: see authorization failed.
- “Playback error” or “stream failed”: see playback error.
- “Codec not supported”: the device can’t decode how the channel was encoded. See codec not supported.
- SSL or certificate errors: often an old device that no longer trusts modern security certificates. See SSL errors.