Skip to content

[HTTP Codes] Update error-1014.mdx #27837

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Oxyjun merged 3 commits into from
Feb 25, 2026
Merged

[HTTP Codes] Update error-1014.mdx #27837

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
298fb08
[HTTP Codes] Update error-1014.mdx
luishcardoso Jan 23, 2026
0b9b035
[1XXX errors] Update error-1014.mdx
luishcardoso Feb 9, 2026
4ae3f7a
Apply suggestion from @Oxyjun
Oxyjun Feb 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion ...support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1014.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,4 +18,7 @@ Another common cause is connecting a custom domain to an R2 bucket, where the do

- To allow CNAME record resolution to a domain in a different Cloudflare account, the domain owner of the CNAME target must use [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/).
- To allow connecting to a R2 bucket with a custom domain, disable the [zone hold](/fundamentals/account/account-security/zone-holds/) feature on the custom domain target zone to resolve the 1014 error.
- To allow connections to an R2 bucket whose zone is banned, first check whether there is any [phishing report](/fundamentals/reference/report-abuse/complaint-types/) for the hostname (and request a review if there is one). If this does not resolve the issue, contact your account team.
- To allow connections to an R2 bucket whose zone is banned:

- First, check whether there is any [phishing report](/fundamentals/reference/report-abuse/complaint-types/) for the hostname (and request a review if there is one).
- Second, make sure that you have no unpaid invoice(s), as you will not be able to enable any new services until [any outstanding balance](/billing/pay-invoices-overdue-balances/) is addressed. If this does not resolve the issue, contact your account team.
Loading