Steps
- Reproduce the smallest failure once and note the exact time. Clear old logs first when possible.
- Confirm core version, config path and listening ports, then search for error, failed, timeout and refused.
- Follow the request through inbound, DNS, matched route and outbound to find the first missing stage.
- Before sharing, replace server names, UUIDs, subscription URLs, usernames and local paths while preserving timing and error types.
Why this matters
The final error may be a downstream symptom. Reading in data-flow order identifies whether startup, DNS, routing or outbound failed first.
How to verify
You can state the failed layer in one sentence and confirm it with one isolated configuration change.
Things to watch
Do not leave debug logging enabled permanently. It increases disk writes and can retain more browsing metadata.