The CloudFlare online chat support person suggested I change the 'target' field of the cname record

The CloudFlare online chat support person suggested I change the 'target' field of the cname record from supplier-portal-fe.pages.dev to s2.supplier-portal-fe.pages.dev, which I did.. but that doesn't seem right to me.

Rrdutton The CloudFlare online chat support person suggested I change the 'target' field ...

Hello, I’m Allie!•9/14/23, 11:34 AM

What is serving your

www

www

subdomain?

rduttonOP•9/14/23, 11:34 AM

Partially served by Cloudflare and partially on AWS

Rrdutton The CloudFlare online chat support person suggested I change the 'target' field ...

zegevlier•9/14/23, 11:36 AM

That indeed seems odd... Did they mention why they recommend that?

Zzegevlier That indeed seems odd... Did they mention why they recommend that?

rduttonOP•9/14/23, 11:37 AM

They 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

zegevlier•9/14/23, 11:37 AM

Did you add the subdomain under Custom Domains on the pages project?

rduttonOP•9/14/23, 11:38 AM

Original message was deleted

rduttonOP•9/14/23, 11:40 AM

I'm not 100% sure on that, but I can try unproxying it. That record was how the pages interface created it for me

rduttonOP•9/14/23, 11:41 AM

Yep, am removing now

Original message was deleted

rduttonOP•9/14/23, 11:43 AM

Ok, great, it's working thanks!

rduttonOP•9/14/23, 11:43 AM

Not sure why it was proxied ..

rduttonOP•9/14/23, 11:44 AM

Now it's working I don't need to touch it

rduttonOP•9/14/23, 11:44 AM

thanks for the assistance

nasimuddin01•9/14/23, 2:31 PM

I am trying to deploy in pages, but for some reason nodejs install is getting hanged. It's been 11 minuts and still nothing.

nasimuddin01•9/14/23, 2:31 PM

It's been happening for the last couple of days

nasimuddin01•9/14/23, 2:32 PM

Last time it ran for 36m 36s but still couldn't download the node version.

nasimuddin01•9/14/23, 2:33 PM

Does anybody know why it's happening?

Cyb3r-Jak3•9/14/23, 2:34 PM

This 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

nasimuddin01•9/14/23, 2:34 PM

okay.

nasimuddin01•9/14/23, 2:35 PM

Thanks for the hint.

nasimuddin01•9/14/23, 2:35 PM

Will check

nasimuddin01•9/14/23, 2:38 PM

Thanks a lot @Cyb3r-Jak3 it worked.

kian•9/14/23, 3:53 PM

would likely be pointed towards to using Wrangler to upload the assets from your own CI

kovbassa•9/14/23, 4:43 PM

Hello Cloudflare Community!

We need your help and hints on solving our case. The initial conditions are:

Two Cloudflare accounts:

-- Account A: has our main domain and a lot of stuff is already served on this domain (let’s call it siteA.com)
-- 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

We want to have the setup where subdomains will serve content from another account project:

project-prod.siteA.com -> prod.project.com
project-staging.siteA.com -> staging.project.com
project-subdir.siteA.com/subdir -> subdir.project.com/subdir

Trying to set up this with CNAME’s causes 1014 CF Error. After reaching the support, asking to allow pointing to our another account we got the response to use Cloudflare for SaaS. But there is only one Fallback Origin which we can set. Are we missing something? Is there a way to set up this like we want.

P.S.: Please, let me know if this message should go to another place.

kian•9/15/23, 12:55 AM

https://discord.com/channels/595317990191398933/1134543567004631121/1151266002173165570

Vero•9/15/23, 12:50 PM

Hey Pages devs Pages

, 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

Google Docs

Build Caching Early Beta Testing Sign Up

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...

zegevlier•9/16/23, 6:33 AM

Last 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

Rabid•9/16/23, 11:30 AM

I 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

orientusprime•9/16/23, 6:42 PM

Is there a Sveltekit template from Cloudflare for showcasing how to use Cloudflare KV, DO, R2 etc within Sveltekit project?

Adi•9/17/23, 11:29 AM

Is there an active issue going on with pages deployments? (via wrangler)?
I just noticed that my deployments for the past day have been failing

Adi•9/17/23, 11:30 AM

I only just noticed this because there was no indication from the

wrangler deploy

wrangler deploy

command, it succeeds with no visible error logs. But on the console we see the red exclamation mark which when you hover says "The deployment failed"

Adi•9/17/23, 11:33 AM

Thankfully 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

87a3c637ba57424b09104e5ade4caffe

87a3c637ba57424b09104e5ade4caffe

if that helps. Let me know if. there is any additional info I can give that would help

Adi•9/17/23, 11:35 AM

Just 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)

✨ Uploading Worker bundle
✨ Uploading _routes.json
✨ Deployment complete! Take a peek over at https://addc7a35.asy.pages.dev

✨ Uploading Worker bundle
✨ Uploading _routes.json
✨ Deployment complete! Take a peek over at https://addc7a35.asy.pages.dev

But clearly it failed, as we can see.
Any help would be greatly appreciated!

James•9/17/23, 12:43 PM

I'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

AAdi Just to clarify the point on wrangler. According to the CI logs the wrangler dep...

James•9/17/23, 12:45 PM

Can you share a deployment ID please?

James•9/17/23, 12:46 PM

?pages-deployment-id

Flare•9/17/23, 12:46 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.

James•9/17/23, 12:47 PM

Wrangler doesn't wait for functions deployment it seems, so something with your Functions are causing an issue.

JJames Can you share a deployment ID please?

Adi•9/17/23, 12:49 PM

Sure 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

addc7a35-1aad-429f-9bc2-8c14f6b93159addc7a35-1aad-429f-9bc2-8c14f6b93159
f5136429-cac9-4980-8757-e6d4db4d0630f5136429-cac9-4980-8757-e6d4db4d0630
8bdcc17d-149a-4c52-a564-15b993faa8c78bdcc17d-149a-4c52-a564-15b993faa8c7

JJames Wrangler doesn't wait for functions deployment it seems, so something with your ...

Adi•9/17/23, 12:50 PM

Hmm interesting, I'll look what could be failing code wise

AAdi Sure thing. Also kudos on the helpflare bot use, was just going to ask what a de...

James•9/17/23, 12:51 PM

Uncaught TypeError: se2 is not a function at bundledWorker-0.1344021811677698.mjs:46264:13 at bundledWorker-0.1344021811677698.mjs:46266:2

Uncaught TypeError: se2 is not a function at bundledWorker-0.1344021811677698.mjs:46264:13 at bundledWorker-0.1344021811677698.mjs:46266:2

James•9/17/23, 12:51 PM

Something in your bundled Functions, yeah

Adi•9/17/23, 12:52 PM

Hmm ok, must be related to the Nuxt 3.6 -> 3.7 upgrade. I'll look into it, thank you for the error log

James•9/17/23, 12:53 PM

Hopefully that'll help you figure it out!

JJames ```Uncaught TypeError: se2 is not a function at bundledWorker-0.1344021811677698...

Adi•9/17/23, 12:54 PM

Btw is there any way we can view these error logs? Or do you need some special access for that?

AAdi Btw is there any way we can view these error logs? Or do you need some special a...

James•9/17/23, 12:55 PM

Unfortunately not

I had to ping someone on the Pages team to pull the logs for that

Adi•9/17/23, 12:55 PM

Ahh ok, gotcha

The CloudFlare online chat support person suggested I change the 'target' field of the cname record

Similar Threads

Similar Threads

Similar Threads