This is the first test because it splits the problem in half. Copy the playlist or portal address into a different player — VLC on a laptop is enough — and load it there. If the list appears and a channel plays, the source is healthy and the fault is local: a cached list, a decoder limit, or a version regression. If the second player shows the same empty list or the same authorization error, stop adjusting app settings. The line, the credentials, or the connection cap is responsible, and only the service can change any of those. Two minutes here saves an hour of reinstalling and re-entering details.

An empty list with no error message is how most players report a failed fetch. Three things produce it. The address expired or changed, so the server returns an error page the parser reads as zero channels. The account's connection slots are consumed, and portal logins get refused before any list is sent. Or the app kept a cached response and is showing you yesterday's failure. The reliable repair is to delete the playlist entry entirely and add it again with a freshly issued address, rather than pressing refresh, because refresh frequently re-reads the cached copy. Type the address by hand once as well, since a truncated paste looks identical on screen.

They look the same and they are not. Authentication failures are consistent: the same credentials fail on every device, at every hour, immediately. Capacity failures are intermittent and time-shaped — they cluster in the evening, they clear after a few minutes, and they often follow a crash on another device that left a session open server-side. Plans commonly allow between one and five simultaneous connections, and a crashed player can hold one of yours for several minutes after it closed. Shut every player everywhere, wait five minutes, then sign in on a single device. If that works, capacity was the cause and you need fewer active devices or more slots.

Two, in practice. Set the buffer to none so a stall surfaces immediately instead of hiding behind pre-load, and point the device at a public DNS resolver so segment requests are not queued behind a slow lookup. After that, the decoder toggle matters on older hardware: HEVC runs at about half the bitrate of H.264, which saves bandwidth but needs a decoder that supports it. Hardware that cannot decode it shows a black screen with audio, or closes the app outright, and software decoding fixes that at the cost of processor load. Hiding groups you never open is worth doing separately, since large lists destabilize players above roughly 18,000 visible channels.

After an update, and rarely before. Post-update regressions are a real recurring cause: a new build changes how playlists are parsed or which decoder path is chosen, and a setup that worked all year breaks the same evening on thousands of devices at once. If the failure began right after an app update and the same address plays in another player, roll back to the previous version or use a different player until a fix ships. A reinstall done before you have checked scope, cross-player behavior and connection slots simply resets your settings and loses your list, then leaves the original cause untouched.