the alias goes into branch.xxxx.pages.dev and not into the actual branch.customdomain.com

S

sudo__su--OP•8/10/24, 5:59 PM

hehe i know i was like damm

Ssudo__su--the alias goes into branch.xxxx.pages.dev and not into the actual branch.customd...

I

Isaac McFadyen•8/10/24, 5:59 PM

Not sure what you mean? With that guide, your domain

branch-name.customdomain.com

branch-name.customdomain.com

branch-name.customdomain.com

branch-name.customdomain.com will go to the branch on the Pages project.

S

sudo__su--OP•8/10/24, 6:00 PM

though i don know if you could CNAME a CNAME wildcard i dobut it

like .*customdomin.com which would go to *.xxxx.pages.dev

I

Isaac McFadyen•8/10/24, 6:00 PM

When I said "no wildcard" I just meant that for each branch you want that to happen for, you need to add them. I don't think you can do

*.customdomain.com

*.customdomain.com

*.customdomain.com

*.customdomain.com

S

sudo__su--OP•8/10/24, 6:02 PM

hmmm i wonder does this have a place i can auto script this (my worry is then my DNS is bombarded with old branches ) lol

S

sudo__su--OP•8/10/24, 6:03 PM

https://developers.cloudflare.com/pages/configuration/preview-deployments/#preview-aliases

Cloudflare Docs

Preview deployments · Cloudflare Pages docs

Preview deployments allow you to preview new versions of your project without deploying it to production. To view preview deployments:

S

sudo__su--OP•8/10/24, 6:58 PM

i tried to follow this

where im in cloudflare DNS
CNAME
branch-name branch-name.project.pages.dev

but im getting error

Connection timed out Error code 522

Connection timed out Error code 522

Connection timed out Error code 522

Connection timed out Error code 522 but it should work

Screenshot_2024-08-10_at_12.56.15_PM.png

S

sudo__su--OP•8/10/24, 6:58 PM

if i have to manually do this (im sure i can API automate this CNAME)but im trying to just get this part working

Ssudo__su--i tried to follow this where im in cloudflare DNS CNAME branch-name branch-...

I

Isaac McFadyen•8/10/24, 7:05 PM

Did you add it as a custom domain in Pages?

I

Isaac McFadyen•8/10/24, 7:05 PM

You need to do that first.

S

sudo__su--OP•8/10/24, 7:10 PM

ya

S

sudo__su--OP•8/10/24, 7:10 PM

so it seems like this only works on production build not preview dyanamic (is that on this list for features on this)

IIsaac McFadyen Did you add it as a custom domain in Pages?

W

Walshy•8/10/24, 7:19 PM

if it's 522ing, you didn't do this or it isn't active

W

Walshy•8/10/24, 7:20 PM

it works otherwise we wouldn't have made the guide

N

nico•8/11/24, 8:28 PM

Hi everyone, I have had 1000+ deployments and used the "delete-all-deployments" node application from cloudflare to make it clean again, but is there a possibility to only store the deployments from the last 60-90 days or something?

S

sadsciencee•8/11/24, 10:27 PM

getting this error when using web crypto crypto.randomUUID(); in a pages project. this works fine in local dev but fails on deploy. we're only using it in the client side react code

Error: Failed to publish your Function. Got error: Uncaught Error: Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope. To fix this error, perform this operation within a handler.

Error: Failed to publish your Function. Got error: Uncaught Error: Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope. To fix this error, perform this operation within a handler.

Error: Failed to publish your Function. Got error: Uncaught Error: Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope. To fix this error, perform this operation within a handler.

Error: Failed to publish your Function. Got error: Uncaught Error: Disallowed operation called within global scope. Asynchronous I/O (ex: fetch() or connect()), setting a timeout, and generating random values are not allowed within global scope. To fix this error, perform this operation within a handler.

has anyone else experienced this issue? I see a lot of suggestions to just set up a worker that lets you get a uuid. not ideal to be doing that all the time in otherwise synchronous code...

seems like this should be supported on pages. maybe I'm using the wrong version. I do not have node_compat enabled.

build node version: 20.10.0

Ssadsciencee getting this error when using web crypto crypto.randomUUID(); in a pages project...

H

Hard@Work•8/12/24, 8:16 AM

Are you using a framework that does SSR? That might be what is causing it...

S

summer•8/12/24, 10:26 AM

Hey, does anyone know how I can check the detailed logs for a failed deployment? All I'm getting is this (attached pic), and sometimes it just works after a retry...

J

jjjrmy•8/12/24, 3:45 PM

is there ever going to be parity with Workers/Pages features. so annoying that the CLI asks you to do something and doesn't work for Pages.

Jjjjrmy is there ever going to be parity with Workers/Pages features. so annoying that t...

C

Chaika•8/12/24, 3:46 PM

eventually: https://blog.cloudflare.com/pages-and-workers-are-converging-into-one-experience

The Cloudflare Blog

Bringing a unified developer experience to Cloudflare Workers and P...

