I see some sites force verify bot check on certain routes only, is it a pro feature ?
I see some sites force verify bot check on certain routes only, is it a pro feature ?
Cdoes anyone know if it's possible to combine vue ssr with pages?
I
IIt's definitely possible. https://developers.cloudflare.com/pages/framework-guides/deploy-a-nuxt-site/
CI think i found a way
CI'm not using nuxt though
MOh great, thnx Isaac
HHere's a fun thing, you can now use
adapter-cloudflareadapter-cloudflare-workers anymoreHIt was created for use when Pages didn't exist(i.e., you had to manage asset serving yourself), but now with Pages/Workers Assets, it isn't really necessary anymore, other than for backwards compatibility
Wwhat do you mean by not showing up?
Wlooks ok to me
Wboth show the same content
Dreally?
Wyep
Dmy browser says it "can't find the server"
Di think it may have been a problem with my cookies im sorry to waste your time
SDNS cache
Resolving DNS entries is complex and involves many parties (your browser, your operating system, your router and then your ISP's resolver).
Any and all of these intermediaries can potentially cache your DNS request and serve stale content, even though you just updated it.
Quick fixes:
- Use a different browser
- Restart your PC
- Change your DNS from your ISP's to Cloudflare's: https://one.one.one.one/dns/#setup-instructions
Tis it just me or env variables don't work in deployment when you set a root directory?
HHi, tried starting with a new project but did not get far.
I'm following https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/get-started/
npm create cloudflare@latest -- site --framework=next && cd site && npm run dev results in ReferenceError: await is not defined. I chose pretty much the defaults. Node is v22.12.0 and npm is 11.0.0. What am I missing?I'm following https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/get-started/
TWhen I deploy the next.js project which include dynamic routes, I failed.
TIs there any solution with this?
DI'm planning on potentially creating a chron-job to delete old deployments. Before I do, is it necessary? Is there any harm with keeping old deployments around? Any fees that are assessed for using up storage or something?
Cyou're not charged for them or anything, other then normal costs of their functions being invoked if you have any/they are called, the only real harm with keeping them around is you can't delete projects with more then 100 or so deployments (takes too much time for them to clean up), have to delete the deployments first: https://developers.cloudflare.com/pages/platform/known-issues/#delete-a-project-with-a-high-number-of-deployments
but you can always just wait to delete them then
but you can always just wait to delete them then
Kanyone successfully enable
I'm using this in pages
using this in DO worker
already following https://github.com/cloudflare/workers-sdk/issues/1908
https://developers.cloudflare.com/pages/functions/local-development/
https://developers.cloudflare.com/workers/wrangler/commands/#dev-1
error below:
annyone can point me how to work on local with https?
wrangler pages devI'm using this in pages
using this in DO worker
already following https://github.com/cloudflare/workers-sdk/issues/1908
https://developers.cloudflare.com/pages/functions/local-development/
https://developers.cloudflare.com/workers/wrangler/commands/#dev-1
error below:
annyone can point me how to work on local with https?
DI encountered the same problem. This issue is discussed here: https://github.com/cloudflare/next-on-pages/issues/925. Removing
awaitAhh, thanks a bunch! I'll try removing it and let's see if other problems arise. Then again I don't really need local dev that much, what I would want to have is a GitHub Action that deploys any branches to some branch specific path on Cloudflare, e.g. https://site.com/test/branch-name/ with
robots.txtWait what. I just booted up my dev workstation and for the luls of it, ran 
Maybe there is something auto-updating under the hood but that would be very scary. Packages.json should have zero changes.
npm run devGlad to hear it seems to be resolved for you! As for me, the situation hasn’t changed...
Eif you rename the repo it may still work due to the redirect github puts in, though thats not always totally reliable
Fhello, i finished coding my website but have no idea how cloudflare works. i went to pages to upload, but it wont let me upload some files i have (media) because theyre too big :/
HIf they are over the 25 MiB limit then you will have to host them somewhere else, like R2
Ncan i use some kind of websocket connection to pull a pages deployment's logs?
UHow I can make cloudflare page, deploy when public forks open Pull Request?
Cmy pages deployment is ignoring
NODE_VERSIONdoesn't build anymore because it's on 18.17 or something
Chad to put it in wrangler.toml
Pso i read that cf has 100 custom domains in the free plan. what is this exactly? is it what i think it is? the domain domain? like domain name? does this mean pages.dev can be changed?
CYep, you can point a custom domain to the pages site
Ahi, noob question. I'm deploying a nuxt site using
wrangler pages deploy
Aodd, now it works 
OHi everyone! Is it possible to make an existing preview deployment to become production one? I'm writing CD for my app and I want to first deploy frontend to staging and when new verison of backend is up then change enviroment to prod for minimalizing version mismatch time for backend.
Pdam, i thought that was a paid feature in hosts
