workers-help
pages-help
general-help
durable-objects
workers-and-pages-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
⚡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd-runtime
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows
vite-plugin
Next 13.4.2, not-found.js, and 404's on Pages
appDir
setup on Next 13.4.2, I created a not-found.js
file to return a custom 404 and not the Next default. On my local setup using npm run dev
this works correctly and gives me my custom page.
On Pages, it returns the Next default error message and not the custom page. ...Create multiple Pages projects with a monorepo

"Unable to find pages project" error with GitHub Actions
- name: Deploy uses: https://github.com/cloudflare/pages-action@v1 with: apiToken: $ {{ secrets.CLOUDFLARE_API_TOKEN }} accountID: $ {{ secrets.CLOUDFLARE_ACCOUNT_ID }} projectName: "website" directory: "dist" gitHubToken: $ {{ secrets.GITHUB_TOKEN }}
- name: Deploy uses: https://github.com/cloudflare/pages-action@v1 with: apiToken: $ {{ secrets.CLOUDFLARE_API_TOKEN }} accountID: $ {{ secrets.CLOUDFLARE_ACCOUNT_ID }} projectName: "website" directory: "dist" gitHubToken: $ {{ secrets.GITHUB_TOKEN }}
CSS not updated.

Error getting domain name working.
Nuxt (3.5.0) SSG rendered HTML differs on a custom domain.
uwvloereruit.nl
differs from uve-website.pages.dev
. The content served by the custom domain is different (in a visually breaking way) while its is fully server side generated HTML. I have verified this difference by examining both response bodies with Postman. Specific components are somehow rerendered and comments indicating conditional renders are not present in the HTML returned by the custom domain which indicate to me this is not a Nuxt issue?
I tried various possible solutions and non of them have worked....Weird Pages NextJS build error
Error 522 when trying to setup a vanity domain via cf for saas
One repository -> multiple pages projects
Add another person to my Cloudflare page
How to set up cloudflare to send an email (or emit some event) after page build is deployed?
ERR_TOO_MANY_REDIRECTS -Tunnel is healthy

ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command failed with ENOENT: node_modules/vite/bin/vite.js
npm install -g pnpm && pnpm i && pnpm build
My environment is also using the following node version : NODE_VERSION 18.14.0
...Deploy a production vs preview build using GitHub Actions
required npm token is not working
NODE_VERSION
environment set to 16.15.0
. After deployment I see a npm ERR! Incorrect or missing password.
error. I added my NPM token as NPM_TOKEN
but not working. What to do
Middleware OK on `pages.dev`, not on custom domain?
_middleware.js
stuff with CF Pages, in an attempt to use it instead of an existing CF Worker. The middleware worked perfectly on the pages.dev
version — but, on the custom-domain version from that pages.dev
, only the HTML files were affected even though the middleware was supposed to apply for all routes and files (location: functions/_middleware.js
, thus presumably for all routes).
To be more specific: on the pages.dev
version, a number of custom headers (such as for caching) were added to a variety of file types, including CSS and image files; but, on the custom-domain version, this worked for only the HTML files.
Is there something special I have to do in the domain’s DNS, or elsewhere, to make the middleware work properly on the custom domain, too? (And I did remove the custom domain’s routes from the Worker for the test, so the Worker shouldn’t have been interfering.)...nodejs_compat Compatability issue.

robots.txt