This domain is served via our edge network but no origin is set.

The edge node accepted the TLS handshake for this hostname, but the routing table contains no upstream service. Connect a backend in the control panel to make this domain serve real traffic. Nothing has been cached, nothing has been logged beyond this diagnostic stub.

This message comes from the edge tier. No application code has executed. No origin certificate has been negotiated yet. This page is a placeholder built into the routing fleet to indicate the boundary between "the edge accepted me" and "no backend exists for me yet".

Diagnostic envelope

Edge POP	node-fra-7a.edge.lan
Request Trail	7f1c-edge-fra-7a-9182-aa3
Policy	default-no-origin
Policy version	2024.10.28-r4
TLS	TLS 1.3 / OK
HTTP	503 NO_BACKEND
Bytes served	0 from origin, this page from edge
Cache state	BYPASS (no origin)

Operator actions

Minimal config (yaml)

policy: routing.v3
hostname: this-edge-domain
origins:
  - host: api.internal.lan
    scheme: https
    port: 443
strategy: failover
probe:
  path: /healthz
  interval: 10s

Common questions

Why am I seeing this and not my site?

Because the routing table for this hostname is empty. The edge accepted your DNS resolution and TLS connect, but does not know where to forward the request.

How fast does a new policy go live?

Policy fans out across all points-of-presence in under one minute, usually around 30 seconds. Watch the propagation widget in the routing panel.

Was any of my data captured?

No. There is no origin to forward to, so nothing has been read except the request envelope used to render this placeholder.

Languages