Trex IPTV
Symptom first, fix second

How to report a problem so it gets fixed on the first reply

There are two routes out of a fault, and picking the wrong one costs more time than writing a bad report does. Work out which of them you need first, then put enough in the message that nobody has to come back to you with questions.

Pick the route before you write anything

Post a thread here when you want to know what is happening and why, or when you suspect the fault is on your side of the router. Write to support when something has to change at source: a MAC re-bind, reissued credentials, a line that authenticates nowhere. The two are not interchangeable, and a source-side request posted as a thread simply waits. If you cannot tell which you need, describe the symptom in a thread and somebody will route you within a reply or two.

The five specifics that decide the diagnosis

Name the device and the app, the exact channel as it is spelled in your list, the host you were on and any host you switched to, the clock time it failed, and whether a second device on the same network failed at the same moment. That last one is the one that splits a line fault from a device fault, and it is the only one of the five that nobody can work out at this end. Leave it out and the diagnosis waits a day while somebody asks you to go and run it.

Quote the error, do not paraphrase it

Apps use similar wording for very different conditions, and the distinction between an authentication refusal and a connection timeout changes the whole diagnosis. Type out what appears on screen, character for character, or photograph it. If there is no message at all and you just get a black screen with a spinner, say that explicitly, because absence of an error is itself a clue.

What to leave out

Do not send your password, and do not send a full M3U playlist URL, which contains the same secret in a less obvious form. Support can locate your line without either. If you have already posted one in a public thread anywhere, treat it as exposed and ask for the line to be reissued rather than hoping nobody noticed.

Anything about orders

Questions about an order, a term, or anything with a number attached are handled where the purchase was made rather than in a technical thread. We are not being unhelpful; a forum answer about money is a forum answer that goes out of date. Take those to https://trexiptv.click and keep this space for faults.

Questions

I do not know which host I am on.

Open the profile or account screen in your app and read the server field. On an M3U setup it is the domain at the front of the playlist URL. Copy the domain only, without the part that follows, and include that.

The fault only happens in the evening. Should I wait to report it?

No, report it with the times it occurs. A fault that tracks the clock is a load pattern and the timestamps are the evidence, so a report filed at noon describing last night is perfectly useful.

Can support fix a problem with my own network?

They can confirm the line is healthy from their side, which narrows it down, but nobody can fix your wiring remotely. If a laptop on the same network streams the same channel cleanly, the answer is already inside your house.

How do I report something I cannot reproduce on demand?

Keep a short log instead of a description. Date, clock time, channel, host, device, for three or four occurrences. Intermittent faults are read from the pattern in those timestamps, and a log beats any amount of recollection.

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