He1p / FIELD NOTES

Troubleshoot without making it worse

Good troubleshooting reduces uncertainty without creating a second problem.

Change one thing at a time

Write down what you see before changing settings. Compare two websites, then two browsers or devices where practical. Keep the task and timing similar so the comparison tells you something. “Works on another device” is evidence that narrows the search; it is not a complete diagnosis.

Keep the first steps reversible

Save unfinished work before reloading. Avoid factory resets, clearing all browser data, disabling security software, or changing shared network settings as early experiments. Site data changes can sign you out or remove local state. On managed equipment, involve the responsible IT team.

Respect certificate warnings

Do not submit sensitive information through a certificate warning. Check the intended address and your device’s date and time. Report the warning through an independently known support channel. Bypassing it or installing an unknown certificate is not a safe troubleshooting shortcut.

Hand off observations, not secrets

A useful support note includes the affected service, approximate start time, redacted error and completed comparisons. Never include passwords, verification codes, recovery codes, access tokens or private message contents. The checklist is manual: checking a box means you marked it done, not that we tested anything.

Official starting points: Mozilla connection troubleshooting, Chrome page-loading help, Gmail missing-message help.