Why does my Xtream Codes login say authentication failed?

The most common causes are a typo in the username or password, using the wrong host URL, or an expired or disabled account. Copy the credentials directly from your provider instead of typing them manually.

Why do channels load but then buffer constantly?

Buffering after a successful login usually means a weak internet connection, a server overload at your provider, or a device that cannot decode the stream format fast enough. Test with a wired connection and try a different server if your provider offers one.

Why is my EPG empty even though channels load?

EPG requires a separate data source linked in your player. Check that your player's EPG URL is set correctly, that you have refreshed the guide data, and that the channel IDs in the stream list match those in the EPG feed.

My account was working yesterday — why did it stop?

Providers occasionally rotate server IPs, change ports, or revoke accounts that have exceeded their connection limit. Contact your provider and confirm the host, port, and your subscription status.

Can too many simultaneous connections block my access?

Yes. Most subscriptions allow one or two simultaneous streams. If another device is using the same credentials, the portal may refuse a third connection. Disconnect other devices and try again.

Xtream Codes Not Working: 9 Fixes That Actually Solve It

Xtream Codes stops working for a finite set of reasons. This guide covers all nine of them in order from most to least common, with a concrete fix for each. Work through the checklist from the top — most people find their answer by fix three or four.

Fix 1 — Check your credentials for typos

This is the cause of more failures than anything else. Credentials are case-sensitive, and providers sometimes use characters that look alike: 0 vs O, l vs 1, | vs I.

What to do:

Copy your username, password, and host from the provider’s welcome email — do not retype them manually
Paste them into a plain-text editor first to strip any hidden formatting
Confirm there are no leading or trailing spaces

If your player has a QR code or URL import option, use that instead of manual entry.

Fix 2 — Verify the host URL format

The host field must be exact. A common mistake is entering just a domain name when the port is required, or including a path that shouldn’t be there.

Correct format:

http://provider.example.com:8080

Wrong formats that will fail:

provider.example.com           ← missing protocol and port
http://provider.example.com/   ← trailing slash breaks some players
provider.example.com:8080      ← missing protocol

Check your provider’s setup instructions for the exact format they expect. Some send a full M3U URL — if so, see how to extract Xtream credentials from a URL.

Fix 3 — Test your account status

Your subscription may have expired or been suspended. Most portals will return an auth: 1 response even for expired accounts but set status: Expired in the user info.

Quick test — paste this in your browser:

http://YOUR_HOST:PORT/player_api.php?username=YOUR_USER&password=YOUR_PASS

Look at the JSON response:

"auth": 0 → wrong credentials
"status": "Expired" → subscription ended
"status": "Disabled" → account suspended by provider
"status": "Active" → account is fine, problem is elsewhere

If expired or disabled, contact your provider directly.

Fix 4 — Check simultaneous connection limits

Most IPTV subscriptions allow 1–2 simultaneous streams. If another device in your household (or a forgotten background app) is consuming a connection, the portal will refuse you.

How to check: Look for "active_cons" and "max_connections" in the API response from Fix 3.

"active_cons": "2",
"max_connections": "2"

If those numbers match, you are at your limit. Stop playback on other devices, wait 2–3 minutes for the session to time out, then try again.

Fix 5 — Test your internet connection speed

Xtream Codes streams require consistent bandwidth. HD channels typically need 5–10 Mbps; 4K streams need 25 Mbps or more. A slow or unstable connection causes buffering even when login works.

Quick tests:

Run a speed test at fast.com — note download speed and latency
Try connecting via ethernet instead of Wi-Fi
Close other apps and devices that are using bandwidth

If your speed is adequate but buffering persists, the problem is on the provider’s server — try a different server region if they offer one, or contact support.

Fix 6 — Switch stream format or output type

Some players default to MPEG-TS (.ts) streams. If your device or network has trouble with TS, switching to HLS (.m3u8) often resolves buffering and playback failures.

In most players look for a setting called Output Format, Stream Type, or Protocol. Try:

ts → m3u8 (or vice versa)
Disable hardware decoding temporarily — some devices mishandle certain codecs in hardware mode

The allowed_output_formats field in your account’s API response shows which formats your subscription supports.

Fix 7 — Fix an empty or broken EPG

EPG (Electronic Program Guide) is a separate data layer from your channel streams. It breaks independently of playback.

Common causes and fixes:

Symptom	Cause	Fix
Guide completely empty	EPG URL not set	Add the EPG URL in player settings
Guide loads but wrong channels	Channel IDs mismatched	Use your provider’s XMLTV URL, not a third-party one
Guide was working, now stale	Cache not refreshed	Force a manual EPG refresh in your player
Guide loads once, disappears	Player memory limits	Reduce EPG fetch interval or use a lighter EPG source

Your provider’s EPG URL is usually:

http://YOUR_HOST:PORT/xmltv.php?username=YOUR_USER&password=YOUR_PASS

See Xtream Codes EPG guide for full details.

Fix 8 — Clear player cache and re-add the account

Players accumulate cached channel lists, tokens, and stream data. If your provider has changed their server setup since you first configured the app, the cache can cause unexpected failures even though your credentials are valid.

Steps:

Remove your account from the player entirely
Clear the app’s cache (Android: Settings → Apps → [Player] → Clear Cache)
Restart the app
Re-add your account from scratch

This fixes a surprising number of “it stopped working for no reason” cases.

Fix 9 — Check whether the provider’s server is down

Sometimes the problem is simply that your provider’s server is temporarily offline. This is not something you can fix — but you can confirm it quickly.

How to test:

Paste the API URL from Fix 3 into a browser on a different device (phone on mobile data, not your home Wi-Fi)
If it times out or returns a connection error from both networks, the server is down
Check if other users are reporting issues (provider’s Telegram group, Discord, or support ticket)

Most providers resolve server issues within hours. If the server is down for more than 24 hours with no response from support, consider that a signal about the provider’s reliability.

When none of these fixes work

If you have been through all nine fixes and the problem persists:

Try a different player — test your credentials in a second app to confirm whether it is a player-specific issue or an account issue. See Xtream Codes players.
Try a different network — use mobile data to rule out an ISP block on your home network
Open a support ticket — include the API response from Fix 3 so your provider can see exactly what the account status is

The Xtream Codes error reference lists specific error codes and what they mean if you are seeing a particular message in your player.

Summary checklist

#	Check	Tool
1	Credentials — no typos	Paste from email
2	Host URL format	Compare to provider instructions
3	Account status	API test URL
4	Connection limit	`active_cons` vs `max_connections`
5	Internet speed	fast.com
6	Stream format	Player output settings
7	EPG URL	Player EPG settings
8	Player cache	App clear cache
9	Server status	Test from different network