Xtream Codes Error Messages: Causes and Fixes

Player error messages are short, but each one points at a different part of the system. This reference catalogs the messages you’re most likely to see, what they mean, and the fastest fix.

Login errors

“Invalid credentials” / “Login failed” / “Username or password is incorrect”

The portal accepted the connection but rejected the credentials.

• Check for typos, capitalization, and trailing spaces.
• Confirm the account is active (not expired or suspended).
• Reset the password at the provider if you can’t remember it.

“Connection refused” / “Could not connect” / “Network error”

The address couldn’t be reached.

• Verify the host and port exactly match the provider’s values.
• Confirm the scheme (https:// vs http://).
• Test the same address in a second app or a browser.

“Too many connections” / “Stream limit reached”

The account’s simultaneous-connection limit is in use.

• Close streams on other devices.
• Wait a few minutes for sessions to expire.
• Check your plan’s allowed connections.

Channel and stream errors

“Stream unavailable” / “Channel not found” / 404

The specific stream isn’t serving.

• Try the channel in another app to rule out a player issue.
• Confirm the channel still exists on your account.
• If it persists, report the channel name and time to the provider.

Buffering / “Playback error”

Usually a network or bitrate issue rather than a portal error.

• Test on a wired connection.
• Raise the player’s buffer setting.
• Check your connection speed against the stream’s bitrate.
• Try a lower-bitrate version of the channel if the player offers one.

“Format not supported” / “Codec error”

The player can’t decode this stream.

• Try another player app to see if it handles the codec.
• Switch the stream format (.m3u8 vs .ts) in the player settings if available.
• Check whether your device’s software is up to date.

“Service offline” / “Server not found”

The portal host itself isn’t reachable.

• Confirm the exact host and port from the provider.
• Test with the same address in a browser — if the browser also fails, the server or your network is the problem.
• Ask the provider whether the server is up.

Guide (EPG) errors

“No information” / empty guide

The playlist IDs and the EPG feed don’t match, or the feed hasn’t refreshed.

• Refresh the guide in the player.
• Confirm the feed URL is correct.
• Map missing channel IDs — see Xtream Codes EPG.

“EPG provider mismatch” / wrong shows

The player matched the wrong channel ID to the program data.

• Rebuild the EPG mapping in the player.
• In some apps, change the EPG time offset — a one-hour off-by-one gap usually means the wrong timezone offset is applied.

A quick error lookup table

Message you see	Likely cause	First fix
Invalid credentials	Wrong user/pass or disabled account	Re-enter carefully; check account status
Connection refused	Wrong host/port, or server down	Verify address; test in a browser
Too many connections	Limit reached	Close streams on other devices
Stream unavailable / 404	Stream removed or player issue	Try another app; report to provider
Playback error / buffering	Network or bitrate	Wired test; raise buffer; lower bitrate
Format not supported	Codec the player can’t decode	Try another player or stream format
No information (EPG)	ID mapping or feed stale	Refresh guide; remap channel IDs

Developer/API errors

If you call the player API directly and get an error response, the portal returns a message string or an HTTP status. See the Xtream Codes API reference for how each endpoint reports errors and what a given code means.

Common API responses:

• auth: 0 — credentials rejected.
• HTTP 403 — account disabled or the request is blocked.
• HTTP 404 — wrong port or endpoint path.
• HTTP 502/503 — portal or upstream failure; try again later.
• Empty arrays — the account or category has no content, or the account is a content-limited trial.

A structured approach

Rather than chasing individual messages, work through the full troubleshooting guide — it isolates credentials, network, app, and provider in a fixed order.

Security note

Never “fix” errors by bypassing the provider’s controls or by obtaining credentials from unauthorized sources. Use the supported path: correct credentials, a working network, and a properly configured player. See Xtream Codes security.

Related reading

• Xtream Codes troubleshooting — the step-by-step process.
• How to log in to Xtream Codes — get login errors resolved.
• The Xtream Codes API — endpoint-level error details.
• Xtream Codes security — protecting your credentials.