Share Logs Safely

Describe the failure first

A useful report states the expected result, actual result, time and shortest reproduction steps. Include the operating system, architecture, client version and proxy mode. An update timeout is a more useful description than simply saying the client does not work. Prefer a test destination that does not involve a private account.

Capture only the relevant interval

Use the log viewing or export method documented for your release. Note the time before reproducing the problem, then retain the necessary context around the error. If you temporarily increase logging detail, restore the earlier level after the test. Redact a local copy while keeping the original privately for your own checks.

Inspect credentials and indirect identifiers

Check subscription URLs, query tokens, Authorization headers, proxy passwords, UUIDs, cookies, control-interface secrets and private server addresses. File paths may contain your real username; destination names and timestamps can reveal activity. Review screenshots for QR codes, address bars and notifications. Use consistent placeholders such as SERVER_A so that related events remain understandable.

Retain useful diagnostic structure

Keep error types, status codes, time differences and sanitized configuration structure where possible. For an HTTP 403, preserve the code and request stage but remove authentication values. For a permission failure, replace the personal directory name instead of deleting the whole line. Explain which categories of information you removed. Excessive redaction can make a useful report impossible to interpret.

Review the attachment and respond to leaks

Reopen the exact file you will upload and search for token, password, secret and Authorization, then inspect it manually. Do not attach an entire user directory or unrelated logs. Use the project's designated reporting channel. If a credential was already public, revoke or rotate it before removing the attachment; hiding a post does not undo copies made by others. Never include the replacement secret in the follow-up.

Next steps

Download center · FAQ

References (project documentation)