triage map
Change one variable at a time
Testing route, network, browser and account state separately makes the result easier to interpret and avoids unnecessary resets.
practical review
What to check on this route
On this troubleshooting page, treat route symptom, device symptom and account symptom as separate evidence checks. Compare their results before deciding what the next action should be.
Route symptom
Check host, redirect and public-page response.
Device symptom
Check storage, time, browser and operating-system state.
Account symptom
Use self-service checks without sharing secrets.
five-step method
A reversible checklist
For troubleshooting, begin with this first check: Record the current symptom. Keep the sequence intact through the final check: Stop after any request for remote access or secret codes. Record what changed before moving on.
- Record the current symptom.
- Test on a stable normal connection.
- Clear only site-specific browser data when appropriate.
- Avoid resetting credentials without an account error.
- Stop after any request for remote access or secret codes.
quick answers
Common questions
Should I try many fixes at once?
No. One change at a time preserves evidence about what affected the problem.
Can a network failure prove the service is down?
No. It may be local, DNS-related or route-specific; record the limited result.
18+ and responsible use
This troubleshooting guide is for adults aged 18 and over. Protect personal data during support contact, keep time and spending boundaries visible and stop when a helper asks for account control.