Skip to content

//SETUP & TROUBLESHOOTING / 2 MIN READ

How to report a proxy connection problem.

What to record when a connection fails, and which details to leave out of shared notes.

Pencil illustration of desktop and mobile devices prepared for a connection check.

Describe the failing step and include a timestamp, tool version and redacted error.

Explain what you expected and what happened

Start with the task and its failing step. Did the proxy reject authentication, did the connection time out, or did the target page return unexpected content? Each result points to a different part of the setup.

Include one representative URL and the time of the attempt with its timezone. A description such as “the proxy does not work” leaves the person helping you to reconstruct the entire sequence.

Include the details needed to repeat the check

IncludePurpose
Tool and versionIdentifies the browser, script or profile used.
Proxy resource referenceIdentifies the affected resource without sharing its password.
Time and observed errorMakes the attempt easier to compare with available records.
Checks already triedAvoids repeating steps and shows where the result changed.

Remove secrets before sharing

Hide proxy passwords, API keys, cookies and account credentials. Check the address bar, terminal commands and screenshots as well as the message itself; authentication details can appear in more than one place.

Share only the page information needed to explain the failure. If the task involves private account content, describe the symptom without copying that content into the report.

Change one thing, then report the result

After a suggested adjustment, repeat the same small check and note whether the error changed. If several settings are changed at once, it becomes harder to tell which one affected the outcome.

Keep the original error and the new result together. Once the proxy test passes, check that a representative target page returns the content you need.

Back to the journal