Skip to content
CatchON TVCatchON TV

Troubleshooting

CatchON TV “Failed to Authenticate”: How to Fix It

By CatchON TV Support TeamPublished

A TV login form with a username, password and server field, a key icon and a red error mark
On this page
  1. What the error means
  2. Fix it in this order
  3. Getting the server URL right
  4. Similar error messages
  5. The two-minute browser test
  6. Still failing?

“Failed to authenticate” means your player app reached the CatchON TV server but the server didn’t accept the login. The usual causes are a typo in the username or password, an incomplete server URL (missing http:// or the port number), an expired plan, or more devices playing at once than your plan allows. Check them in that order.

What does “failed to authenticate” mean?

When you sign in, the player sends your username and password to the server address you entered and asks for the channel list. If the server rejects the request, or can’t be found at that address, the app shows an authentication error. Player apps word it differently, but the causes are the same.

Fix the CatchON TV login in this order

  1. Copy the details again. Don’t retype them

    Usernames and passwords are case-sensitive. Copy them from your activation message. Look out for a space pasted at the end, a capital O instead of a zero, or a lowercase l instead of a capital I.

  2. Check the server URL format

    Include the full address exactly as sent: http:// or https://, the domain and the port (for example :8080). See the table below.

  3. Check the plan hasn’t expired

    An expired account is rejected exactly like a wrong password. Many players show an expiry date in the account or user-info screen. If not, ask support.

  4. Stop playback on other devices

    If your plan covers one screen and another device is playing, a new sign-in can be refused. Close the app on the other device, wait a minute and try again. Need more screens? Plans for up to four devices are on the pricing page.

  5. Check the device’s date and time

    Secure (https) connections fail when the device clock is far off. Set date and time to automatic.

  6. Remove the playlist and add it again

    Some apps cache a failed login. Delete the playlist or user profile, restart the app and add it fresh.

Getting the server URL right

Server URL examples (placeholder domain)
Entered asResultWhy
http://example.com:8080CorrectProtocol, domain and port, exactly as sent
example.com:8080Often failsSome apps need the http:// prefix
http://example.comFailsMissing port, so the app connects to the wrong service
http://example.com:8080/Sometimes failsSome apps don’t accept a trailing slash
https://example.com:8080Fails if the server expects httpUse the protocol you were given

Similar error messages

MessageMost likely meaningFix
Invalid username or passwordTypo or wrong caseSteps 1 and 6
Account expired / inactivePlan ended or not yet activatedRenew or ask support to check activation
Max connections reachedToo many devices playing at onceStep 4, or a plan with more devices
401 UnauthorizedServer rejected the loginSteps 1 to 3
403 ForbiddenAccount blocked, or the network blocks the serverTest on mobile data; contact support
Failed to connect / server not respondingWrong server URL or port, or a network problemStep 2; test on another network

The numbers come from the web’s HTTP standard. A 403 means, in the specification’s words, that “the server understood the request but declines to fulfill it” (RFC 9110), so the details reached the server and were refused. A connection error, by contrast, means the app never reached the right server at all.

The two-minute browser test

Open your M3U link in a browser on a computer or phone. If it downloads a text file beginning with #EXTM3U, your account works and the problem is how the details were entered in the app, or the app itself. If you get an error page, the account or the link is the problem. Send support a screenshot of that page.

Still failing?

Send support the app name, the exact error text and a photo of the login screen with the password hidden. If the login works but the picture stalls, the problem is speed, not authentication. See CatchON TV buffering fixes. For anything else, the CatchON TV troubleshooting guide lists every common symptom.

Sources

  1. RFC 9110: HTTP Semantics (status codes 401 and 403) — IETF / RFC Editor (accessed )
  2. M3U — Wikipedia (accessed )

Still stuck after these steps? Send support your device model, app name and a photo of the error.

Contact support