Tagged articles
SNI
10 articles · Page 1 of 1
This article explains why Nginx reverse‑proxying to an HTTPS upstream can return a 502 Bad Gateway error when SNI is not sent, shows the relevant SSL handshake log, and provides a complete configuration example—including enabling proxy_ssl_server_name—to fix the issue and avoid reload‑related socket problems.
502 Bad GatewayConfigurationSNI
0 likes · 4 min read

In many Envoy‑based gateways, enabling HTTP/2 can cause intermittent 404 errors because the :authority header and the TLS SNI value differ, especially when using wildcard certificates and multi‑domain routing, and this article explains the root cause and multiple mitigation strategies.
421EnvoyFilter Chain
0 likes · 14 min read

This guide explains why separate ports are normally required for multiple SSL sites, how Nginx’s SNI support lets you share a single IP and port, and provides step‑by‑step compilation and configuration examples for www, live, and vod domains.
HTTPSOperationsSNI
0 likes · 6 min read

During a migration from Nginx to APISIX, the team encountered TLS handshake failures caused by missing SNI fields and legacy SSLv2Hello usage, leading to a detailed investigation, protocol explanations, and configuration fixes to restore secure connections without modifying client code.
APISIXGatewayKubernetes
0 likes · 11 min read

Even though HTTPS encrypts web traffic, DNS queries, IP address sharing, traffic patterns, cookies, and especially the plaintext TLS handshake—including the SNI field—can reveal which sites you visit, but the Encrypted ClientHello extension can mitigate this leakage.
Encrypted ClientHelloHTTPSSNI
0 likes · 8 min read

This article walks through a real‑world Nginx reverse‑proxy SSL issue, explains the root cause of 502 and handshake failures caused by missing SNI support, and provides step‑by‑step configuration changes and code snippets to resolve the problem.
SNISSLnginx
0 likes · 8 min read

This article explains the DNS hijacking threat, shares a real incident affecting NetEase Cloud IM, and details a comprehensive high‑availability architecture—including HttpDNS, laddered HTTP requests, caching strategies, and SNI handling—that protects the SDK from DNS attacks and ensures reliable service.
CacheDNS hijackingHTTPDNS
0 likes · 13 min read

The article explains why accessing Zhihu with its raw IP address is blocked while domain access works, covering CDN sharing, the importance of hostnames, and how the TLS SNI extension lets servers identify the intended website before establishing a connection.
CDNDNSIP address
0 likes · 5 min read

This article uses a foot‑massage shop analogy to explain why deploying HTTPS behind a 7‑layer proxy can encounter hidden pitfalls, detailing SNI requirements, the dangers of binding multiple certificates to the same IP + port, and the need for consistent SSL settings across all Nginx virtual hosts.
ProxySNI
0 likes · 7 min read

This guide explains the five most common reasons an SSL certificate appears untrusted—such as using a self‑signed certificate, misconfigured trust chain, missing domain coverage, expiration, or lack of SNI support—and provides practical steps to resolve each issue.
SNISSLcertificate
0 likes · 6 min read
