Here are some known bugs and issues that we're aware of with Cloudflare Pages:
- Source code hosting tools besides GitHub—for instance, BitBucket or Gitlab—are not currently supported.
- Pages currently only supports a single project per repository. Monorepos or repositories with multiple codebases/applications currently can't deploy more than one project to Pages at a time.
- Once you've selected a GitHub repository for your Pages application, it can't be changed. Please remove/delete your Pages project and create a new one pointing at a different repository if you need to update it.
- pages.dev subdomains currently can't 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 instance, 0.80.0), you'll need to set an environment variable. Set
0.80.0or the Hugo version of your choice.
- By default, we use Node
12.18.0in the Pages build environment. If you need to use a newer Node version, refer to the for configuration options.
- For users migrating from Netlify, Cloudflare does not support Netlify's Forms and Serverless Functions features. Cloudflare Pages does not directly support HTTP header customization, but it can be done through Workers. Refer to the guide for more information.
- It is currently not possible to add a custom domain with a wildcard, e.g. *.domain.com.
- Cloudflare Pages is not supported with Cloudflare Apps; you may see a 1014 error if you use both in a deployment.