← Pages / pages / platform

Known issues

Here are some known bugs and issues with Cloudflare Pages:

• GitHub and GitLab are currently the only supported platforms for automatic CI/CD builds. Direct Upload allows you to integrate your own build platform or upload from your local computer.

• Incremental builds are currently not supported in Cloudflare Pages.

• Uploading a /functions directory through the dashboard's Direct Upload option does not work (refer to Using Functions in Direct Upload).

• Commits/PRs from forked repositories will not create a preview. Support for this will come in the future.

• If you deploy using the Git integration, you cannot switch to Direct Upload later. However, if you already use a Git-integrated project and do not want to trigger deployments every time you push a commit, you can disable/pause automatic deployments. Alternatively, you can delete your Pages project and create a new one pointing at a different repository if you need to update it.

• *.pages.dev subdomains currently cannot be changed. If you need to change your *.pages.dev subdomain, delete your project and create a new one.

• Hugo builds automatically run an old version. To run the latest version of Hugo (for example, 0.101.0), you will need to set an environment variable. Set HUGO_VERSION to 0.101.0 or the Hugo version of your choice.

• By default, Cloudflare uses Node 12.18.0 in the Pages build environment. If you need to use a newer Node version, refer to the Build configuration page for configuration options.

• For users migrating from Netlify, Cloudflare does not support Netlify's Forms feature. Pages Functions are available as an equivalent to Netlify's Serverless Functions.

• It is currently not possible to add a custom domain with

  • a wildcard, for example, *.domain.com.
  • a Worker already routed on that domain.

• It is currently not possible to add a custom domain with a Cloudflare Access policy already enabled on that domain.

• Cloudflare's Load Balancer does not work with *.pages.dev projects; an Error 1000: DNS points to prohibited IP will appear.

• When adding a custom domain, the domain will not verify if Cloudflare cannot validate a request for an SSL certificate on that hostname. In order for the SSL to validate, ensure Cloudflare Access or a Cloudflare Worker is allowing requests to the validation path: http://{domain_name}/.well-known/acme-challenge/*.

• Advanced Certificates cannot be used with Cloudflare Pages due to Cloudflare for SaaS's certificate prioritization.

• Functions does not currently support adding/removing polyfills, so your bundler (for example, webpack) may not run.

• passThroughOnException() is not currently available for Advanced Mode Pages Functions (Pages Functions which use an _worker.js file).

• passThroughOnException() is not currently as resilient as it is in Workers. We currently wrap Pages Functions code in a try...catch ↗ block and fallback to calling env.ASSETS.fetch(). This means that any critical failures (such as exceeding CPU time or exceeding memory) may still throw an error.

If you would like to enable Cloudflare Access ↗] for your preview deployments and your *.pages.dev domain, you must:

1. In the Cloudflare dashboard, go to the Workers & Pages page.

   Go to Workers & Pages ↗

2. Select your Pages project.

3. Go to Settings > Enable access policy.

4. Select Manage on the Access policy created for your preview deployments.

5. Under Access > Applications, select your project.

6. Select Configure.

7. Under Public hostname, in the Subdomain field, delete the wildcard (*) and select Save. You may need to change the Application name at this step to avoid an error.

At this step, your *.pages.dev domain has been secured behind Access. To resecure your preview deployments:

8. Go back to your Pages project > Settings > General > and reselect Enable access policy.
9. Review that two Access policies, one for your *.pages.dev domain and one for your preview deployments (*.<YOUR_SITE>.pages.dev), have been created.

If you have a custom domain and protected your *.pages.dev domain behind Access, you must:

10. In the Cloudflare dashboard ↗, go to Zero Trust > Access controls > Applications. Select Create new application > Self-hosted and private.
11. Select Add public hostname and select your custom domain from the Domain dropdown menu.
12. Configure your access rules to define who can reach the Access authentication page.
13. Select Create.

If you have an issue that you do not see listed, let the team know in the Cloudflare Workers Discord. Get your invite at discord.cloudflare.com ↗, and share your bug report in the #pages-general channel.

You may not be able to delete your Pages project if it has a high number (over 100) of deployments. The Cloudflare team is tracking this issue.

As a workaround, you can use wrangler pages deployment delete to delete deployments individually. After you delete your deployments, you will be able to delete your Pages project.

npx wrangler pages deployment delete <DEPLOYMENT_ID> --project-name <PROJECT_NAME>

Use the --force flag to skip the confirmation prompt and to force deletion of aliased deployments.

To delete all your deployments for a particular project name, you could run the following shell script:

prod_id=""
while :; do
  ids=$(npx wrangler pages deployment list --project-name <PROJECT_NAME> --json | jq -r '.[].Id')
  to_delete=$(echo "$ids" | grep -v -F -x "$prod_id" | grep .)
  [ -z "$to_delete" ] && { echo "Done. Production: $prod_id"; break; }
  echo "Deleting $(echo "$to_delete" | wc -l | tr -d ' ') deployments..."
  while IFS= read -r id; do
    if ! npx wrangler pages deployment delete "$id" --project-name <PROJECT_NAME> --force 2>&1 | tee /tmp/wrangler-del.log | grep -q "Successfully deleted"; then
      grep -q "active production deployment" /tmp/wrangler-del.log && prod_id="$id"
    fi
  done <<< "$to_delete"
done

Note that this will not delete the active production deployment if one exists.

Cloudflare Load Balancing will not work without the host header set. To use a Pages project as target, make sure to select Add host header when creating a pool, and set both the host header value and the endpoint address to your pages.dev domain.

Refer to Use Cloudflare Pages as origin for a complete tutorial.