A loaded playlist proves that the player received some catalogue information. It does not prove that every media source is reachable, available or compatible with the device. When categories and programme names appear but playback fails, keep that distinction in mind. Replacing the login immediately can remove useful evidence and introduce a second problem before the first one is understood.
Record the exact failure point
Open one authorised programme and note what happens. Does the player show a specific error, return to the catalogue, display a black screen or wait indefinitely? Does audio start? Record the name, time and app version. A catalogue-loading success followed by a repeatable playback error is a much clearer report than “the account does not work”.
Try a second source from the same account, where your access permits it. If one plays and another does not, report the difference. A missing film, unavailable channel or changed source can be narrower than a whole-account problem. Avoid claiming that every programme is unavailable after checking only one item.
Check simultaneous use
Confirm the connection allowance of the content subscription. Stop playback on other devices before testing again. A closed app window may not always mean a previous session ended immediately, so follow the provider’s guidance if it reports a connection limit. Do not repeatedly open the same source on several screens to test it at once.
If you compare another device, keep the same authorised account and source but use one active test at a time. A success on another screen suggests that device or player compatibility deserves attention. A failure on both screens still needs interpretation; the connection or source may be shared between them.
Keep network tests controlled
Check ordinary internet access and compare another authorised app on the same device. If the device cannot reach anything, investigate its network connection. If other apps work, do not assume that internet access alone proves the specific source is reachable. Different services can use different delivery paths and formats.
Where practical, try a lower available quality or another supported playback option documented by the player. Record the original setting and restore it if no improvement appears. Avoid unknown codec packs, unofficial app copies and random server-address changes. Those actions can complicate the diagnosis and expose private information.
Escalate before deleting the setup
- Include whether the catalogue loads successfully.
- Name two tested sources and their different results.
- State whether another device was tested with other sessions stopped.
- Copy the error text without including private credentials.
- Mention any recent app, device or network change.
Do not delete favourites or reorganise the catalogue while the playback fault is being investigated. Keeping the saved setup stable makes repeated tests easier and preserves the programme references you may need to report. Once the cause is known, you can tidy the catalogue without confusing the diagnosis.
Our playlist troubleshooting page explains the catalogue side of the process. For actual pauses after playback starts, use buffering help. If you need a different supported player, start with the player selection guide and confirm compatibility before reinstalling. Preserve the working connection details securely until support has identified a reason to change them.
Build a small playback test without losing the saved source
When programme names appear, something in the connection process has already succeeded. Preserve that evidence. Keep the saved source, note which categories loaded and choose one authorised item to test. The next goal is to identify what happens between selecting that item and seeing or hearing media. A clear description of that transition is more useful than repeatedly entering the same login.
Describe what the screen and sound actually do
A black picture with audible dialogue is different from a spinner with no sound. A player returning immediately to the catalogue is different from playback beginning and later pausing. Write down the sequence in ordinary words. Include any error message exactly, provided it does not contain credentials. If the app closes, state that too; do not call every failure a buffering problem.
Repeat the same selection once to see whether the result is consistent, then test another authorised item. Avoid opening many streams in quick succession. Keep the tests small enough that you can remember which result belonged to which source. If only one fails, record the title, channel label or version. If both fail, note that result without claiming the entire catalogue has been checked.
Keep account limits out of the comparison
Stop playback on other household devices before comparing another screen. Check the subscription's actual connection allowance with the provider. A successful catalogue load does not necessarily mean that another simultaneous stream is permitted. If the player reports a connection limit, follow the provider's documented guidance rather than repeatedly trying to start more sessions.
Use one active comparison at a time. Note whether the previous device was stopped and which source was tested next. This makes a result on another device more meaningful. Otherwise, a second screen might fail because the first test was still active, creating an apparent compatibility problem that the comparison did not actually establish.
Separate a source problem from a device problem
If one item works and another does not in the same player, keep the successful item as a reference. Compare their visible characteristics only where the app supplies them, such as the available quality or audio options. Do not infer technical details from the title alone. Report the narrow difference to the content provider before changing the account's server address.
If the same authorised item works on another supported device with other sessions stopped, record the player versions and the relevant playback settings. That comparison can direct attention towards the first device's supported format or configuration. It does not prove which single setting is responsible, and it does not justify installing unverified software. Ask for a supported next step based on the evidence.
Use network checks for the question they answer
Opening another website or app can show that the device has ordinary internet access. It cannot establish that every media endpoint used by a particular source is reachable. Similarly, a general speed test is context rather than a guarantee about sustained playback. Compare the failing source under clear conditions, without treating one unrelated successful connection as a complete diagnosis.
Where practical, compare a stable wired arrangement with the usual Wi-Fi connection, keeping the same device and player. Do not change several router options at once. If you use a managed or shared network, ask its administrator before altering configuration. A test should leave the household with a known working network arrangement, not an unexplained collection of permanent changes.
Try supported playback options carefully
The player may provide an alternative playback engine, decoding option or available quality. Consult its own documentation before changing one. Record the starting value and test the same source afterwards. If the option makes no useful difference, return it to the original state. A change that helps one item may affect another differently, so check more than a menu preview.
Avoid downloading random codec packs, unofficial app copies or “repair” utilities. The problem has not established a need for them. Also avoid clearing all application data before confirming that recovery information is retained. Deleting a correctly loaded source can turn a playback investigation into a new sign-in problem and remove the references that support needs.
Escalate with a concise result table
List each tested item, whether the catalogue loaded, whether sound began and the final screen or error. Add whether the test used the normal network and whether other sessions were stopped. Include the device model and player version once. This short record gives support a repeatable starting point without sharing a private playlist address or full login form.
After an agreed correction, repeat the original test and one comparison source. Confirm the actual result before reorganising favourites or removing old entries. If playback begins but later pauses, switch to the buffering investigation. If the app asks about a licence, use the expiry explanation. Keep each troubleshooting step connected to the stage that is failing.
Recent changes can provide useful context without proving the cause. Note whether the fault began after an app update, a new device, a router replacement or a change to the saved source. Keep the order of events clear. If you changed several things while investigating, separate those later experiments from the original symptom. This prevents a support conversation from treating an attempted fix as though it were the initial failure, and helps you identify which previous configuration should be restored when a test makes no improvement.