HTTPfy

530 Origin Error (with 1xxx code)

Cloudflare: returned together with a Cloudflare 1xxx error, such as 1016 Origin DNS error or 1033 Tunnel error.

530 at a glance

Code
530
Name
Origin Error (with 1xxx code)
Class
5xx Server error
Status
Non-standard used by Cloudflare
Documented by
Cloudflare
Cacheable by default
No by default. Caches only store responses with unrecognised status codes if explicit freshness (Cache-Control max-age) is given.

What 530 means

Cloudflare sends HTTP 530 alongside a 1xxx error page. The real diagnosis is the 1xxx number on the page: 1016 means Cloudflare could not resolve the origin hostname, 1033 means a Cloudflare Tunnel is not connected, and so on.

What typically causes a 530

  • Error 1016: a CNAME in Cloudflare points to a hostname that does not resolve.
  • Error 1033: cloudflared is not running or the tunnel is deleted/misconfigured.
  • Other 1xxx configuration errors on the zone.

Fix it on the server

  • Look up the 1xxx code in Cloudflare's docs; for tunnels, check cloudflared tunnel info and the connector logs.

Fix it as a client or visitor

  • Report the 1xxx code and Ray ID to the site owner.

Headers that go with 530

HeaderRole
CF-RAYRequest ID for troubleshooting.

Example response

HTTP/1.1 530
Server: cloudflare
Content-Type: text/html

... Error 1033 Cloudflare Tunnel error ...

Opens the HTTP headers tool with your URL filled in; it shows the status line and headers of every redirect hop.