A structured way to identify and fix access is forbidden after the request reaches the server without changing random settings or exposing private credentials.
Fix access is forbidden after the request reaches the server with a structured UK troubleshooting process covering credentials, apps, devices, Wi-Fi, broadband and source-side faults.
HTTP 403 means the server understood the request but refused access. It is different from a wrong-password 401 error.
The account may be disabled or limited.
Too many simultaneous sessions may be active.
The service may apply location or network rules.
A playlist or stream link may no longer be valid.
Close and reopen the player, then restart the device if necessary.
Use a compatible second player to isolate app-specific settings.
Test the same authorised account without changing the home network.
| Test | Result | What it suggests |
|---|---|---|
| Works in a second player | First player fails | Application configuration or decoder is likely involved |
| Works on a second device | First device fails | Hardware, storage, OS or local app issue |
| Works on another connection | Home broadband fails | Wi-Fi, router, DNS or ISP path is involved |
| Fails everywhere | All comparisons fail | Account, source or provider-side issue is more likely |
Send useful evidence instead of only saying that it does not work.
Use the next guide that matches your device, application or symptom.
Compare authentication failure.
Read guide →Check device and connection differences.
Read guide →Test account-wide availability.
Read guide →
