That indeed seems odd... Did they mention why they recommend that?
That indeed seems odd... Did they mention why they recommend that?
RThey referred to this document - https://developers.cloudflare.com/pages/how-to/custom-branch-aliases/ But that's related to branches.. and I am just deplying the main branch at the moment
ZDid you add the subdomain under Custom Domains on the pages project?
R
RI'm not 100% sure on that, but I can try unproxying it. That record was how the pages interface created it for me
RYep, am removing now
ROk, great, it's working thanks!
RNot sure why it was proxied ..
RNow it's working I don't need to touch it 
Rthanks for the assistance
NI am trying to deploy in pages, but for some reason nodejs install is getting hanged. It's been 11 minuts and still nothing.
NIt's been happening for the last couple of days
NLast time it ran for 36m 36s but still couldn't download the node version.
NDoes anybody know why it's happening?
CThis happens occasionally where node takes a while to download from the site . If you are on build image v2 then you can try using a different version which is cached but I forget what versions are saved. Maybe try using v18
Nokay.
NThanks for the hint.
NWill check
N
K- would likely be pointed towards to using Wrangler to upload the assets from your own CI
KHello Cloudflare Community!
We need your help and hints on solving our case. The initial conditions are:
-- Account B: here is another project hosted, which we can’t move to account A, meaning we don’t wanna move it to another github org. (let’s call it project.com)
P.S.: Please, let me know if this message should go to another place.
We need your help and hints on solving our case. The initial conditions are:
- Two Cloudflare accounts:
-- Account B: here is another project hosted, which we can’t move to account A, meaning we don’t wanna move it to another github org. (let’s call it project.com)
- The project.com has multiple deployments: production, staging and another, which serves it’s content into subdirectory:-- Production: prod.project.com-- Staging: staging.project.com-- Subdirectory: subdir.project.com/subdir
- project-prod.siteA.com -> prod.project.com
- project-staging.siteA.com -> staging.project.com
- project-subdir.siteA.com/subdir -> subdir.project.com/subdir
P.S.: Please, let me know if this message should go to another place.
VHey Pages devs
, for those who don't know, you can sign up for Pages Build Cache Beta testing filling out this form https://forms.gle/2rQ8FCTtn2CUqmpk9 It currently supports Next.js, Gatsby and Astro, you can ask questions and share your feedback in build-caching-beta
, for those who don't know, you can sign up for Pages Build Cache Beta testing filling out this form https://forms.gle/2rQ8FCTtn2CUqmpk9 It currently supports Next.js, Gatsby and Astro, you can ask questions and share your feedback in build-caching-betaGoogle Docs
Pages is excited to introduce build cache - a feature designed to speed up your build times by caching and reusing previously computed project dependencies and build outputs. 
This is a very early version of the feature, and while we're excited about its potential, we recommend not enabling it on critical projects just yet. Please note that...
Pages is excited to introduce build cache - a feature designed to speed up your build times by caching and reusing previously computed project dependencies and build outputs. This is a very early version of the feature, and while we're excited about its potential, we recommend not enabling it on critical projects just yet. Please note that...
ZLast time the "tlds available soon" were listed there for several months before they got added. I wouldn't hold my breath for any that aren't even listed there
RI have my web app being served from the root domain pointed at my webapp.pages.dev, and my api served from api.domain.com. Because of this, I have to handle a lot of OPTIONS preflight requests. I'd like to be able to cache these via cloudflare, but it seems like Request Method isn't an available filter for Cache Rules
OIs there a Sveltekit template from Cloudflare for showcasing how to use Cloudflare KV, DO, R2 etc within Sveltekit project?
AIs there an active issue going on with pages deployments? (via wrangler)?
I just noticed that my deployments for the past day have been failing
I just noticed that my deployments for the past day have been failing
AI only just noticed this because there was no indication from the
wrangler deployThankfully pages uses the last successful deployment, so the site is not down, but seems like new deploys can't be made.
Would really appreciate some help
My account id is
Would really appreciate some help
My account id is
87a3c637ba57424b09104e5ade4caffeJust to clarify the point on wrangler. According to the CI logs the wrangler deployment succeeded (e.g for the last preview deployment this was the terminal log)
But clearly it failed, as we can see.
Any help would be greatly appreciated!
But clearly it failed, as we can see.
Any help would be greatly appreciated!
JI've seen a couple of these recently, another at https://community.cloudflare.com/t/wrangler-pages-publish-always-fails-tried-both-with-nextjs-and-with-astro-templates/554749. I wonder if related 
JCan you share a deployment ID please?
J?pages-deployment-id
FThe Pages deployment ID is a unique build identifier.
It's the UUID in the browser bar (for example, a URL would be
This ID can help troubleshoot some issues with Pages builds so if you have a failing build make sure you grab that ID for the Pages team to use.
It's the UUID in the browser bar (for example, a URL would be
dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_ID where the deployment ID looks something like a398d794-7322-4c97-96d9-40b5140a8d9b).This ID can help troubleshoot some issues with Pages builds so if you have a failing build make sure you grab that ID for the Pages team to use.
JWrangler doesn't wait for functions deployment it seems, so something with your Functions are causing an issue.
ASure thing. Also kudos on the helpflare bot use, was just going to ask what a deployment ID is XD
Here are the last three failed deployment IDs
Here are the last three failed deployment IDs
addc7a35-1aad-429f-9bc2-8c14f6b93159f5136429-cac9-4980-8757-e6d4db4d06308bdcc17d-149a-4c52-a564-15b993faa8c7
AHmm interesting, I'll look what could be failing code wise
JSomething in your bundled Functions, yeah
AHmm ok, must be related to the Nuxt 3.6 -> 3.7 upgrade. I'll look into it, thank you for the error log
JHopefully that'll help you figure it out!
ABtw is there any way we can view these error logs? Or do you need some special access for that?
JUnfortunately not 
I had to ping someone on the Pages team to pull the logs for that
I had to ping someone on the Pages team to pull the logs for thatAAhh ok, gotcha
JGitHub
Which Cloudflare product(s) does this pertain to? Wrangler core What version(s) of the tool(s) are you using? 3.8.0 What version of Node are you using? 18.17.1 What operating system are you using? ...
