Diagnosing JD Worldwide Seller Portal Connection Resets
JD Worldwide’s seller portal is hosted on JD Cloud’s infrastructure with Cloudflare as the CDN layer in front. The portal uses TLS 1.3 with ECH for all seller authentication. When sellers access the portal from macOS Safari on networks with SSL inspection (common in China and Southeast Asia), the ISP gateway resets the ECH-enabled ClientHello, preventing the TLS handshake from completing.
JD Cloud’s CDN configuration supports TLS 1.2 fallback, but Cloudflare’s current security policy deprioritizes TLS 1.2 fallback unless the client explicitly signals TLS 1.2 support in the ClientHello. Some ISP gateways strip this signal, causing Cloudflare to assume TLS 1.3-only support, which then fails due to ECH incompatibility.
AWS CloudFront Routing Metrics for JD Cloud CDN
The webs.ninja network lab provides latency and packet loss data for JD Cloud’s CDN edge nodes, helping sellers identify whether the connection reset is caused by their local network infrastructure or a specific CDN edge node failure in their region.
Fixing JD Worldwide Seller Portal Connection Resets
Using Chrome with QUIC Disabled
JD’s Cloudflare configuration supports HTTP/3 (QUIC), which can be blocked by ISP gateways. Download Chrome → Settings → Advanced → System → disable Use QUIC protocol. Access JD Seller Portal in Chrome — with QUIC disabled, Chrome uses HTTP/2 over TCP, which ISP gateways handle reliably.
Manually Setting DNS to Cloudflare’s Resolver
Navigate to System Settings → Network → Wi-Fi → Details → DNS. Set DNS servers to 1.1.1.1 and 1.0.0.1. Cloudflare DNS returns the optimal Cloudflare edge node IP for JD’s CDN, potentially routing the connection to a node with a clearer path from the seller’s location.
Using VPN with Hong Kong or Singapore Endpoints
JD’s infrastructure is most accessible from Hong Kong and Singapore. Use a VPN with endpoints in these regions to route your traffic through ISP infrastructure that fully supports TLS 1.3 with ECH, bypassing the problematic ISP gateway in the seller’s region.
Call to Action
Before applying VPN or DNS fixes, run the webs.ninja network lab to trace the full connection path to JD’s seller portal. The diagnostic identifies the specific failure layer — ISP gateway, Cloudflare edge, or JD Cloud origin — allowing targeted remediation.