Symptom first, fix second

Reading the error instead of guessing at it

Players describe very different conditions with almost identical wording, which is why so many threads start with the wrong fix. This page maps the messages people actually paste in here onto the thing that is really happening, and says which of them you can clear yourself.

Refused, timed out, or nothing at all

Three shapes cover most of what you will see. A refusal is fast and definite: the server answered and said no, which makes it a credentials story. A timeout is slow and vague: nothing answered in time, which makes it a host or network story. Silence, meaning a spinner or a black screen with no text, usually means the app gave up before it had anything to report. Sort your error into one of those three before you change a single field, because the fixes do not overlap.

Invalid credentials, and its three causes

In order of likelihood: the line reached its expiry date, the line was reissued and the old pair retired the instant the new one existed, or another device on your network is already connected with the same username and the server is refusing the duplicate. Test the same credentials in VLC on a laptop to take the app out of the picture, then rule out the duplicate by checking who else in the building has the app open. What is left is a question for support, and it is answered in one reply if you say which two you eliminated.

Expiry reads as a clean stop, not a stutter

An expired line does not degrade. It fails on every channel, on every device, at a single moment, usually with authentication wording rather than a buffering symptom. That pattern is worth memorizing because it saves the classic wasted evening: host after host tested against a line that ran out at lunchtime. Establish that the line is still live before any other test, and no host swap will ever contradict that result.

The error that is really the other TV

Concurrency messages are the most misread of the lot, partly because apps word them so differently. Some say the maximum connection count was reached, some report an authentication failure, and some simply stop the picture with no explanation at all. What they share is timing: the failure lands exactly when somebody else started watching. If a fault appears at the same time every evening and clears when the house is empty, stop reading the message and count the screens.

Silent failures with no message at all

A spinner that never resolves, a black screen that holds, an app that exits to the home screen. These carry the least information and people therefore assume the worst about them. Treat them as ordinary connection failures: try a second channel, then a second host, then the same credentials in VLC. If VLC produces an actual error where the TV produced silence, the message you needed was there all along and the player was hiding it.

Why one fault has four different wordings

Players write their own text on top of whatever the server returned, and that translation loses detail. Two apps on the same device can describe one refusal as an account problem and as a network problem respectively. This is why we ask for the message character for character rather than in your own words: the exact string identifies which app produced it, and that tells us how much to trust it. When two apps disagree about the same line, the more specific message is usually the honest one.

Questions

The app says invalid credentials and I changed nothing.

Expiry first, reissue second, a duplicate connection from your own network third. Test in VLC on a laptop to eliminate the app, then check who else is watching. That is two of the three ruled out in five minutes.

Connection timed out on every channel.

Change host before anything else and replay the channel that failed. A timeout everywhere with a working browser on the same network points at the door you are knocking on rather than at the credentials behind it.

Connection timed out on one channel only.

That is the source behind that channel, not your line. Try it on a second host to confirm, then report it by exact name and category. Everything else playing normally is the evidence that nothing on your side needs touching.

Spinner forever, no error text anywhere.

Run the same credentials in VLC. Players that show nothing are hiding a message that VLC will print, and a real error is worth more than an hour of guesswork on a remote control.

It says the account expired but I bought recently.

Retype the credentials once from the original message with autocorrect off, since a capitalized first character produces the same refusal. If it still refuses, the dates are a shop question and not something a thread can look up.

The wording mentions authorization rather than connection.

Then the server answered you, which rules out the host and the network in one step. Work the credentials branch: expiry, reissue, duplicate connection. Do not start swapping hosts, because the host is demonstrably reachable.

Every channel produces the same generic network error.

Check whether a dead profile is still saved in the app. Most players retry old credentials quietly in the background and surface the result as a network error that has nothing to do with your network. Delete the spare profile and retest.

The MAG portal loads but no channels appear under it.

The box reached the portal, so the address is right and the binding is answering. That points at the line rather than the hardware: check it has not expired, and confirm the MAC on the sticker is the one on file if the unit was ever repaired.

The error appears only at one time of day.

A clock-following fault is load, not configuration, and nothing you change permanently will address it. Switch host before that hour rather than during it, and record the times in any report, because the timestamps are the evidence.

The message changed after I switched hosts.

That is useful rather than alarming. A timeout that becomes a refusal means the new host is reachable and answering, which moves the whole diagnosis over to credentials. Quote both messages when you report it.

It says maximum connections reached.

One line carries one stream, so something else is already using it. Phones and tablets with the app left open count. Close every other install, wait a moment, and try again before you treat this as a fault.

The app closes to the home screen instead of showing an error.

That is the device reclaiming memory rather than the line refusing you. Cold boot, open nothing else, and try the same channel. If it survives, your fault was never about credentials or hosts.

Still stuck after all that?

Send the channel, the device and the app you are using and we will look at the line itself.

Get a line Ask first