Unable to generate origin certificate for zip domains

[aaronhatton]

Answer these questions to help the Community help you with Security questions.

What is the domain name?
exported-report.zip

Have you searched for an answer?
Yes

Please share your search results url:
https://community.cloudflare.com/t/unable-to-generate-certificate/183945

When you tested your domain using the Cloudflare Diagnostic Center, what were the results?
Yes, no issues found

Describe the issue you are having:
When trying to generate an origin certificate, I am shown an error message as follows:

What error message or number are you receiving?
Failed to validate requested hostname *.exported-report.zip: This zone is either not part of your account, or you do not have access to it. Please contact support if using a multi-user organization. (Code: 1010)

What steps have you taken to resolve the issue?

1. Used the troubleshooter (no errors found)
2. Changed to specific domains (doesnt work)
3. Tried another domain (works)

Was the site working with SSL prior to adding it to Cloudflare?
Yes

What steps have you taken to resolve the issue?

1. Visit the certificate origin page
2. Generate certificate with default settings

Have you tried from another browser and/or incognito mode?

Yes, no luck

Please attach a screenshot of the error:
See above

[Laudian]

@aaronhatton

This zone is either not part of your account, or you do not have access to it.

The domain exported-report.zip uses Google nameservers, see Network Tools: DNS,IP,Email. You need to add your site to Cloudflare by changing the Nameservers before you can issue an Origin certificate.

[mcorreia]

Hi there.

Is this still an issue? I can see you have currenlty an origin certificate issued on your zone valid until 2038.

Take care.

[aaronhatton]

Sorry for the slow response! Yes, that was indeed the problem. Google took a bit longer than anticipated to transfer the namesevers across. I was a little surprised I couldn’t provision the SSL certificate in advance but I understand that verification is needed first. Perhaps better error messages could have avoided this issue.