Error 530
Cloudflare could not reach the origin; see the 1xxx error on the page
Seen in Cloudflare
Cloudflare returns HTTP 530 when it cannot resolve or reach the origin, with a 1xxx error code in the page body that names the exact cause.
Common causes
- Error 1016: the origin hostname in DNS does not resolve.
- Error 1033: the Cloudflare Tunnel for the hostname is not connected.
- Another 1xxx error shown in the body of the page.
How to fix it
- Read the 1xxx code in the page body and troubleshoot that error.
- Check the DNS record for the hostname points at a valid origin or a live tunnel.
Got a different message? Paste it into the error explainer.
Related errors
- 408 Request Timeout · The client took too long to send its request
- 413 Request Entity Too Large · The request body is bigger than the server allows
- 431 Request Header Fields Too Large · The request headers are too big
- 400 Bad Request: Request Header Or Cookie Too Large · nginx rejected oversized headers or cookies
- 499 Client Closed Request · The client gave up before nginx answered
- Error 524: A timeout occurred · Your origin took longer than 100 seconds to respond
- Error 1003: Direct IP access not allowed · A Cloudflare IP was requested without a hostname
- Error 1010: The owner of this website has banned your access based on your browser's signature · Your browser looks like a bot to the site's security settings
- Error 1015: You are being rate limited · You sent too many requests to a Cloudflare site
- Error 1020: Access denied · A Cloudflare firewall rule blocked your request
- Error 1033: Argo Tunnel error · The Cloudflare Tunnel for this hostname is not connected
- Error 1101: Worker threw exception · A Cloudflare Worker crashed with a JavaScript error