Troubleshooting

Start with the symptom.

Ten practical guides that separate observed evidence from possible causes.

TOPIC-01

Codex “Waiting for network”: what it means and what to check

A careful, evidence-based way to distinguish a Codex network wait from browser success, authorization, or a provider incident.

TOPIC-02

Separate a Codex reconnect symptom from DNS, TLS, WebSocket, route, and provider evidence without guessing root cause.

TOPIC-03

Why a working ChatGPT page does not prove the native Codex path, protocol, proxy context, or session is healthy.

TOPIC-06

Separate DNS, connection, TLS, proxy, first-byte, streaming, and application evidence after a Claude Code timeout.

TOPIC-07

Why initial Claude reachability and stream continuity are different observations, and how to verify safely.

TOPIC-08

A bounded way to investigate Cursor client connectivity without treating a working website as proof of the application path.

TOPIC-09

Separate Copilot client, proxy, certificate, provider-status, and entitlement evidence without guessing a root cause.

TOPIC-10

Use bounded evidence to distinguish Gemini transport symptoms from API, account, quota, and provider-service conditions.

TOPIC-15

Recognize the captive-portal bootstrap window without automating login or blaming the AI provider.

TOPIC-17

Why browser success does not prove a native AI agent’s DNS, TLS, proxy, WebSocket, or address-family path.