Network proxy first triage response

When this happens

Use this when only the visible message is known. Do not stop at the screen message; validate the first observable mismatch before any setting is changed first.

Symptom checklist

• proxy appears repeatedly in the Network UI or logs.
• DNS, TCP handshake, proxy, VPN, packet loss differs between successful and failed requests.
• The issue appears only after separating server outage from network path issue.
• It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

• proxy specifically changes the investigation surface for Network: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• HTTP_PROXY, HTTPS_PROXY, or NO_PROXY values differ between shell and service runtime.
• The proxy blocks CONNECT to the target host or port.
• TLS inspection replaces certificates and breaks strict clients.
• Internal hosts are not included in NO_PROXY.
• Proxy authentication succeeds for browsers but not server-side jobs.
• For the first triage case, the first useful clue is the first observable mismatch before any setting is changed.

First 1-minute checks

1. Write down the first failure time, latest change, affected user, path, and object ID.
2. Compare DNS, TCP handshake, proxy, VPN, packet loss for success and failure in the same window.
3. Test the hypothesis: proxy failure caused by CONNECT restrictions, wrong proxy environment variables, TLS interception, bypass list drift, or upstream authentication.
4. Classify this as first triage: the first observable mismatch before any setting is changed.
5. Capture current values before changing configuration.

First evidence

Treat proxy as a first triage case. First collect evidence for the first observable mismatch before any setting is changed.

Output examples

Normal output

No matching error appears during the affected request window.

Failing output

The same error appears at the exact request time with the affected path, user, or object.

Output-to-action branches

• Only the visible message is known.
  Collect timestamp, route, request ID, user, and the first backend log line before editing configuration.
• The working and failing outputs differ.
  Act on the differing layer first: For proxy, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Command output is normal but users still fail.
  Separate browser cache, cookies, permissions, and network location before declaring it fixed.

Do not do this

• Do not change DNS, SSL, cache, and permissions at the same time.
• Do not change multiple layers before identifying the failing layer.
• Do not delete production data, grant broad permissions, or disable security controls as a first response.

Evidence quality

Auto-generated operator draft: includes issue-specific causes, commands, output branches, and unsafe-action warnings. Official-source links and real incident validation are queued for enrichment.

Commands to run first

grep -R "proxy" ./logs

dig example.com

curl -Iv https://example.com

traceroute example.com

nc -vz example.com 443

printenv | grep -i proxy

curl -Iv https://example.com

curl -x http://proxy.example.com:8080 -Iv https://example.com

openssl s_client -connect example.com:443 -servername example.com

date -u && grep -R "ERROR\|WARN\|failed" ./logs | tail -n 50

Fix order

1. Record the full proxy message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for proxy failure caused by CONNECT restrictions, wrong proxy environment variables, TLS interception, bypass list drift, or upstream authentication.
3. Compare the failing case with a successful case before editing settings.
4. If this is the first triage branch, Collect timestamp, route, request ID, user, and the first backend log line before editing configuration.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For proxy, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Print proxy environment values in the failing process.
• Test direct and proxied curl requests separately.
• Add internal hosts and metadata endpoints to NO_PROXY.
• Install the corporate CA only for clients that must trust interception.
• Use service-account proxy credentials for background jobs.
• For the first triage branch, Collect timestamp, route, request ID, user, and the first backend log line before editing configuration.

Evidence links

• curl everything official
• Cloudflare network troubleshooting official

Verification metadata

• operator-draft
• official-reference-linked
• 2026-07-23

Update queue

• Review cadence
  weekly-source-review
• Next enrichment
  Add one official-source check and one real output example for Network proxy.

Environment-specific checks

• Shared hosting, proxies, VPNs, or CDN layers can change server outage from network path issue results.
• Do not trust only the Network UI; compare command output.
• Japanese hosting panels may show completion before DNS or SSL fully propagates.
• Test from both office and external networks.

Prevent it next time

• Store normal examples for DNS, TCP handshake, proxy, VPN, packet loss.
• Add DNS cache, proxy bypass, MTU, firewall ports to the release checklist.
• Keep recurring errors in the same note format.
• Split alerts by error rate, latency, certificates, disk, and permission changes.

Related notes

• Network timeout first triage response
• Network connection refused first triage response
• Network connection reset first triage response
• Network TLS handshake first triage response
• Network VPN first triage response
• Network MTU first triage response
• Network DNS cache first triage response
• Network packet loss first triage response