Opened 20 months ago

Last modified 20 months ago

#29584 assigned task

Write a guide to understanding a Tor log

Reported by: wayward Owned by: wayward
Priority: Medium Milestone:
Component: Community/Tor Browser Manual Version:
Severity: Normal Keywords:
Cc: emmapeel, ggus, gk, traumschule Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


As it stands, Tor Browser logs are fairly difficult for users to understand. We should write up a guide to help users understand their Tor Browser logs. Doing so will help users to diagnose connection issues with the browser.

If possible, it would also be helpful if the logs could provide more information about what issues are occurring, or if users were presented with error messages that 1. indicated what issue they were experiencing, and 2. suggested a potential solution to that issue. These changes would give users more tools to solve small connection problems on their own, and also provide us with more information to go on when assisting users through RT/frontdesk and other lines of communication.

Child Tickets

Change History (2)

comment:1 Changed 20 months ago by gk

Cc: gk added; geko removed

What output is difficult to understand? And if so, I wonder what details a casual user should actually need to understand. I am not convinced we should spend effort on making everyone understand what errors/warnings your browser console is throwing at you, for instance.

That said, the main problem I see is more that we need something written down on how to gather the log information we need to debug and reproduce problems on all supported platforms + making the necessary information available in our software in the first place (clock skew issues come to mind as one major one, for example. See #9675 for the parent ticket.)

comment:2 Changed 20 months ago by emmapeel

Maybe the page at can be improved upon, and then linked from elsewhere?

Note: See TracTickets for help on using tickets.