IPTV M3U URL not working? What to check first
If your player won't read an M3U link or loads no channels, the link is nearly always at fault: a copy that got cut off, a login that's expired, or a provider that's moved servers. The app only reports what it's handed. Here's what to check, quickest first.
Which problem is it?
"Not working" covers three different faults, and they don't share a fix:
- The playlist won't load. No channels at all, or an error like "couldn't read playlist". That's this page.
- Channels load but won't play. The link's fine, the streams aren't. See some channels work and others don't.
- Channels play but the guide's empty. That's the EPG, a separate feed. See EPG showing "no information".
Stuck on the first one? Read on.
Check the link copied whole
Easily the most common cause, and the dullest. M3U links are long, and pulling one out of an email is easy to fumble; miss the last few characters and it won't resolve.
Paste it into a notes app and look at both ends. It should start http:// or https:// and usually end in get.php?username=... or .m3u. If the tail looks chopped, or a space or line break has crept in where the email wrapped, there's your culprit. Watch for curly quotes too, if it came through something that autocorrected the punctuation. Copy it again from the source rather than retyping it.
seefax will take the whole welcome email and find the link inside, so you needn't fish it out yourself. It still can't rescue characters that never got copied.
Your login lives in the link
An M3U link isn't just an address, it's your login as well. The username and password sit right there in the text, which matters twice over.
It's why the link is private: anyone holding the full URL can watch on your subscription. And it's why a link that worked last month can suddenly die, because the moment your provider resets your password or reissues your details, the old link is wrong even though it looks identical.
Has the subscription lapsed?
An expired subscription fails exactly like a wrong password, usually with no polite "your plan has ended" to explain it. So rule it out early. Is it still active? Did the last payment go through? If your provider has a login portal and it won't let you in there either, the app was never the problem.
The provider may have moved
IPTV providers change domains more than most, sometimes because the old one got blocked, sometimes just housekeeping. When they do, every old link pointing at the previous domain dies at once.
The giveaway is timing: it worked, then everything on that provider failed at the same moment, with nothing changed at your end. That's not a typo, it's a server that's gone, and you'll need a fresh link from the provider. No app can guess the new address.
Try http instead of https
Usually the http or https at the front just works. Occasionally a server only answers on one of the two, so a link that says https against an http-only server (or the reverse) fails before a single channel loads. A mate of ours hit exactly that: same link, fine for one person, dead for another, purely on the scheme.
seefax retries the other scheme for you before it gives up. In a player that doesn't, swap it by hand; it's a thirty-second test that sometimes fixes the lot. Certificate errors on https links are the same story, and usually the provider's to sort.
Are you over the connection limit?
Providers cap how many streams you can run at once, counted in streams, not devices. Hit the cap and a new login can be refused until something frees up. If seefax is on the telly, your phone and a tablet all at once, close a couple and try again.
Compare it in another player
The cleanest test there is. The link is your provider's, not the app's, so it should behave the same anywhere. Load it into a second player: if it fails there too, it's the link or the provider, not seefax; if it works there but not here, that's worth telling us on support. Mind the privacy point below, though, and don't post it anywhere public to run the test.
When it's the provider, not the player
So it's the provider's end, and nothing an app can fix, when:
- the same link fails in more than one player;
- everything died at once, with no change from you;
- the provider's own portal won't let you in;
- the subscription has lapsed, or the account was reset.
Then it's a message to the provider for a current link, or confirmation the account's live. A player's job is to load a valid link and say so plainly when it can't, which is what seefax aims for: a readable error, not a silent black screen. It can't summon a link the provider has retired.
One rule worth keeping: don't share the link
Your link carries your username and password in plain sight, so posting it is the same as posting your password. People do it anyway, dropping a full link into a forum or some online "M3U checker" to ask why it's broken, and handing a live subscription to whoever's reading.
Don't. If you have to show it, blank out everything after username= and password=. Provider support can find your account from your details; they don't need the raw link in a public thread.
Quick answers
Why does my M3U URL contain a username and password?
Because an M3U link is how your provider authenticates you: the username and password sit inside the URL itself. That's normal, but it's why the link is as sensitive as a password. Anyone with the full URL can use your subscription, so treat it as private.
Why does the playlist load but no channel plays?
That's a different fault. If the channel list appears, the URL and login are fine, and the problem is with the individual streams. Try several channels: if a few fail it's those sources, if all fail it's usually the provider's streaming servers or your connection limit.
Can I use the same M3U URL in another player?
Yes. The M3U link is your provider's, not the app's, so the same URL works in any compatible player. That makes it a handy test: if the link fails everywhere, the problem is the link or the provider, not seefax.
Should I share my M3U URL with support?
Not in public, and not the full thing. The URL contains your login. If a provider's support needs it they'll ask privately, but never paste a complete M3U link into a forum, a review or a public checker site. Blank out the username and password if you have to show it.
Does it matter whether the link starts http or https?
It can. Some provider servers only answer on one of the two, and a copied link occasionally has the wrong one. seefax retries the other scheme automatically if the first fails; in a player that doesn't, swapping http for https (or the reverse) is worth a try before you write the link off.
