Cloudflare Docs
Visit Pages on GitHub
Set theme to dark (⇧+D)

Debugging Pages

When setting up your Pages project, you may encounter various errors that prevent you from successfully deploying your site. This guide gives an overview of some common errors and solutions.

​​ Check your build log

You can review build errors in your Pages build log. To access your build log:

  1. Log in to the Cloudflare dashboard.
  2. In Account Home, go to Pages.
  3. Select your Pages project > View build.

After logging in to the Cloudflare dashboard, access the build log by following the instructions above

Possible errors in your build log are included in the following sections.

​​ Initializing build environment

Possible errors in this step could be caused by improper installation during Git integration.

To fix this in GitHub:

  1. Log in to your Github account.
  2. Go to Settings from your user icon > find Applications under Integrations.
  3. Find Cloudflare Pages > Configure > scroll down and select Uninstall.
  4. Re-authorize your Github user/organisation on the Cloudflare dashboard.

To fix this in GitLab:

  1. Log in to your GitLab account.
  2. Go to Preferences from your user icon > Applications.
  3. Find Cloudflare Pages > scroll down and select Revoke.

Be aware that you need a role of Maintainer or above to successfully link your repository, otherwise the build will fail.

​​ Cloning git repository

Possible errors in this step could be caused by lack of Git Large File Storage (LFS). Check your LFS usage by referring to the GitHub and GitLab documentation.

Make sure to also review your submodule configuration by going to the .gitmodules file in your root directory. This file needs to contain both a path and a url property.

Example of a valid configuration:

[submodule "example"]
path = example/path
url = git://

Example of an invalid configuration:

[submodule "example"]
path = example/path


[submodule "example"]
url = git://

​​ Building application

Possible errors in this step could be caused by faulty setup in your Pages project. Review your build command, output folder and environment variables for any incorrect configuration.

​​ Deploying to Cloudflare’s global network

Possible errors in this step could be caused by incorrect Pages Functions configuration. Refer to the Functions documentation for more information on Functions setup.

If you are not using Functions or have reviewed that your Functions configuration does not contain any errors, review the Cloudflare Status site for Cloudflare network issues that could be causing the build failure.

​​ Differences between and custom domains

If your custom domain is proxied (orange-clouded) through Cloudflare, your zone’s settings such as Auto Minify and caching will apply.

If you are experiencing issues with a framework, like Nuxt.js, only on the custom domain, review if Auto Minify is enabled (log in to the Cloudflare dashboard > Speed > Optimization > Auto Minify) for HTML and disable it.

If you are experiencing issues with new content not being shown, go to Rules > Page Rules in the Cloudflare dashboard and check for a Page Rule with Cache Everything enabled. If present, remove this rule as Pages handles its own cache.

If you are experiencing errors on your custom domain but not on your domain, go to DNS > Records in the Cloudflare dashboard and set the DNS record for your project to be DNS Only (grey cloud). If the error persists, review your zone’s configuration.

​​ Domain stuck in verification

If your custom domain has not moved from the Verifying stage in the Cloudflare dashboard, refer to the following debugging steps.

​​ Blocked HTTP validation

Pages uses HTTP validation and needs to hit an HTTP endpoint during validation. If another Cloudflare product is in the way (such as Access, a redirect, a Worker, etc.), validation cannot be completed.

To check this, run a curl against your domain hitting /.well-known/acme-challenge/randomstring. For example:

$ curl -I
HTTP/2 302
date: Mon, 03 Apr 2023 08:37:39 GMT
access-control-allow-credentials: true
cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
server: cloudflare
cf-ray: 7b1ffdaa8ad60693-MAN

In the example above, you are redirecting to Cloudflare Access (as shown by the Location header). In this case, you need to disable Access over the domain until it the domain is verified. After it the domain is verified, Access can be reenabled.

You will need to do the same kind of thing for Redirect Rules or a Worker example too.

​​ Missing CAA records

If nothing is blocking the HTTP validation, then you may be missing Certification Authority Authorization (CAA) records. This is likely if you have disabled Universal SSL or use an external provider.

To check this, run a dig on the custom domain’s apex (or zone, if this is a liberated zone). For example:

$ dig
dig CAA
; <<>> DiG 9.10.6 <<>> CAA
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59018
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
; EDNS: version: 0, flags:; udp: 4096
;; ANSWER SECTION: 300 IN CAA 0 issue ""
;; Query time: 92 msec
;; WHEN: Mon Apr 03 10:15:51 BST 2023
;; MSG SIZE rcvd: 76

In the above example, there is only a single CAA record which is allowing Amazon to issue ceritficates.

To resolve this, you will need to add the following CAA records which allows all of the Certificate Authorities (CAs) Cloudflare uses to issue ceritificates: 300 IN CAA 0 issue "" 300 IN CAA 0 issue "; cansignhttpexchanges=yes" 300 IN CAA 0 issue "" 300 IN CAA 0 issue "; cansignhttpexchanges=yes" 300 IN CAA 0 issuewild "" 300 IN CAA 0 issuewild "; cansignhttpexchanges=yes" 300 IN CAA 0 issuewild "" 300 IN CAA 0 issuewild "; cansignhttpexchanges=yes"

​​ Resources

If you need additional guidance on build errors, contact your Cloudflare account team (Enterprise) or refer to the Support Center for guidance on contacting Cloudflare Support.

You can also ask questions in the Pages section of the Cloudflare Developers Discord.