Trex IPTV: what to do when a line stops
Trex IPTV playback faults sort into a few shapes, and the shape names the cause. Work through them in this order and you will usually beat a support reply.
Two questions before anything else
Almost every playback problem on Trex IPTV can be placed by answering two questions, and the answers are worth more than any amount of reinstalling.
First: is it one channel or all of them? Second: is it one device or every device in the house? A fault that affects one channel on every device lives upstream of you and there is nothing to configure. A fault that affects every channel on one device is in that room. A fault that affects everything everywhere is the line or the server address, and that is the quickest of the three to fix.
Answer those before you touch a setting. Reinstalling a player is the instinct and it is almost always wasted effort, because the player holds no state worth losing and the subscription does not live inside it.
When everything stops at once
Start with the one observation that splits this case in half: does the channel list still load?
If the list appears and nothing opens, the account authenticated. That single fact rules out an expired term, a mistyped username and a wrong password in one go, because none of those would have produced a list. What is left is the server address, and a server address that has stopped answering is the most common failure on any IPTV line anywhere.
If the list does not load either, check the expiry date on your order first, then the details themselves, character by character, capitals included. A password pasted with a trailing space behaves exactly like a wrong password and looks completely correct on screen.
Changing the host, which fixes most of it
Your order comes with more than one server address. They look like http://line.txteditors.site, http://line.mytexxy.site, http://line.catrex.site and so on, and they are interchangeable - the same line, reached by a different road.
In an Xtream login, the host is its own field and you simply replace it. In an M3U link it is harder to see: the address takes the form http://some.host/get.php?username=...&password=... and only the part between the double slash and the first slash after it is the host. Everything from get.php onwards stays exactly as it is, and that is the part people accidentally delete.
On a MAG box it is Portal 1 under System Settings, Servers, Portals, and you must restart from the menu afterwards rather than pulling the power, or the box carries the old session into the new boot and appears not to have changed anything.
There is a step-by-step version with screenshots and the hosts issued for your own line, which is worth having open on a phone while you do it on a television.
When one channel is bad and the rest are fine
This is the case where the honest answer is that there is nothing for you to do. A single channel that blocks up, softens or freezes while everything around it is immaculate is being re-encoded badly or is coming from a degraded source. It is upstream of your router, your device and your account, so no setting anywhere will change it.
What helps is a precise report. The name as your own app prints it, the group it sits in and the time you saw it are between them enough to find the right feed and put eyes on it. A message saying that sport is bad is not actionable, because there is nothing in it to look up.
There is a related case worth naming separately. When one demanding channel falls apart while the rest hold, and the fault deepens the longer the box has been running, the device is handling H.265 on its processor and overheating. It looks exactly like a network fault and it is not one.
When the guide is blank or the times are wrong
These two look similar on screen and have completely different causes, so the distinction is worth making carefully.
- The whole grid is displaced by one fixed amount, everywhere. The player is reading the schedule against the wrong region. That is a device setting, and it is in your hands rather than ours.
- Some channels have a full schedule and others are empty. That is an identifier that has drifted, usually because a broadcaster renamed a service. It is ours to remap, it is not visible from your end, and telling us which channels are blank usually fixes it the same day.
Neither case means the stream is broken. A channel with an empty grid still plays perfectly; it only feels broken, because without a schedule the list is a directory of names instead of something you can look through and land on. That is precisely why it is worth reporting rather than living with.
When playback refuses to start for no reason
A line that works, then does not, then works again, on no pattern you can identify, is usually the connection limit rather than a fault. The limit is enforced at the server, and going over it does not reliably produce a clear message - often the stream simply will not begin.
The things that quietly hold a slot are worth listing, because none of them look like watching television:
- A television left switched on in an empty room.
- A phone app pushed into the background rather than shut, which keeps its slot for a while afterwards.
- A second device someone else in the house started and forgot.
- Anyone outside the house holding the same details.
That last one is the hardest to diagnose from the inside, because the failures correlate with nothing in your own routine. If playback refuses at times that match nothing you are doing, it is worth considering before anything technical. The details are the subscription, so sharing them is the same as sharing the line.
When the term has simply ended
It is worth checking the boring explanation before the interesting ones. Your order carries an expiry date, and a term that has reached it stops answering with no warning message of its own.
Renewing extends the line you have rather than building a second one, so the account name, the password and the address are all untouched and no device needs opening. Act ahead of the date rather than behind it: an extension on a running line takes effect at once, and waking one that has already gone quiet does not always. How renewals and refunds actually work covers the mechanics and the cases where a refund applies.
What to put in the message
If none of that has settled it, what decides whether this takes two messages or two days is how much you put in the first one.
- Your order number, which begins TRXA- for Trex IPTV orders placed on this site.
- The channel name exactly as it is printed in your own app, which is not always how the broadcaster writes it.
- The device and the player, and whether it was wired or on wifi.
- The time it happened and your own timezone.
- Whether the same channel also fails on a phone with wifi off and mobile data on.
That last line is worth more than the rest combined, because it settles whether the problem is delivery or your own network in about a minute. Send it to the contact page or over WhatsApp, and a person who can open your actual order will read it rather than a script.
Common questions
Everything stopped at once. Has my line been cut off?
Far more often the server address has stopped answering than the line has been disabled. The quick test is whether the channel list still loads: a list that appears while nothing opens means the account authenticated fine, which rules out expiry and a wrong password immediately. Change the host before assuming anything worse.
Why does it only fail in the evening?
Because that is when your own connection, everybody else in the street, and delivery infrastructure are all under their heaviest load at the same time. A fault that appears between seven and eleven and vanishes at midnight is a load story, and a cable to the router is the single most effective answer available to a household.
One channel is terrible and the rest are perfect. What can I change?
Nothing, and that is the useful part of the answer. A lone bad channel is either badly re-encoded or fed from a degraded source, and both of those sit above your router, your hardware and your account in the chain. Send us the name the way your own app prints it and somebody will go and look at that feed. It is the case of everything failing together that points back at your end.
Playback refuses to start at random times. Why?
That pattern is usually the connection limit rather than a fault. Exceeding it often produces no clear error at all, just a stream that will not begin. A set left running in an empty room occupies one, and so does a phone app that was minimised instead of being shut. If it happens at times that match nothing in your own house, consider whether the details have been shared.
Still stuck?
Send us your order number and the device you are using, and a real person will work through it with you. If the list is there but nothing opens, point the line at a different host before writing in.
Contact support