In this guide
01Read the exact error before changing anything02Complete a safe login check in the right order03Check the details without exposing them04Make sure the player uses the correct login method05What 401, 403 and 404 mean06Remove a stale session without wiping the player07Work out whether the problem is the account, app or device08Send useful information to support, not your password09Avoid actions that make the login problem worseRead the exact error before changing anything
Player messages are not completely standardised. Two apps may describe the same server response differently, so write down the exact wording and any number shown.
Also note whether the error appears before the library opens, after the library opens or only when a stream starts. A login failure, an account-permission problem and an individual playback error require different checks.
Common messages and what they suggest
- Incorrect username or password: a credential, capitalisation or hidden-space problem is likely.
- 401 or unauthorised: the server did not receive acceptable authentication.
- 403, forbidden or access denied: the server understood the request but is refusing access.
- 404 or not found: the server path or portal address may be incorrect or obsolete.
- Connection failed, timed out or server unavailable: investigate the address, internet connection and service status before changing the password.
Complete a safe login check in the right order
- Confirm that the app came from its official store listing or the provider's verified download page.
- Check that the device date, time and time zone are set automatically.
- Confirm the required login method: account credentials, an M3U address or a device portal pairing.
- Compare the complete server address, including its https prefix, punctuation, port and path where supplied.
- Check username and password capitalisation and remove spaces accidentally added at the beginning or end.
- Confirm through the authorised account or provider that the service is active and the device or connection allowance is not exceeded.
- Close duplicate sessions on devices you are not using, wait briefly, then make one carefully checked attempt.
- If the same response continues, stop retrying and collect diagnostic details for support.
Check the details without exposing them
Credentials may be case-sensitive. A zero can be mistaken for the letter O, and copied text can include an invisible space. Use the player's local reveal-password control privately if it provides one, then hide the value again.
Do not post a login screenshot or send a complete playlist URL in a public group. An M3U address may contain a username and password inside the URL even when they are not shown as separate fields.
If details may have been exposed, use the official account recovery route or ask the authorised provider to replace them. Update saved details on your own devices after the change.
Make sure the player uses the correct login method
Username, password and server address
Enter the server address in the server field and the credentials in their separate fields. Do not add an M3U path to a field that expects only the server base address. Preserve the port number when one was supplied.
M3U playlist address
Use the complete authorised playlist address in an M3U-compatible field. Avoid editing individual query parameters unless the provider has issued a corrected link. Because the address may contain credentials, treat the entire URL as private.
Device portal, MAC address or device key
A device portal pairs the player with a registered device identity. Confirm that the displayed MAC address and device key belong to the current installation. Reinstalling the app or changing devices can produce a different identity, which may require an authorised replacement in the portal.
What 401, 403 and 404 mean
These meanings follow the HTTP standard, but a player may replace the number with a shorter message. The response narrows the investigation; it does not by itself reveal the account-specific cause.
401 unauthorised: authentication was not accepted
Despite the wording, a 401 response is normally an authentication problem. The request may be missing a valid login, token or session, or saved credentials may no longer match the account.
Recheck the exact credentials and login method once. If a password or subscription recently changed, sign out where possible or clear only the app cache before trying the newly issued details.
403 forbidden: the request is recognised but refused
A 403 response is not proof that the password is wrong. The account may lack permission for that request, the authorised-device allowance may be full, the subscription may require attention, or a server security rule may be rejecting it.
Do not attempt to evade the response with a VPN, proxy, modified application or repeated retries. Those actions can conceal the actual cause or conflict with service rules. Ask the authorised provider to confirm account, device and connection status.
404 not found: check the destination
A 404 response means the requested server path was not found. Compare the complete portal or playlist address with the latest details issued by the provider. Do not guess alternative domains or download replacement configurations from search results.
Timeout or server unavailable
Test whether ordinary websites work on the same device and restart the router only if the broader connection is affected. If login fails on every network and device, record the time and ask the provider about service status rather than changing the password repeatedly.
Remove a stale session without wiping the player
If the details are correct but the player continues to reuse an old session, sign out through the app where possible, force-stop it and clear its cache. Reopen it and enter the verified details once.
Clear app data only when the correct setup information has been retained securely. This action may remove every locally stored playlist, favourite and preference.
Work out whether the problem is the account, app or device
The login fails on every authorised device
This points towards account details, subscription status, connection allowance or the provider endpoint. Stop repeated attempts and ask the provider to verify the account using a redacted reference.
The login works elsewhere but fails in one app
Check that app's login method, version, cached session and server-field format. Do not assume that details formatted for one player can be pasted unchanged into a different type of login screen.
The login works on one network but not another
Record the networks and exact responses, then contact the provider. Do not use a VPN to force access. The provider can determine whether a security or account rule is involved without exposing your credentials.
Send useful information to support, not your password
A concise diagnostic report allows support to investigate account and server records while keeping private details private. Use only the support channel published on the official website.
- The exact error text and number.
- The date, local time and time zone of the latest attempt.
- The device model, operating-system version, app name and app version.
- The login method used, without the password or complete playlist URL.
- Whether the problem affects one device, one network or every device.
- Whether the library ever opens and, if so, where failure begins.
- The last approximate time the same setup worked.
- A redacted account or order reference if support requests one.
Avoid actions that make the login problem worse
- Do not keep retrying; automated protection may temporarily limit repeated attempts.
- Do not buy replacement credentials from someone claiming to fix a 403 response.
- Do not install a modified player or disable device security.
- Do not publish screenshots containing playlist addresses, usernames, QR codes or device keys.
- Do not reset the whole device until the login method and account status are checked.
- Do not assume a 403 can be safely bypassed; it requires an authorised explanation.
Frequently asked questions
My password is correct, so why do I receive a 403 error?
A 403 response is an access decision, not necessarily a bad-password message. The provider may need to check the subscription, device registration, connection allowance or a server security rule. Do not try to bypass it.
Can a VPN fix an IPTV 403 error?
It should not be used as a workaround. A VPN can hide the original diagnostic signal, create another access conflict or breach service rules. Record the exact response and ask the authorised provider to investigate.
How many times should I retry a failed login?
After checking the login method, address and credentials, make one careful attempt. If the same error returns, stop. Repeated guesses can trigger temporary protection and make diagnosis harder.
Should I clear app data when the login stops working?
Clear cache first. Clearing app data can remove every saved server, playlist, favourite and login. Use it only when you have securely retained the correct setup details.
Why do I still get 401 after changing my password?
The player may hold an old session or password. Sign out if possible, force-stop the app, clear its cache and enter the newly issued details once. If it continues, ask the provider to confirm the change is active.
How can I tell whether the service is unavailable?
Check whether the same verified details fail on another authorised device and network, then note the exact time and message. If every setup fails, contact the provider with redacted diagnostics rather than resetting each device.