XX-net/XX-Net · warning
%s %s%s status:%d trace:%s
Error message
%s %s%s status:%d trace:%s
What it means
CloudFlareFront.request received a non-200 HTTP status; logs method, host, path, status and the task trace for diagnosis.
Source
Thrown at code/default/x_tunnel/local/cloudflare_front/front.py:107
self.dispatchs[host] = http_dispatcher
dispatcher = self.dispatchs[host]
return dispatcher
def request(self, method, host, path="/", headers={}, data="", timeout=120):
dispatcher = self.get_dispatcher(host)
response = dispatcher.request(method, host, path, dict(headers), data, timeout=timeout)
if not response:
self.logger.warn("req %s get response timeout", path)
return "", 602, {}
status = response.status
content = response.task.read_all()
if status == 200:
logger.debug("%s %s%s send:%d recv:%d trace:%s", method, host, path, len(data), len(content),
response.task.get_trace())
else:
self.logger.warn("%s %s%s status:%d trace:%s", method, response.worker.ssl_sock.host, path, status,
response.task.get_trace())
return content, status, response
def stop(self):
logger.info("terminate")
self.connect_manager.set_ssl_created_cb(None)
for host in self.dispatchs:
dispatcher = self.dispatchs[host]
dispatcher.stop()
self.connect_manager.stop()
self.running = False
def set_proxy(self, args):
logger.info("set_proxy:%s", args)
self.config.PROXY_ENABLE = args["enable"]
self.config.PROXY_TYPE = args["type"]View on GitHub (pinned to cfa5bc17b6)
Solutions
- Inspect the logged status code: 403 suggests IP/SNI blocking, 5xx suggests origin issues
- Rotate front IPs / domains
- Verify the target host configuration
Defensive patterns
Strategy: fallback
Try / catch
content, status, resp = front.request(...)
if status != 200:
handle_block_or_origin_error(status) Prevention
- Handle 403 as IP-blocking signal and rotate fronts
- Don't assume 200; always branch on status
When it happens
Trigger: Any dispatcher response whose status != 200, e.g. 403/502/525 from the CloudFlare edge.
Common situations: CloudFlare blocking (403), origin errors (502/504), or CAPTCHA/challenge pages when the fronted host is unavailable.
Related errors
- req %s get response timeout
- api:%s fail:%s t:%d
- req %s get response timeout
- %s %s%s status:%d trace:%s
- login session server is down, try get new server.
AI-assisted analysis of XX-net/XX-Net@cfa5bc17b6 (2026-08-27).
Data as JSON: /api/errors/79df26d71ebe1e69.
Report an issue: GitHub.