Today we’re excited to announce that over the next year we will be working to bring together the best traits and attributes you know and love from each product into one powerful platform!

Ssummer Hey, does anyone know how I can check the detailed logs for a failed deployment?...

C

Chaika•8/12/24, 3:46 PM

there's no more detailed logs then that which you can see about user command failures, unless there's some debug flags/etc which can enable more verbose logging

J

jjjrmy•8/12/24, 3:47 PM

@Chaika it's not the dashboard that's the problem, it's the functionality: pages-helpBuild Requests `account_id` in Wrangler.toml but fails with `account_id`
I run into issues like this all the time - what's the point of using pages if it doesn't work

Jjjjrmy <@905865275583365161> it's not the dashboard that's the problem, it's the functi...

C

Chaika•8/12/24, 3:48 PM

And the idea of convergence isn't bringing just the dashboard together, but the entirety of the two products into one
If you want help with your build failure, share wrangler toml in the post

L

laurent•8/12/24, 9:26 PM

is cloudflare pages broken? I can't deploy a basic vite app (nothing at the URL)

W

Walshy•8/12/24, 9:27 PM

we'd have a lot more people yelling if so haha

L

laurent•8/12/24, 9:38 PM

not setting any node version breaks create vite@latest + react deployments. (fixed with NODE_VERSION = 20.9.0 env variable)

A

April•8/13/24, 9:29 AM

Why I cannot bind the d1 env even I already put the env using the dashboard?

S

Stoke•8/13/24, 3:46 PM

Hey friends, I'm trying to add a Tail Worker to my Pages deployment like so:

tail_consumers = [{service = "<TAIL_WORKER_NAME>"}]

tail_consumers = [{service = "<TAIL_WORKER_NAME>"}]

tail_consumers = [{service = "<TAIL_WORKER_NAME>"}]

tail_consumers = [{service = "<TAIL_WORKER_NAME>"}]. But sadly it says

Configuration file for Pages projects does not support "tail_consumers"

Configuration file for Pages projects does not support "tail_consumers"

Configuration file for Pages projects does not support "tail_consumers"

Configuration file for Pages projects does not support "tail_consumers". I assume that means Pages projects can't be tail producers? What's the recommended way to get logs pushed to my central log storage (Loki)? I'm using Pages with Hono because I'm serving static assets too and according to the docs serving static assets using regular Workers is deprecated. Thanks!

F

Foreignity•8/13/24, 6:16 PM

Hello everyone, I'm using Cloudflare Pages with Supabase Auth for Auth System, I'm using locally .env file for the secret keys, but I'm wondering I can access the live keys, is it through a function, do I need to return the secret through a function?

D

DiceOfDeath•8/14/24, 9:22 AM

Hey i am using CF Pages (currently on free plan) my 95% traffic comes from the india but CF has the global IP for my pages site which has the average latency of 150ms from india, is there a way i can ask cloudflare to move my pages to indian datacenter or if i go with the paid plan is that possible all i need to reduce this latency which is downgrading my site performance.

DDiceOfDeath Hey i am using CF Pages (currently on free plan) my 95% traffic comes from the i...

H

Hard@Work•8/14/24, 9:26 AM

A Paid Plan on your Custom Domain may improve routing, but note that we have seen some Indian ISPs like to route outside of the country anyway

H

Hard@Work•8/14/24, 9:26 AM

As a test, could you try seeing what the latency is with your

pages.dev

pages.dev

domain?

D

DiceOfDeath•8/14/24, 9:26 AM

C:\Users\mayan>ping pages.dev

Pinging pages.dev [2606:4700:9a63:4e94:1bca:0:8d61:1552] with 32 bytes of data:
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=35ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms

Ping statistics for 2606:4700:9a63:4e94:1bca:0:8d61:1552:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 35ms, Average = 33ms

C:\Users\mayan>ping -4 pages.dev

Pinging pages.dev [104.18.20.135] with 32 bytes of data:
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58

Ping statistics for 104.18.20.135:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 34ms, Average = 34ms

C:\Users\mayan>ping pages.dev

Pinging pages.dev [2606:4700:9a63:4e94:1bca:0:8d61:1552] with 32 bytes of data:
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=35ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms

Ping statistics for 2606:4700:9a63:4e94:1bca:0:8d61:1552:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 35ms, Average = 33ms

C:\Users\mayan>ping -4 pages.dev

Pinging pages.dev [104.18.20.135] with 32 bytes of data:
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58

Ping statistics for 104.18.20.135:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 34ms, Average = 34ms

C:\Users\mayan>ping pages.dev

Pinging pages.dev [2606:4700:9a63:4e94:1bca:0:8d61:1552] with 32 bytes of data:
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=35ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms

Ping statistics for 2606:4700:9a63:4e94:1bca:0:8d61:1552:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 35ms, Average = 33ms

C:\Users\mayan>ping -4 pages.dev

Pinging pages.dev [104.18.20.135] with 32 bytes of data:
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58

