Hi! Did you set up caching for that custom domain? If so, you can remove it (and do a manual purge),

Hi! Did you set up caching for that custom domain? If so, you can remove it (and do a manual purge), Pages has internal caching that makes enabling cache rules redundant for assets hosted with Pages

DDaniFoldi Hi! Did you set up caching for that custom domain? If so, you can remove it (and...

VMSS•8/21/23, 7:19 AM

Thank you Dani, I will check it!

DDaniFoldi Hi! Did you set up caching for that custom domain? If so, you can remove it (and...

VMSS•8/21/23, 7:48 AM

How long can it take? I thought that about 30 seconds are enough after purging, but I cannot see any changes after deploying the new build. When I access the assets through the path from custom domain, I am able to see the latest assets, but when I look at manifest, they are the same old icons.

chientrm.com•8/21/23, 9:14 AM

Does Pages build store built app in a git repository?

kian•8/21/23, 9:15 AM

Nope

Kkian Nope

chientrm.com•8/21/23, 9:32 AM

wouldn't that help reduce storage usage?

Bbuckett Just bumped into an issue with setting up a custom domain for a pages site faile...

Erisa•8/21/23, 2:30 PM

Sorry about that, this is something that the Pages team are aware of and are planning to improve on. In the meantime we created this guide on things to look out for, including CAA records https://developers.cloudflare.com/pages/platform/debugging-pages/

isaacryu•8/21/23, 6:32 PM

seemed to have started running into this

isaacryu•8/21/23, 6:33 PM

Guessing it's a cloudflare side problem? pages-helpFailing deploy (Could not generate the asset manifest)

defidivvy•8/21/23, 6:34 PM

Just jumped in here for the same reason as @isaacryu > Having that exact issue

zegevlier•8/21/23, 6:35 PM

We're raising it with the team! Thank you for reporting it

isaacryu•8/21/23, 6:35 PM

Thanks

Iisaacryu seemed to have started running into this

tizianschönijahn•8/21/23, 6:35 PM

Same Error for me

Ttizianschönijahn Same Error for me

isaacryu•8/21/23, 6:35 PM

Issue on their end, theyre working on it

defidivvy•8/21/23, 6:36 PM

OK thanks!

zegevlier•8/21/23, 6:38 PM

https://www.cloudflarestatus.com/incidents/rbcwy68wvxp3

Cloudflare Pages deployment failures

Zzegevlier https://www.cloudflarestatus.com/incidents/rbcwy68wvxp3

Isx•8/21/23, 6:46 PM

The one time I wake up early to experiment with some deployments…

Zzegevlier https://www.cloudflarestatus.com/incidents/rbcwy68wvxp3

chientrm.com•8/21/23, 6:47 PM

are we practicing GitHub methodology?

Iisaacryu seemed to have started running into this

Matheus•8/21/23, 6:53 PM

Same error here...

MMatheus Same error here...

itsmatteomanf•8/21/23, 6:54 PM

There is an incident declared, follow the status page posted just above

Matheus•8/21/23, 6:55 PM

Thank you! I'm following it

defidivvy•8/21/23, 7:32 PM

It's working now. Thanks for the quick responses and fix Pages

Ddefidivvy It's working now. Thanks for the quick responses and fix <:Pages:818921758794448...

chientrm.com•8/21/23, 7:47 PM

You're welcome

. Thank to the team, not me.

Cchientrm.com You're welcome 👍. Thank to the team, not me.

zegevlier•8/21/23, 7:51 PM

Please don't imply that you're an employee

chientrm.com•8/22/23, 11:13 AM

error: failed to download node-v16.20.1-linux-x64.tar.gz

error: failed to download node-v16.20.1-linux-x64.tar.gz

Erisa•8/22/23, 11:14 AM

That's an issue on the side of node, it shouldnt happen if you switch to Pages build system v2 and set a major version for node e.g.

NODE_VERSION=16

NODE_VERSION=16

Erisa•8/22/23, 11:14 AM

Since v2 will prepackage the latest of each major version

EErisa That's an issue on the side of node, it shouldnt happen if you switch to Pages b...

chientrm.com•8/22/23, 11:18 AM

I didn't notice. Now I removed

NODE_VERSION=16

NODE_VERSION=16

and it works.

Elliot Hesp•8/22/23, 1:21 PM

Hm getting this myself weirdly

14:16:54.454    Trying to update node-build... ok
14:16:54.967    Downloading node-v18.13.0-linux-x64.tar.gz...
14:16:54.967    -> https://nodejs.org/dist/v18.13.0/node-v18.13.0-linux-x64.tar.gz
14:20:43.754    error: failed to download node-v18.13.0-linux-x64.tar.gz
14:20:43.755    -> https://nodejs.org/dist/v18.13.0/node-v18.13.0-linux-x64.tar.gz

14:16:54.454    Trying to update node-build... ok
14:16:54.967    Downloading node-v18.13.0-linux-x64.tar.gz...
14:16:54.967    -> https://nodejs.org/dist/v18.13.0/node-v18.13.0-linux-x64.tar.gz
14:20:43.754    error: failed to download node-v18.13.0-linux-x64.tar.gz
14:20:43.755    -> https://nodejs.org/dist/v18.13.0/node-v18.13.0-linux-x64.tar.gz

Elliot Hesp•8/22/23, 1:24 PM

https://nodejs.org/dist/v18.13.0/node-v18.13.0-linux-x64.tar.gz doesn't seem to work

Pepper•8/22/23, 10:34 PM

Is there any way to see why a pages deployment failed? Wrangler doesn't give any errors, but the page is stuck on deployment not found and when I go to the dashboard it says deployment failed. It is probably just an issue with my code because deploying an earlier version of it works, but idk how to find what went wrong because usually when there is a problem either wrangler will catch it or it will still deploy but the function will give an error.

Erisa•8/22/23, 10:47 PM

?pages-deployment-id

Flare•8/22/23, 10:47 PM

The Pages deployment ID is a unique build identifier.
It's the UUID in the browser bar (for example, a URL would be

dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_ID

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.

Erisa•8/22/23, 10:48 PM

There are some errors that are not made visible to the user for one reason or another - If you have this deployment ID, someone from Cloudflare can check it for you

DDeleted User `Your project has too many deployments to be deleted, follow this guide to delet...

Unsmart•8/22/23, 11:29 PM

What happens when you run the script?

EErisa There are some errors that are not made visible to the user for one reason or an...

Pepper•8/22/23, 11:35 PM

Ok, thank you for the information. It was a silly mistake I was able to figure out myself, I was just missing a couple commas. Though it is strange that wrangler didn't let me know because usually it detects stuff like that.

Erisa•8/22/23, 11:40 PM

Where were the commas?

Pepper•8/23/23, 12:09 AM

The commas were separating a list that was in a javascript dictionary. The list was generated by a python script that isn't on cloudflare, and a mistake in that caused there to be no commas separating the list values.

Erisa•8/23/23, 12:12 AM

Interesting!

Erisa•8/23/23, 12:12 AM

Glad you got it working

Aajgeiss0702 purging the cache shouldnt matter since it shouldnt be cached, right? and I thi...

ajgeiss0702•8/23/23, 2:08 AM

Any ideas on why the page is still being cached?
An additional piece of info I realized I should give is that a ctrl+shift+r causes the new changes to come through, but if i do a normal reload again, sometimes the old cached version is served again

if not, any ideas if there is somewhere else I might be able to ask about this?

Aajgeiss0702 Any ideas on why the page is still being cached? An additional piece of info I r...

Cyb3r-Jak3•8/23/23, 2:11 AM

Sounds like it might be cached in your browser. Does it look correct in an incoginto window

ajgeiss0702•8/23/23, 2:13 AM

appears cached in a private window too

ajgeiss0702•8/23/23, 2:14 AM

and i thought it might be the browser caching it too, but the devtools claims it is a non-cached 200 response (also, iirc the browser doesnt usually cache html? that could be outdated though)

stavros-k•8/23/23, 10:06 AM

I want to have a page (redirect) rule to only apply when the "main" backend is not responding. Is that possible?

Ccomagoosie Has there been any indication that `node_compat` will come to pages? Don't want ...

Cyb3r-Jak3•8/23/23, 1:24 PM

I believe all compatibility flags should be in pages. You just have to do it via the dashboard

14:16:54.454 Trying to update node-build... ok 14:16:54.967 Downloading node-v18.13.0-linux-x64.tar.gz... 14:16:54.967 -> https://nodejs.org/dist/v18.13.0/node-v18.13.0-linux-x64.tar.gz 14:20:43.754 error: failed to download node-v18.13.0-linux-x64.tar.gz 14:20:43.755 -> https://nodejs.org/dist/v18.13.0/node-v18.13.0-linux-x64.tar.gz

Hi! Did you set up caching for that custom domain? If so, you can remove it (and do a manual purge),

Similar Threads

Similar Threads

Similar Threads