EDGE NODE: NO ORIGIN CONFIGURED

This domain resolves to an Edge Network point-of-presence, but no upstream origin has been configured for the requested hostname. The node is healthy and able to accept TLS, but cannot forward the request because the routing table is empty for this name.

If you are the operator of this domain, finish your edge configuration by mapping the hostname to a backend through the control panel. The placeholder response below will continue to be served until at least one origin pull rule is published.

Suggested checklist

1. Add an origin pull rule for host-mapping with a reachable upstream
2. Verify the CNAME flatten target matches your edge zone declaration
3. Set at least one HTTPS upstream and re-publish the routing policy
4. Confirm the policy version number has incremented in the panel
5. Wait ~30s for the change to fan out across all points-of-presence

Current routing decision

Example panel snippet

policy: gridpop-routing
hostname: this-edge-domain
origins:
  - https://backend-1.internal.lan:443
  - https://backend-2.internal.lan:443
strategy: round-robin
health_check:
  path: /healthz
  interval: 10s
  timeout: 2s
publish: true

Frequently asked

• Did the edge cache my data? No — there is no backend to fetch from, so no payload is stored anywhere.
• Will the change take effect immediately? Most policy versions go live in under a minute, edge-wide.
• Can I have multiple origins? Yes — round-robin, weighted, or active/passive failover are available.