XX-net/XX-Net · warning
not support
Error message
not support
What it means
CloudFront check_ip script: a result came back but res.ok is False — connected, yet the response did not validate as a working CloudFront front for that host.
Source
Thrown at code/default/x_tunnel/local/cloudfront_front/check_ip.py:152
config_path = os.path.join(module_data_path, "cloudfront_front.json")
config = Config(config_path)
openssl_context = SSLContext(logger, support_http2=True)
host_manager = HostManagerBase()
connect_creator = ConnectCreator(logger, config, openssl_context, host_manager, debug=True)
check_ip = CheckIp(logger, config, connect_creator)
#check_all_ip(check_ip)
#exit(0)
res = check_ip.check_ip(ip, sni=sni, host=host, wait_time=wait_time)
if not res:
xlog.warn("connect fail")
elif res.ok:
xlog.info("success, domain:%s handshake:%d", res.host, res.handshake_time)
xlog.info("response:%s",res.response.content)
else:
xlog.warn("not support")View on GitHub (pinned to cfa5bc17b6)
Solutions
- Try another SNI/host
- Drop this IP from the pool
- Re-scan with the maintenance tooling
Defensive patterns
Strategy: fallback
Prevention
- Use a known-good CloudFront SNI for probing
- Drop IPs failing res.ok
When it happens
Trigger: TLS completes but HTTP check for the host fails (403/incorrect content).
Common situations: IP is CloudFront but the tested distribution/host is not served or blocks direct SNI access.
Related errors
AI-assisted analysis of XX-net/XX-Net@cfa5bc17b6 (2026-08-27).
Data as JSON: /api/errors/4de3c6d736640b38.
Report an issue: GitHub.