By the LotinTV support team · Last updated 21 September 2026
The short answer: when IPTV stops working completely, start with the account details, subscription status, connection limit, and playlist information before changing network settings or reinstalling anything. A second device and a mobile hotspot can then tell you whether the problem stays with the device, the home network, or the service.
That order matters.
A lot of troubleshooting guides begin with “restart your router” because it is easy advice to give. It is not always the best first check. If the account has expired, the server address is wrong, or another device is already using the same connection, rebooting the router changes nothing.
There is also an important difference between IPTV not working and IPTV buffering. If the app opens and channels play but the picture repeatedly freezes, drops quality, or spins every few minutes, use our IPTV buffering troubleshooting guide instead. This guide is for the more basic failure: the app cannot load, channels will not start, the playlist is empty, or playback fails altogether.
Before changing a setting, test three channels from three different categories.
That ten-second check tells you more than a reinstall.
If every channel fails, the possible causes include your login details, account status, connection limit, network path, player, or the service itself.
If one channel fails while several unrelated channels play normally, the problem is more likely to be specific to that stream. That can mean a source outage, a channel-side configuration problem, or a compatibility issue with that particular feed. There is no reason to reset your whole device before testing another channel.
The same rule applies to picture quality. A 4K stream failing while an HD version works does not automatically prove that the provider is down. Higher-resolution streams place different demands on the connection, device, decoder, and source.
For more on device and format compatibility, see our IPTV device compatibility guide.
Use the symptom that looks closest to your problem, then start with the first check rather than changing several things at once.
| What you see | Most likely area | First check |
|---|---|---|
| Every channel fails on one device | Device, player, credentials, or network | Test the same line on another device |
| Every channel fails on multiple devices | Account, network, or provider | Check account status, then run the hotspot test |
| Playlist is empty or will not load | URL, login format, or player | Re-check the M3U/server details |
| Works on mobile data but not home Wi-Fi | Home network or DNS path | Test another device on home Wi-Fi, then DNS |
| Works in the morning but not later | Congestion, routing, or service load | Compare the same channel at two different times |
| One channel fails while others play | Individual stream or source | Test several other channels |
| Second device cannot connect | Connection limit or session issue | Close other active sessions |
| App opens and closes or shows a blank screen | App, cache, update, or decoder | Force-stop, clear cache, then update |
| TV says “No Signal” | HDMI/input/device connection | Check the HDMI input and cable |
The important point is that these are working hypotheses, not guarantees. The test result should decide what you do next.
This is the first thing to check because a single incorrect field can stop the entire service from loading.
The mistake is not always the password. Depending on the setup, the player may also need a server address, port, protocol, or playlist URL. One missing character can be enough to make a perfectly valid account appear dead.
This becomes especially common after:
changing to a new device
reinstalling the IPTV player
restoring an old backup
entering a long URL manually
switching between M3U and login-based setup methods
What to do:
Delete the existing entry and add it again using the information supplied by your provider. Copy and paste whenever the device allows it.
Check the complete value rather than only the username and password:
Server address
Port, if one is supplied
Username
Password
M3U URL, if applicable
http or https, if specified
Do not “fix” a URL by guessing what it should look like.
If your setup uses an M3U playlist, our M3U playlist guide explains how the playlist fits into the player.
An expired account can look almost identical to a server outage because the result is often simple: nothing loads.
Check the actual account status rather than relying on memory or a payment notification. Trial access can also have a defined activation window, so “I only started testing it yesterday” does not necessarily tell you whether the line is still active.
What to do:
Open your account or dashboard and check:
Expiration date
Activation date
Current status
Trial end time, when applicable
If the account is inactive, there is no device setting that will bring the channels back.
A connection limit is easy to overlook because it does not always look like a connection problem.
Suppose your plan allows one simultaneous stream. One TV is already watching, and somebody opens the same line on a phone or another television. Depending on the provider and player, one session may be rejected, disconnected, or prevented from starting.
From the sofa, that can look like an outage.
What to do:
Close the IPTV player on other devices in the house, including:
phones
tablets
spare TVs
Fire TV devices
Android TV boxes
computers
Then test again on the device you actually want to use.
If the household needs more than one stream at the same time, the issue is not a cache setting. It is a plan and connection-capacity question. You can review the available connection options in the IPTV server collection.
Some IPTV setups depend on a playlist URL or portal address. If that address changes, an older configuration may stop loading even though the account itself is still active.
This can happen after a provider changes infrastructure, replaces an endpoint, or asks users to migrate to a new server address.
A useful distinction here is between “the URL can be reached” and “the URL contains working streams.” Opening an M3U link in a browser may show text, download a file, redirect somewhere else, or return an error depending on how the server is configured. None of those responses alone proves that every stream in the playlist is healthy.
What to do:
Check the latest setup information supplied by your provider.
If you have been told that the server address or playlist has changed, replace the old entry instead of creating multiple duplicate playlists.
This is obvious, but it is still worth checking early because it can be ruled out quickly.
Do not test the internet by looking only at the Wi-Fi icon. Open another unrelated online service on the same device.
For example:
Open a website on a computer.
Open a video service on the TV or streaming box.
Open an online app on the phone or tablet.
If several unrelated services are failing on the same device, IPTV is probably not the root problem.
If everything else works normally, move to the next check.
This is the most useful isolation test in the article because it changes the network path without changing your IPTV account.
Take a phone with mobile data.
Turn on the phone's personal hotspot.
Connect the streaming device to that hotspot.
Open the same IPTV channel that failed on your home network.
Give the stream some time to establish before judging the result.
Test an HD channel first if possible, so the comparison is not distorted by a particularly heavy 4K stream.
Then compare the results.
| Home Wi-Fi | Mobile hotspot | What the result suggests |
|---|---|---|
| Fails | Plays | Investigate the home router, Wi-Fi, DNS, or ISP path |
| Fails | Fails | Investigate account status, credentials, connection limits, device/app issues, or the service |
| Plays | Plays | The original issue may have been temporary or device/network specific |
| One channel fails on both | Other channels play | Investigate that individual stream |
There is one important limitation: a hotspot test proves a path difference, not automatically a provider fault.
Mobile data can have lower or more variable throughput than a home broadband connection. A high-bitrate stream may therefore fail on the hotspot even though the underlying IPTV account is working.
That is why a second channel and, where possible, a second device make the test more useful.
A useful report contains evidence, not just “IPTV not working.”
Send:
The exact time the failure occurred and your time zone.
The channel names that failed.
Whether other channels played.
The player app and version.
The result of the hotspot test.
A screenshot of any error message.
That lets support start at the correct layer instead of asking you to repeat the same basic checks.
When IPTV works on mobile data but not on your normal home connection, DNS is one possible explanation.
DNS is responsible for translating a domain name into an address that the device can connect to. Cloudflare documents 1.1.1.1 as a public DNS resolver and provides instructions for configuring it on routers and individual devices.
A DNS problem can appear as:
endless connection attempts
server lookup failures
timeout messages
a playlist that suddenly stops loading
What to do:
Start with the simplest comparison.
First, restart the router and test again.
If the same IPTV line still works on mobile data but fails on home Wi-Fi, try changing the DNS resolver on the router or device to a public resolver such as:
Cloudflare: 1.1.1.1
Cloudflare secondary: 1.0.0.1
Google: 8.8.8.8
Cloudflare notes that changing DNS at the router level applies the setting to devices on the network, although exact menu names vary by router.
After changing DNS, restart the relevant network connection and reopen the player.
Do not assume that DNS is always the explanation just because the hotspot works. If changing DNS makes no difference, move on.
This category needs more caution than most IPTV troubleshooting articles give it.
A stream that works perfectly at one time and fails repeatedly during busy periods can be affected by:
household network congestion
local Wi-Fi congestion
ISP congestion
routing problems
traffic-management policies
increased load on the streaming service
The pattern matters more than the label.
For example, compare the same channel:
on the same device
at roughly the same quality
once during a quiet period
once during the period when the problem normally appears
A useful result might look like this:
Stable at midday, unstable every evening on home Wi-Fi and multiple devices: investigate congestion, routing, or service-side load.
Stable on mobile data but unstable on home broadband: the home network or ISP path moves higher on the list.
Unstable on both networks: look back at the account, player, device, or service.
A VPN can sometimes be used as an additional comparison because it changes the network route, but a different result does not by itself prove that an ISP is throttling the service. The VPN itself can introduce overhead or a slower route.
For a more general view of latency under load, the Waveform Bufferbloat Test can help show whether your connection becomes significantly less responsive when the line is busy.
Sometimes the service is fine and the app is the part that has changed.
This becomes more plausible when:
another player works on the same device
the same account works on another device
the app was recently updated
the operating system was recently updated
the app opens but content will not load
the interface becomes blank or unstable
Start with the least destructive fix:
Force-stop the player.
Clear its cache.
Reopen the player.
Check for an app update.
Test the same line again.
On Android TV and Google TV, clearing an app's cache is a standard troubleshooting step documented by Google. Exact menu names can vary by device and software version.
If that does not help, test the same line in another compatible player.
That comparison is useful because it changes the software while keeping the account and, ideally, the network unchanged.
For device-specific setup guidance, see our Fire TV setup guide or Android TV setup guide.
Only after you have checked the account, credentials, connection limit, device, network, and player should you settle on a service-side fault.
A provider-side issue becomes more likely when:
the account is active
the login details are correct
the connection limit is not being exceeded
the same line fails on a second device
the same line fails on a different network
several unrelated channels fail
the problem persists after basic player checks
There is also a difference between a service-wide problem and a single-stream problem.
If one channel fails while other channels continue playing, report that channel.
If many unrelated channels fail across devices and networks, report the wider outage pattern.
The goal is not to prove the provider wrong or right from your living room. The goal is to eliminate the variables you can actually control.
Error messages are often useful clues, but they rarely identify only one possible cause.
| Message | What it may indicate | What to check first |
|---|---|---|
| Authentication failed | Login details or server information are wrong | Re-enter the full login information |
| Invalid username or password | Credentials are incorrect or not being accepted | Verify username, password, URL, and port |
| Too many connections | Another session is using the line | Close other active devices |
| Subscription expired | Account access has ended | Check the account status and expiry date |
| Playlist not found / 404 | Playlist address is unavailable or incorrect | Verify the current M3U/playlist URL |
| Connection timeout | The device cannot establish the connection | Run the hotspot test |
| Stream not available | A particular stream is unavailable | Test other channels |
| Empty channel list | Playlist, server response, or player issue | Check URL and login method |
| Endless spinner | Network, player, decoder, or stream issue | Compare another channel, player, and network |
The key phrase here is “may indicate.” A player error is evidence, not a complete diagnosis.
When the same account works elsewhere, stop changing the account.
The problem is now more likely to be the device, player, local configuration, or connection used by that device.
| Device | Start here | Then try |
|---|---|---|
| Fire TV / Firestick | Force-stop the player and clear its cache | Update or reinstall the player, then add the line again |
| Android TV / Google TV | Clear the player's cache | Clear app data or reinstall if necessary |
| Samsung / LG Smart TV | Restart and update the player | Reinstall the app from the TV's supported store |
| iPhone / iPad / Apple TV | Restart or sign out of the player | Update or reinstall the app |
| MAG / Stalker portal | Check portal details and registered device information | Re-enter the portal configuration |
| Windows / Mac / VLC | Test the playlist or server information again | Re-download the playlist or try another player |
Exact settings differ by operating system and application, so avoid publishing one rigid menu path as though it applies to every device.
Google's own troubleshooting guidance recommends clearing app data/cache and leaving a factory reset until other troubleshooting steps have been attempted.
A surprising number of “IPTV problems” are actually television or device problems.
If the television says No Signal, check the HDMI input and cable first.
The TV menu working normally tells you that the television itself is on. It does not tell you that the external streaming device is sending a usable signal.
Some streaming devices appear unresponsive after standby. Press Home and check whether the device interface responds before changing anything.
A hot streaming box or stick can produce odd behavior, including crashes, playback failures, and random restarts. Give the device enough ventilation and remove it from enclosed spaces where possible.
Do not post your IPTV username, password, M3U URL, or portal details in public forums or send them to unofficial “checking” websites.
Those details may provide access to the account.
If somebody suddenly asks you to send money to “unlock” a line, first confirm that the request is coming through the provider's official support channel and that the charge is actually part of the service terms.
Do not assume that a payment request is legitimate simply because the person claims to be support.
A factory reset removes apps, settings, and account information. It should be a last resort, not the opening move. Google also places factory reset after less destructive troubleshooting steps.
If you clear the cache, change DNS, reinstall the app, switch Wi-Fi bands, and change the player at the same time, you will not know what actually fixed the problem.
Change one variable, test it, then continue.
Check the expiry date, credentials, connection limit, and current server information first.
A hotspot test is useful because it tells you whether changing the network path changes the result. That is more informative than changing DNS at random.
A third-party checker asking for your full credentials deserves caution. Use the provider's own dashboard or support channel whenever possible.
Work through these in order.
Yes: focus on the original device or player.
No: continue.
Yes: investigate home Wi-Fi, router, DNS, ISP routing, or congestion.
No: continue.
No: fix the account status.
Yes: continue.
No: replace them with the current values.
Yes: continue.
No: investigate the individual stream.
Yes: with the same result on another device and network, contact support with the evidence you collected.
This is much more useful than asking “Is the server down?” before you have eliminated the variables on your side.
At this point, you have already done the useful customer-side diagnosis.
Send support:
the account identifier they need to locate the line
the exact time of the problem
the affected channels
the player and device
the home-network result
the hotspot result
any error screenshot
Then stop changing settings until you receive a response.
Repeated reinstallations, router resets, DNS changes, and new player installs only make the history harder to follow.
If the same failure keeps returning after the service recovers, that is a separate question. Repeated outages can point to recurring problems with the service, routing, account configuration, device compatibility, or connection capacity. At that stage, it is worth looking at the service over several viewing sessions rather than judging it from one successful afternoon.
Our guide to choosing an IPTV service covers the practical factors to compare before subscribing, while the IPTV server collection shows the available server options and connection details.
Start by checking the account status, connection limit, credentials, and current server information. If the same line also fails on another device and another network, a service-side problem becomes more likely.
That result points toward something in the home network path. Check the router, Wi-Fi connection, DNS settings, and possible ISP-side routing or congestion.
You cannot confirm a provider outage from one failed channel alone. Test several unrelated channels, then test the same line on another device and another network. If the account is active and the same failure follows the line across those tests, contact support with the results.
The player may be rejecting another part of the login configuration, such as the server address, port, protocol, or playlist method. Delete the existing entry and re-enter all required fields from the current provider information.
Yes. If the plan limits simultaneous streams, opening the same account on additional devices can prevent a new session from starting or cause another session to disconnect.
It can, especially when the problem is local to the router or network. It is not a universal fix, though. Check the account, credentials, and device before assuming the router caused the problem.
A single channel failing while unrelated channels continue to play usually points toward that stream or its source. Test several other channels before changing your account or device settings.
Only when DNS is part of the problem. A useful clue is when the same line works on mobile data but fails on your home network. Changing DNS is a troubleshooting test, not a guaranteed fix.
The account may be fine while the second device has a player, cache, decoder, operating-system, or local-network problem. Test the same line on both devices before making account changes.
Not immediately. Force-stop it and clear the cache first. If another compatible player works with the same line on the same device, reinstalling or replacing the original app becomes a more reasonable next step.
