Skip to content 
Xtream Request Failed / Failed to Connect: How to Fix It
“Xtream request failed / failed to connect” almost always means your player reached out with the login you typed and the server refused the handshake. Nine times out of ten it is one of a short list of fixable things: the server URL is in the wrong format, the port is missing, you are on http when the line needs https (or the reverse), your subscription has expired, every connection slot is already in use, your device clock is wrong, or the host is being blocked by DNS. Work down that list and the connection comes back.
The error is worded to sound like a dead end, but it is really a diagnosis waiting to happen. The word “connect” is the clue: your app opened its side of the conversation and the other end never completed it. That failure can sit in three places — the details you entered, the line itself, or the network between them — and the whole trick is telling those three apart before you start changing settings at random. This guide walks the exact cause-checklist in the order that resolves the most cases first, then shows how to tell an app problem from a provider problem so you stop guessing.
What “Xtream request failed / failed to connect” actually means
An Xtream login is not magic; it is a small web request. Your player takes the server address, your username and your password, and asks a single file on the server — the player API — to confirm the account and hand back your channel and guide lists. “Failed to connect” means that request never got a proper answer. Either the app could not reach the address at all, or it reached it and the server said no. It is a handshake that did not complete, not a sign your channels are gone.
That distinction matters because it splits every fix into two families. If the app cannot reach the address, the problem is the URL, the port, the protocol, your network or DNS. If the app reaches the server but is refused, the problem is your credentials, an expired line, or a connection limit. Knowing which family you are in saves you from toggling settings that were never the issue. If you are still new to how these apps work, our explainer on what an IPTV player is sets the scene, and the difference between the two login styles is covered in M3U vs Xtream Codes.
The most common causes, ranked
Start at the top and stop when the connection returns. This order fixes the majority of “Xtream request failed” reports without touching anything you did not need to.
1. The server URL is in the wrong format. The server field wants only the base address, like http://example.com:8080. It should not end in a slash and should never include the API filename or a playlist path such as /player_api.php or /get.php — the app adds those itself. A single stray character here produces an instant “failed to connect”, and it is the number-one cause. 2. The port is missing. Most lines answer on a specific port, and if you leave it off the app knocks on the default door and gets no reply. Add the :port exactly as your provider gave it. If you are unsure what a port even is, the overview of a network port explains why it has to match.
3. http vs https mismatch. Some lines run on plain http, others on secured https, and the two are not interchangeable. If http fails, try https and vice versa — the wrong one refuses the handshake. 4. Wrong or mistyped credentials. Usernames and passwords are case-sensitive, and a copied space or a swapped l/1 is enough to be refused. Retype them by hand rather than trusting a paste. 5. The subscription has expired or the line is disabled. An out-of-date or suspended line answers every request with a refusal that looks identical to a typo. If everything else checks out, confirm the account is active.
6. The connection limit is already reached. Xtream lines allow a set number of simultaneous connections, and once they are all in use a new device is turned away. Another device left playing in another room, or a session that did not close cleanly, can hold a slot. Close the others and try again. 7. The device clock is wrong. This one surprises people: a secured line uses a certificate that is only valid inside a date range, and your device compares that range to its own clock. If the date, time or time zone is off, a perfectly good certificate looks expired and the TLS handshake fails. Set the clock to update automatically. 8. DNS or an ISP block. If the host name will not resolve, the app cannot find the server at all. Switching your device or router to a public resolver often clears it, because the problem is name lookup rather than the line. The role of name lookup is explained well in the overview of the Domain Name System.
App-side vs provider-side: how to tell whose fault it is
Before you contact anyone or reinstall anything, find out which side of the fence the fault sits on. The fastest test is to try the same login on a second app or a second device on the same network. If it fails everywhere, the line or your network is the suspect. If it works elsewhere, the first app or its settings are the problem.
| Symptom | Most likely side | First thing to try |
|---|---|---|
| Fails on every app and device | Provider or network | Check the line is active and the connection limit is not maxed; test on mobile data |
| Fails in one app, works in another | App or its settings | Re-enter the URL, port and protocol; clear the app’s cache |
| Worked yesterday, dead today | Provider or clock | Confirm the subscription date and that the device clock is correct |
| Only fails on one network | DNS or ISP block | Change DNS to a public resolver, or test on a different connection |
| Fails only after a big playlist loads | App handling | Use a player that handles a large playlist without lag |
This split is why “failed to connect” is so often misfiled. People reinstall an app when the line was simply maxed out, or they blame the provider when a trailing slash in the URL was doing the damage. Ten minutes of testing on a second device points you straight at the real cause. A sibling symptom worth knowing is when a login succeeds but playback still stops — that is a different animal, covered in IPTV Smarters showing unable to play stream.
Fix it step by step
Here is the clean run-through, from the fixes that resolve the most cases to the ones that catch the stubborn stragglers. Do them in order and re-test after each.
First, retype the server address as the bare base URL with the correct protocol and port and nothing on the end — no slash, no player_api.php, no get.php. Second, retype the username and password by hand, watching case and stray spaces. Third, if it still refuses, flip the protocol between http and https and try once more. Fourth, confirm the account is still active and within date; an expired line is a silent refusal. Fifth, make sure no other device is holding your connection slots, then try again. Sixth, open your device settings and set the date, time and time zone to update automatically, because a wrong clock quietly breaks secured logins. Seventh, if only one network fails, switch the device or router DNS to a well-known public resolver, or test on a phone hotspot to prove whether your home network is the block. Most people are reconnected by the third or fourth step; the last three exist for the cases the obvious ones miss.
If the login now works but the picture keeps stalling once you are in, that is buffering rather than a connection failure, and our guide to fixing buffering after an update takes it from there.
Why some players choke on Xtream — and how mtivi handles it
A surprising number of “failed to connect” reports come down to how forgiving the app is about what you paste in. Some players demand a flawless URL and give you a single cryptic error when it is not, with no hint about the slash, the port or the protocol that caused it. That turns a two-second typo into an evening of reinstalling.
mtivi is built to take the Xtream login the way people actually have it: paste the server, username and password, and it sorts the base URL, adds the API path itself and tries the login cleanly, so a stray slash or a forgotten port is far less likely to sink you. It plays your own M3U or Xtream source — it supplies no channels of its own — and it is free to start with no account needed, so you can test your exact line in minutes before committing. Once you are in, features like cloud sync that carries your playlist and favourites across devices mean you set the login up once and it travels with you, rather than re-entering it on every box and risking the same typo again. It runs today on Android phones and tablets, Android TV, Google TV, Fire TV and Firestick, Nvidia Shield and Android boxes, with Apple and Windows apps on the roadmap.
Related guides
- M3U vs Xtream Codes: Which IPTV Format Should You Use?
- IPTV Smarters Unable to Play Stream? How to Find the Cause
- TiviMate Buffering After Update? Fixes That Actually Work
- What Is an IPTV Player? A Clear Guide for 2026
Frequently asked questions
Why do I get “Xtream request failed / failed to connect”?
It means your player sent your login to the server and the handshake did not complete. The usual causes are a badly formatted server URL, a missing port, the wrong http or https protocol, mistyped credentials, an expired line, a maxed-out connection limit, a wrong device clock, or a DNS block. Work down that list in order and the connection normally returns.
Do I need to add a port number to my Xtream server URL?
Usually yes. Most lines answer on a specific port, so the address should look like http://example.com:8080. If you leave the port off, the app tries a default that the server is not listening on and you get “failed to connect”. Enter the port exactly as your provider gave it.
Is “failed to connect” my provider’s fault or my app’s?
Test the same login on a second app or device on the same network. If it fails everywhere, the line or your network is the likely cause — check the account is active and the connection limit is not full. If it works in another app, the first app’s URL, port or protocol settings are the problem.
Should the server URL end with player_api.php or get.php?
No. The server field wants only the base address, such as http://example.com:8080, with no trailing slash and no API filename. The player appends player_api.php or the playlist path itself. Adding it by hand is one of the most common reasons a login is refused.
Can the wrong date or time on my device cause Xtream to fail?
Yes, on secured lines. A secured connection uses a certificate that is only valid inside a date range, and your device compares that range to its own clock. If the date, time or time zone is wrong, a valid certificate looks expired and the login fails. Set the clock to update automatically.
What does “connection limit reached” have to do with failed to connect?
Xtream lines allow a fixed number of simultaneous connections. When all the slots are in use — often by another device still playing, or a session that did not close cleanly — a new login is turned away with a connection error. Close the other sessions and try again.
Can my ISP block the Xtream port or host?
It can. If the host name will not resolve or the port is blocked on one network only, the app cannot reach the server. Switching your device or router to a public DNS resolver often clears a name-lookup block, and testing on mobile data quickly shows whether your home network is the cause.
Why does http work but https fails, or the other way round?
Lines run on either plain http or secured https, and the two are not interchangeable. If one protocol refuses the handshake, switch to the other and try the login again. Using the wrong protocol produces the same “failed to connect” message as a bad address.
I get the error after a big playlist loads — why?
That is usually the app struggling with the size of the list rather than a true login failure. A player built to keep a large channel list and guide loaded smoothly avoids the stalls that look like connection drops. Choosing an app that handles a large playlist without lag fixes this class of problem.
Does mtivi provide the channels behind an Xtream login?
No. mtivi is a media player. We don’t provide, sell, or include any channels, movies, series, or playlists. You add your own M3U or Xtream source, and the player simply connects to it and plays what you point it at.
Will reinstalling the app fix “failed to connect”?
Rarely, on its own. A reinstall only helps if the app’s stored settings were corrupted. Because the error is almost always the URL format, the port, the protocol, the line status or the network, it is faster to re-enter the login carefully and test on a second device before wiping and reinstalling anything.
