Recovering a Failed Automatic Proxy Group with a Local Failover Guard
How request-based health checks, bounded local control, and explicit ownership turned a stale automatic proxy group into a recoverable connection path.
9 articles
How request-based health checks, bounded local control, and explicit ownership turned a stale automatic proxy group into a recoverable connection path.
How binary header inspection separated a WAV container-length defect from damaged audio, and how a verified rewrite made the file safe for stricter media pipelines.
How idempotent daily plans, evidence-gated completion, spaced review, and bounded load changes turn a long roadmap into an executable learning system.
How a stable allocation key and a process lock let a recurring paid pipeline create several jobs per period without duplicating work when a scheduled run retries.
A recovery-first procedure for stopping a cloud workload, releasing every paid resource, and preserving evidence that the system can be restored.
A local connectivity incident resolved by proving the remote service was healthy, isolating incorrect direct routing, and adding one precise proxy rule.
Making a Codex desktop launcher resilient to local proxy port changes while keeping failure handling safe.
A Dubbo connection failure investigation that moved from the deepest network exception to a stopped provider container and its memory limits.
A retained historical incident note: diagnosing the former fichil.com VPS from DNS and network reachability through listening ports, Nginx, and site files. Production now runs on Sites.