Desktop browser developer tools · Research guidance. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Decide whether a trace is necessary
Begin with the error text, approximate time, browser version and the smallest repeatable action. A detailed network archive is useful only when the legitimate support team needs it. Agree the purpose and secure destination first; a public forum or unrelated file-analysis website should not receive a recording of a private account session.
Bound the recording
Chrome and Firefox document starting, stopping and clearing the Network request log. Use a fresh relevant log and reproduce only the failing harmless step. If the task crosses a page navigation, inspect Preserve log or Persist Logs deliberately. Avoid recording unrelated browsing, private messages or payment operations while the panel remains open.
Read the export choice
Chrome and Edge document sanitised HAR exports that omit specified sensitive headers, while offering a separate sensitive-data export. Firefox documents saving the current log as HAR. Do not assume identical redaction or export scope across tools; inspect the actual selected action and current publisher instructions rather than following an old screenshot blindly.
Review before sending
Treat the archive as potentially private even when sanitised. Review addresses, query values and any included content for account-specific information. If you cannot assess it, ask the trusted team for a narrower redacted observation instead. Keep a private original if needed for diagnosis and a clearly identified redacted copy, rather than editing evidence silently and declaring it complete.
Questions, answered
Does sanitised mean every private field was necessarily removed?
No. Review the documented scope and the actual file.
Should an entire unrelated browsing session be captured?
No. Bound the trace to the necessary failing task.