Ping statistics for 104.18.20.135:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 34ms, Average = 34ms

C:\Users\mayan>ping pages.dev

Pinging pages.dev [2606:4700:9a63:4e94:1bca:0:8d61:1552] with 32 bytes of data:
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=35ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms
Reply from 2606:4700:9a63:4e94:1bca:0:8d61:1552: time=33ms

Ping statistics for 2606:4700:9a63:4e94:1bca:0:8d61:1552:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 35ms, Average = 33ms

C:\Users\mayan>ping -4 pages.dev

Pinging pages.dev [104.18.20.135] with 32 bytes of data:
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58
Reply from 104.18.20.135: bytes=32 time=34ms TTL=58

Ping statistics for 104.18.20.135:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 34ms, Maximum = 34ms, Average = 34ms

DDiceOfDeath ``` C:\Users\mayan>ping pages.dev Pinging pages.dev [2606:4700:9a63:4e94:1bca:0...

H

Hard@Work•8/14/24, 9:27 AM

Sorry, I meant with your Project's

pages.dev

pages.dev

. Though the results you showed do look promising...

H

Hard@Work•8/14/24, 9:27 AM

So like

diceofdeath.pages.dev

diceofdeath.pages.dev

diceofdeath.pages.dev

diceofdeath.pages.dev, as an example

D

DiceOfDeath•8/14/24, 9:29 AM

damn it is the same as i ping the

pages.dev

pages.dev

but with custom domain its not

D

DiceOfDeath•8/14/24, 9:30 AM

do ig it is the problem with custom domain ?

DDiceOfDeath do ig it is the problem with custom domain ?

H

Hard@Work•8/14/24, 9:30 AM

Yeah, that is probably the case then. Upgrading to a paid plan should give you better routing

D

DiceOfDeath•8/14/24, 9:31 AM

gotcha thanksss

D

DiceOfDeath•8/14/24, 9:31 AM

Hey i see that is 20 bucks per month

D

DiceOfDeath•8/14/24, 9:32 AM

D

DiceOfDeath•8/14/24, 9:32 AM

are you talking about this domain plan ?

DDiceOfDeath are you talking about this domain plan ?

H

Hard@Work•8/14/24, 9:32 AM

Yes. There are higher plans, but you shouldn't need them to get better routing

D

DiceOfDeath•8/14/24, 9:33 AM

are you sure this 20 bucks plan can fix my problem bro

HHard@Work Are you using a framework that does SSR? That might be what is causing it...

S

sadsciencee•8/14/24, 9:33 AM

yup. remix. you hit the nail on the head. @Hard@Work

I had

const defaultConfig = {...etc, id: crypto.randomUUID()}

const defaultConfig = {...etc, id: crypto.randomUUID()}

const defaultConfig = {...etc, id: crypto.randomUUID()}

const defaultConfig = {...etc, id: crypto.randomUUID()} in my global scope. oops

a few days ago I got around this by doing a stupid hand-rolled id generator, was planning to come back around to proper UUID but just wanted to keep things moving

today I was testing bulk inserts and can't for the life of me figure out why some UUIDs are actually random and other ones stayed the same...foreign key conflicts abound

so moral of the story. turns out cloudflare was trying to protect me from my foolish ways. I finally traced the repeating id to the defaultConfig and once that bug was fixed, switched my hand-rolled thing back to the web crypto UUI

T

Tim Apple•8/14/24, 11:48 AM

Hey everyone, thought I'd try my luck here with some help. I've had my A and CNAME records set up for a week on Cloudflare DNS but it isn't propogating. I've checked the community support without success. Anyone would be able to help here? We are looking to launch in a week so really appreciate the help here

SStoke Hey friends, I'm trying to add a Tail Worker to my Pages deployment like so: `ta...

I

ItsWendell•8/14/24, 12:44 PM

It seems like that very, very soon (might be in the next couple of days, according to some git activity in workers-sdk / workerd) pages-like asset support is coming for Workers, which means that if you have some patience you could migrate your setup to that and use tail workers. If you can't wait for that you could look into using / creating a seperate logger within your Pages deployment that queues / push the logs out after every request with e.g. waitUntil. You could do this by binding to the context as a Hono middleware and pushing after a request for example.

TTim Apple Hey everyone, thought I'd try my luck here with some help. I've had my A and CNA...

H

Hard@Work•8/14/24, 1:29 PM

It looks like it has propagated a bit more on my end, but in the locations it is failing, I also see that you are missing the Cloudflare Nameservers. I would check with your registrar to see if they are having issues

HHard@Work It looks like it has propagated a bit more on my end, but in the locations it is...

C

Chaika•8/14/24, 1:31 PM

it's our good friend dnssec DNS_PROBE_FINISHED_NXDOMAIN

J

John•8/14/24, 4:58 PM

Pages seems slow today for no apparent reason

the alias goes into branch.xxxx.pages.dev and not into the actual branch.customdomain.com

Similar Threads

Similar Threads

Similar Threads