Overview
What it is
An investigation of edge-to-origin connectivity failures and reverse-proxy behavior.
Problem and context
External requests experienced connection failures and Cloudflare 522 behavior even when local origin processes appeared reachable.
Approach
Trace the entire network path using endpoint validation, listening socket checks, packet captures, firewall/load-balancer examination and TLS handshake comparison.
Technical depth
An edge-to-origin 522 investigation requires separating three boundaries: external TCP handshake, TLS negotiation, and reverse-proxy upstream connectivity. Prior testing used `ss`, loopback and `--resolve` curl variants, and packet capture.