IPTV not working covers a wide range of faults, and the fastest way to fix any of them is to name the symptom precisely. A black screen with sound is not the same fault as a rejected password, and neither is the same as one channel that will not load. This guide starts with a symptom table, then runs the same ten-minute sequence a support agent would use.
The 60-second answer
Restart the app, then the device, then the router. Check the subscription end date. Re-enter your credentials exactly, including the port. Test a second channel group and a second player. Try a mobile hotspot to rule out your line. If none of that changes the symptom, send the details to support rather than reinstalling again.
IPTV not working: which of the five patterns fits?
Most reports fit one of five patterns, and each pattern points at a different layer. Read the table, pick the row that matches what you actually see, and start there instead of working through every possible cause. Guessing wastes more time than testing.
| Symptom | Likely layer | Quick test | Where to go |
|---|---|---|---|
| Black screen, no menu at all | Device, HDMI or power | Press home; if the menu appears, the app is at fault | Section on black screens |
| Black screen with sound | Player or decoder | Change player, disable hardware acceleration | Section on black screens |
| Login failed or credentials rejected | Account or typing | Re-enter the details manually, check the port | Section on logins |
| Only some channels load | Source or group mapping | Test a second channel group | Section on partial lineups |
| Freezing and stutter | Network, cache or device | Wired test on the same device | Buffering guide |
| Audio but no picture, or picture but no sound | Player audio track or HDMI | Switch the audio track, test another channel | Section on audio |
Two minutes with the table usually settles which half of the problem you have: something about your account, or something about your equipment. Everything after that is confirmation rather than diagnosis.
The ten-minute sequence
Run these steps in order and stop as soon as the picture returns. Each step removes one layer, so by the end you can describe the fault to support in one sentence rather than a paragraph of guesses. It takes ten minutes on a device you can reach, and works on a stick, a television or a phone.
- Minute 1: force stop the player and reopen it. Do not clear data yet; just close it properly and relaunch. A surprising number of faults end here.
- Minute 2: restart the device from the menu, not with the remote's standby button. Pull the power if the menu will not respond, wait fifteen seconds, then plug it back in.
- Minute 3: check the app version. Update from the official store if an update is waiting, then reopen the app.
- Minute 4: confirm the subscription is still active. Check the end date in your order details or dashboard before you change anything else.
- Minute 5: re-enter the credentials manually. Type the username, password and server address rather than pasting, and check the port number character by character.
- Minute 6: load a second channel group. If the news group works and the sports group does not, the fault is at the source, not in your home.
- Minute 7: test a second player with the same login. This separates an app fault from a service fault without touching your network.
- Minute 8: run a speed test on the device. Note download, latency and jitter, not just the headline number.
- Minute 9: try a mobile hotspot. If playback works on mobile data, your home line or router is the problem.
- Minute 10: write the report. Device, app, channel, time, error text and what you already tried, sent to support.
If the symptom is stutter rather than a total failure, the sequence above overlaps with the buffering guide, which goes deeper on the network layer. If the picture is fine but the guide is empty, the fault is in the EPG rather than playback, and the fix is a reload rather than a reinstall.
Black screens: with sound and without
A black screen has two forms that point in opposite directions. No menu at all is a device, cable, input or power fault. A menu that appears but a player that stays black is an app fault. Sound with no picture is a decoder or output fault. Check the menu first, because it halves the possibilities.
No menu at all
If the device menu does not appear when you press home, the television is not receiving a picture at all. Work backwards from the HDMI cable before touching the app.
- Press the home button on the remote and wait five seconds.
- Change the television input to the correct HDMI port; many televisions have four and remember the last one.
- Reseat both ends of the HDMI cable, then try a different cable.
- Try the device on another television or another HDMI port.
- If the menu appears but the app stays black, the app is the fault: clear its cache and reopen it.
Stop here if the menu appears and only the player is black. That is an app-level failure, not a dead device. Clearing the cache or reinstalling the player is the fix, and you keep your subscription either way.
Sound but no picture
Sound with no picture is a decoding or output problem, not a network problem. The stream is arriving because you can hear it. The player is failing to render the video, or the television is failing to accept the format.
- Change the channel; if the picture returns, the original stream had a video fault.
- Switch the player's video output or decoder setting: hardware to software, or the reverse.
- Lower the output resolution to 1080p and test again.
- Try a second player with the same login. If the picture appears, the first player is at fault.
Stop here if a second player shows the picture on the same channel. Keep the working player and report the broken one rather than reinstalling the device.
Login failed or credentials rejected
A rejected login is almost always a typing problem, an expired term or a connection count that is already in use. The service is reachable, otherwise you would see a network error rather than an authentication error. Check the three causes in that order.
- Re-enter the username and password by hand, matching upper and lower case exactly.
- Check that you used the playlist URL in the playlist field and the server address in the server field; mixing the two is the most common mistake, and the Xtream Codes guide shows where each field sits in a typical app.
- Confirm the port number if your details include one, and confirm you chose Xtream Codes rather than M3U, or the reverse.
- Check whether another device is already streaming on a one-connection plan.
- Confirm the subscription has not reached its end date.
Stop here if the same credentials work in a different app on a different network. That proves the account is fine and the original app or device is the problem. If the credentials fail everywhere, it is an account issue and support needs the exact error text.
Only some channels work
A partial lineup is the clearest sign of a source problem. Your connection is delivering video, your login is valid and the app is working; individual channels or groups are failing upstream. Nothing you do to your router will change that.
| Pattern | What it usually means |
|---|---|
| One channel fails, neighbours work | That channel's source is down or being worked on |
| One whole group fails | Group mapping or a source cluster problem |
| Sports channels fail on match nights | Source overload at peak demand |
| Channels load but are the wrong region | Playlist variant or a stale list |
| New channels missing from the list | The playlist has not been refreshed |
Refresh or reload the playlist first, because a stale list will not show channels added since you last logged in. If a reload changes nothing and the pattern matches a row above, report the channel names and times. A provider can replace a source quickly once it knows which one failed.
Freezing, stutter and dropouts
Freezing that affects every channel is a network or device problem and belongs in the buffering guide. Freezing on one channel only is a source problem. The distinction is the number of channels affected, not how bad the freeze looks.
Run a wired test on the same device before assuming anything. If the wired test is clean, your Wi-Fi is the cause. If the wired test fails on every channel, work through the twelve buffering causes in order rather than jumping to a support ticket.
Picture but no sound, or sound but no picture
Audio faults are usually track selection or output settings. Many streams carry several audio tracks, and a device set to an unsupported surround format will stay silent while the picture plays perfectly. The fix is almost always a setting inside the player rather than anything to do with your connection or the account.
- Open the player's audio track menu and select a different track, usually stereo rather than 5.1.
- Change the device audio output from surround to stereo PCM.
- Check the television volume and the mute state, then check the device's own volume.
- Change the HDMI cable if audio drops only on some channels.
Stop here if stereo works and surround does not. That is a device or soundbar limitation rather than a stream fault, and leaving the output on stereo is a complete fix.
Error messages and what they usually mean
Error text differs between players, so treat these as patterns rather than exact wording. The useful part is which layer the message points at, because that decides whether you change a setting or open a ticket. Match the pattern to the table, then act once rather than changing three things at the same time.
| What you see | Usual meaning | First action |
|---|---|---|
| Invalid username or password | Typing error, expired term or wrong login type | Re-enter manually and check the end date |
| Connection limit reached | All connections on the plan are in use | Close the stream on another device |
| Network error or timeout | DNS, router or ISP path | Change DNS, restart the router, retest |
| Playlist could not be loaded | Wrong URL, or a temporary server error | Check the URL, then retry in ten minutes |
| No EPG data | Guide URL or refresh problem | Reload the guide, check the timezone |
| Playback failed | Codec or source fault on that channel | Try another channel and another player |
Screenshot the message even if it means nothing to you. Support can usually identify the fault from the wording and the version number in the same frame, which is faster than asking you to reproduce it later.
Is your ISP or router blocking it?
Broadband providers rarely block a streaming service outright, but routers with parental controls, content filters or a stuck DNS cache can. The mobile hotspot test settles it in two minutes: if the service works on mobile data, the block is in your home network.
- Disable content filtering and parental controls on the router temporarily.
- Set DNS to a public resolver and restart the router.
- Test again on the device, not on a phone.
- If a work or campus network is involved, expect the port to be blocked and use a different connection.
Stop here if the hotspot works and your home line does not. The account is fine; the router settings are the fault. Record which setting you changed so you can reverse it.
Has the subscription expired?
An expired term produces several different symptoms depending on the app: a login failure, an empty channel list, or a single channel that loads and then stops. Check the end date before you troubleshoot anything else, because every other test is wasted on a lapsed account.
Your order details show the term you bought and the day it ends. If the date has passed, renewing the account restores access, usually with the same credentials. If the date has not passed and the login still fails, the account may have been reset, and support can confirm that in one message.
Reporting it, and when to start again
Send one message with the device, app, version, error text, channel, time and what you have already ruled out, then wait rather than reinstalling hourly. If the same fault survives a clean install on a second device, stop repairing it and replace the hardware instead of repeating the same steps.
What to include in the message
A precise first message usually saves a day. Support needs to know what you see, on what equipment, at what time, and what you have already ruled out. Without those four things, the only possible reply is a request for them.
- Device make and model.
- Player app and version.
- The exact error text, or a screenshot.
- Channel or group affected, and whether others work.
- Wired or wireless, and your speed test figures.
- Whether a second player or a hotspot changed anything.
Send it to support once, then wait. Reinstalling the app every twenty minutes between messages makes it harder to tell what fixed or caused the fault. If you are still deciding whether to stay, the subscription page sets out terms and what each plan includes.
When replacing beats repairing
Some faults are not worth a third hour. If the app crashes on launch after a reinstall, if the device is more than five years old, or if the same fault returns weekly, replacing the player or the hardware is faster than diagnosing it again. Keep the subscription; the login is portable.
A clean install on a different device takes about ten minutes and tells you more than another hour of settings changes. If that works, you have isolated the fault to the old hardware and can decide whether to replace it or move the stream to another room. The setup guide covers the install order if you are starting from a blank device, and the FAQ answers the shorter questions about accounts and devices.
Related reading
IPTV not working questions
Why is my IPTV showing a black screen?
Why does my IPTV say invalid username or password?
Why do only some channels work?
How do I know if my subscription has expired?
Is my internet provider blocking IPTV?
Should I reinstall the app?
Why does it work on my phone but not my television?
How long should I wait before contacting support?
Still stuck after the sequence?
Send the device, app, channel and error text to support. If you are deciding whether to stay, compare the terms and connection counts first.