This error is likely caused by the Name Servers Cloudflare provides not matching on your domain registrar. Head to your domain registrar and verify the Name Servers entered as seen on your "Custom Domain" page within PageCloud.

The Name Servers Cloudflare provides do not match on your domain registrar. Head to your domain registrar and verify the Name Servers are exactly as displayed on your "Custom Domain" page within PageCloud.

4. My site still shows .pagecloud.com when entering in my custom domain name.

This is usually due to a Forward being pointed to your .pagecloud.com address on your domain registrar instead of setting up the A-Record and CNAME information. Head to your domain registrar and remove the forward that is set up. Make sure to add in the the DNS records on your domain registrar to properly point your custom domain. You can review all of the require A-Records here.

5. My site won't load when adding https.

If your site is not loading when using https, this is a sign you custom domain DNS records are not set up correctly. You can review the DNS records in our Connecting a Custom Domain to PageCloud walkthrough guide.

6. My site is giving me a "Not secure" warning.

If your site is giving you a "Not secure" warning when heading to your custom domain, This could either mean your DNS records are not set up correctly, or there is content on your page that is not secure. You can review the DNS records in our Connecting a Custom Domain to PageCloud walkthrough guide. If you have content that was added to your page from a non-secure source, this will also trigger a "Not Secure" warning. Uploading the content directly to PageCloud, or using a service that supports https will remove this warning.

7. My domain registrar does not support Name Servers.

If your domain registrar does not support Name Servers, You can use our Recommended Approach for point your custom domain. This method uses CNAMEs and Forwarding records to point your custom domain name.

8. My domain registrar does not support CNAMEs or A-Records.

If your domain registrar does not support CNAMEs or A-Records, You can use Cloudflare to point your custom domain. This method uses Name Servers to point your custom domain name.

9. Domain validation error codes.

A list of the domain validation error codes, their meaning and possible fix:

133701 - When trying to validate the domain, the validation token was not the one we set.

Resolution:

Ensure the DNS records are configured on the domain registrar.

Refresh the page and try validation again.

133702 - When trying to validate the domain, an incorrect status code was received.

Resolution:

Ensure the DNS records are configured on the domain registrar.

Refresh the page and try again.

133703 - When trying to validate the domain, we were forwarded to another domain that was not the one we expected.

Resolution: Remove redirects from domain registrar.

133704 - When trying to validate the domain, we were forwarded to a specific page that did not include the validation token.

Resolution: If there is no home page set for your site, set a page as the home page.

133705 - We cannot validate the domain because it is not a valid domain.