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 uploads allow you to integrate your own build platform or upload from your local computer.
 - Monorepos or repositories with multiple codebases/applications currently cannot use the automatic GitHub/GitLab integration to build multiple sites from the same repository. However, Direct Uploads can be used to upload a monorepo as separate Pages projects from your own computer.
 - After you have selected a GitHub/GitLab repository for your Pages application, it cannot be changed. Remove/delete your Pages project and create a new one pointing at a different repository if you need to update it.
 *.pages.devsubdomains currently cannot be changed. If you need to change your*.pages.devsubdomain, 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.80.0), you will need to set an environment variable. SetHUGO_VERSIONto0.80.0or the Hugo version of your choice. - By default, Cloudflare uses Node 
12.18.0in 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. An equivalent to Netlify’s Serverless Functions is currently in beta.
 - It is currently not possible to add a custom domain with a wildcard, for example, 
*.domain.com. - It is currently not possible to add a custom domain with 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.devprojects; anError 1000: DNS points to prohibited IPwill appear. - A GitHub or GitLab account cannot be attached to more than one Cloudflare account.
 - Functions (beta) does not currently support adding/removing polyfills, so your bundler (for example, Webpack) may not run.
 - When adding a custom domain, the domain may get stuck verifying due to being unable to validate a request for an SSL 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/pki-validation/*. - Incremental builds are currently not supported in Cloudflare Pages.
 - A Direct Upload of a 
/functionsdirectory does not work (refer to Using Functions in Direct Upload). 
Enabling Access on your *.pages.dev domain
If you would like to enable Cloudflare Access] for your preview deployments and your *.pages.dev domain, you must:
- Log in to Cloudflare dashboard.
 - From Account Home, select Pages.
 - Select your Pages project.
 - Go to Settings > Enable access policy.
 - Select Edit on the Acccess policy created for your preview deployments.
 - In Edit, go to Overview.
 - In the Subdomain field, delete the wildcard (
*) and select Save application. 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:
- Go back to your Pages project > Settings > General > and reselect Enable access policy.
 - Review that two Access policies, one for your 
*.pages.devdomain 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:
- Select Add an application > Self hosted in the Cloudflare Zero Trust dashboard.
 - Input an Application name and select your custom domain from the Domain dropdown menu.
 - Select Next and configure your access rules to define who can reach the Access authentication page.
 - Select Add application.
 
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.gg/cloudflaredev, and share your bug report in the #pages-general channel.