The Logs page in full: levels and common messages decoded
The Logs page streams the core's log. The profile's log-level field controls verbosity: silent, error, warning, info (default — logs every connection), debug (most verbose, for tough cases).
Common lines decoded
[TCP] dial DIRECT ... error: connect timeout— a direct connection timed out: the target is genuinely unreachable, or traffic that should be proxied got misrouted to DIRECT;[TCP] dial HK-01 ... error: connect failed— connecting through that node failed: node down or blocked; try another;[DNS] resolve xxx.com error— name resolution failed; check the DNS config ("Custom DNS");rejected due to ...— the connection was deliberately REJECTed by a rule; ad-blocking rulesets produce these in volume, which is normal.
Recommended workflow: temporarily set log-level to debug (a Mixin override works), reproduce the issue once, then search the log for the target domain and see where it failed — DNS, rule matching, or the node connection. Switch back to info afterwards; debug output is heavy.