Write a support ticket that can actually be answered
Describe the observable failure: “The player signs in, but every live item stops after about two minutes on this device.” That is more useful than saying the whole service is broken. Avoid guessing the cause in the title
Start with one sentence
Describe the observable failure: “The player signs in, but every live item stops after about two minutes on this device.” That is more useful than saying the whole service is broken. Avoid guessing the cause in the title.
Include the environment
List the device model, operating system version, player name and app version. State whether the device uses Wi-Fi or Ethernet. Mention a recent update or setting change if it happened just before the issue started.
Record a time and a sample
Give the date, local time and time zone. If only certain items fail, list one or two examples rather than an entire category. Explain whether another authorized sample works in the same session.
Show what you tried
- Restarted the player: describe the result.
- Compared another device: say whether it reproduced the issue.
- Checked another connection: describe the change, if any.
- Refreshed the guide or playlist: say whether the import completed.
Remove private data
Never include passwords, payment-card details or full playlist URLs in a forum post. If support requires an account identifier, provide it through the site's private route. Crop a screenshot to the error and double-check that a token is not visible elsewhere.
A reusable structure
Device and app:
Connection:
When it happens:
Expected result:
Actual result:
One affected sample:
Comparisons already tried:
Redacted error text:
Close the loop
If a fix works, reply with the exact change and any remaining limitation. A future reader can then understand whether your result applies to the same device and symptom. On the IPTVs Hub forum, the topic owner can mark an approved reply as the accepted answer.