Unable to add custom domain to new R2 bucket

For Workes & Pages, what is the name of the domain?

N/A

What is the error number?

10001

What is the error message?

We encountered an internal error. Please try again. (Code: 10001)

What is the issue or error you’re encountering

I’m attempting to add a custom domain to a newly-created (~8 hours ago) R2 bucket. After providing the custom domain and clicking “Connect domain” I get the the above error along the bottom red error bar.

What steps have you taken to resolve the issue?

I’m aware that there was an incident regarding connecting custom domains (Cloudflare Status - Issues connecting R2 custom domains) recently but it is marked as resolved, and this is still occurring.

1 Like

I’m encountering the same issue with adding a custom domain to my new R2 bucket. The domain is already active in my Cloudflare account, but the R2 bucket itself is new. Despite the Cloudflare Status update indicating that the problem was resolved about 20 hours ago, I’m still unable to assign the custom domain.

Hi,

@creamfilled and @sametbkomurcu,

Are you still having issues when adding Custom Domains to R2 buckets?

Greets

I’m still encountering issues when trying to add a custom domain. Below is the HTTP response I received:

{
    "success": false,
    "errors": [
        {
            "code": 10001,
            "message": "We encountered an internal error. Please try again."
        }
    ],
    "messages": [],
    "result": null
}

I’m still encountering this issue too. If it helps, the Ray ID of the request was “8b2f9c4a8db78441-YVR”.

{
  "success": false,
  "errors": [
    {
      "code": 10001,
      "message": "We encountered an internal error. Please try again."
    }
  ],
  "messages": [],
  "result": null
}

It looks like the issue has been fixed, and I was able to add the custom domain.

I was also able to add a custom domain now.

1 Like

Hi everyone. Apologies for the delay. We had an incident a 2 days ago impacting custom domains and released a fix. There was a very small subset of customers we needed to remediate after the incident that attempted to create domains during the incident time that needed correction. This process is complete and custom domains should be working as expected. Please reach out if you’re seeing otherwise.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.