If a deployment is stuck as queued, is there anything that I can do to check it's status/ prompt it

RR.Thompson If a deployment is stuck as queued, is there anything that I can do to check it'...

�

𝚄𝚗𝚔𝚗𝚘𝚠𝚗.•12/18/24, 11:58 PM

Cancel it and retry it... idk? See the build log?

R

R.ThompsonOP•12/19/24, 12:01 AM

This is hilarious. Over the past two days, I've done it nearly one hundred times. But I thought I would try it one more time to send you the build log. But it worked!!! So, thanks!

RR.Thompson This is hilarious. Over the past two days, I've done it nearly one hundred times...

�

𝚄𝚗𝚔𝚗𝚘𝚠𝚗.•12/19/24, 9:13 AM

that is hilarious and you're welcome.

J

Jadugar_Jaggu•12/19/24, 10:09 AM

warp

R

R1CH•12/19/24, 6:03 PM

Is GitLab connectivity broken? Can't re-authenticate after the "Cloudflare Pages is not properly installed on your Git account, this may cause deployments to fail." error. "An unknown error occurred. Contact your account team or Cloudflare support: https://cfl.re/3WgEyrH."

RR1CH Is GitLab connectivity broken? Can't re-authenticate after the "Cloudflare Pages...

�

𝚄𝚗𝚔𝚗𝚘𝚠𝚗.•12/19/24, 6:27 PM

Check the Permissions you gave to the cf pages app

R

R1CH•12/19/24, 6:41 PM

What scopes does it need if it's not requesting them automatically?

R

R1CH•12/19/24, 7:11 PM

Looks like it magically fixed itself after trying for the 10th time

S

Stephen•12/20/24, 12:39 AM

Is it possible to set a custom domain for preview URLs? So instead of hash.my-project.pages.dev it'd be hash.previews.my-domain.com?

SStephen Is it possible to set a custom domain for preview URLs? So instead of hash.my-pr...

H

Hello, I’m Allie!•12/20/24, 2:48 AM

Not automatically. You can point a Custom Domain to hash-based preview deployment via the API, but not automatically

HHello, I’m Allie!Not automatically. You can point a Custom Domain to hash-based preview deploymen...

S

Stephen•12/20/24, 2:55 AM

Thanks... I think custom preview domains would make it easier to support session cookies in preview environments (a bit like https://vercel.com/docs/deployments/preview-deployment-suffix)

A

aphaduriendur•12/20/24, 2:57 AM

Hey all.
hey all. Could someone help with this issue:
Like this works fine: https://portfolio-nuxt-abasu0713.nuxt.dev/
But the actual custom domain doesn't work (https://arkobasu.space/). I can visit a page under it like for example: https://arkobasu.space/blogs and then click Home navigation. which brings me to the root of the site. Which then works fine.. But if I refresh this page.. I get weird errors.

Home | Arko Basu

Arko's personal space for learning and trying out new technology.

Home | Arko Basu

Arko's personal space for learning and trying out new technology.

A

aphaduriendur•12/20/24, 2:57 AM

much appreciate the help

W

Walshy•12/20/24, 4:41 AM

Ask the Nuxt team?

K

kane•12/20/24, 2:19 PM

hello

, im curious doos pages builder recognize the new bun lockfile format

bun.lock

bun.lock

? seems like it falls back to using

npm install

npm install

R

rennesz•12/20/24, 9:15 PM

hey guys, i just added a

.nvmrc

.nvmrc

with

lts/iron

lts/iron

in it and i get the following error. looks like deployment doesn't work when using

lts/*

lts/*

syntax?

15:46:59.046    Detected the following tools from environment: nodejs@lts/iron
15:46:59.046    , npm@9.6.7
15:46:59.046    Installing nodejs lts/iron
15:46:59.046    
15:46:59.114    mkdir: cannot create directory '/opt/buildhome/.asdf/installs/nodejs/lts/iron': No such file or directory
15:46:59.582    Trying to update node-build... ok
15:46:59.615    node-build: definition not found: 20
15:46:59.623    Error: Exit with error code: 1
15:46:59.623        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
15:46:59.624        at Object.onceWrapper (node:events:652:26)
15:46:59.624        at ChildProcess.emit (node:events:537:28)
15:46:59.624        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
15:46:59.635    Failed: build command exited with code: 1
15:47:02.391    Failed: error occurred while running build command

15:46:59.046    Detected the following tools from environment: nodejs@lts/iron
15:46:59.046    , npm@9.6.7
15:46:59.046    Installing nodejs lts/iron
15:46:59.046    
15:46:59.114    mkdir: cannot create directory '/opt/buildhome/.asdf/installs/nodejs/lts/iron': No such file or directory
15:46:59.582    Trying to update node-build... ok
15:46:59.615    node-build: definition not found: 20
15:46:59.623    Error: Exit with error code: 1
15:46:59.623        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
15:46:59.624        at Object.onceWrapper (node:events:652:26)
15:46:59.624        at ChildProcess.emit (node:events:537:28)
15:46:59.624        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
15:46:59.635    Failed: build command exited with code: 1
15:47:02.391    Failed: error occurred while running build command

15:46:59.046    Detected the following tools from environment: nodejs@lts/iron
15:46:59.046    , npm@9.6.7
15:46:59.046    Installing nodejs lts/iron
15:46:59.046    
15:46:59.114    mkdir: cannot create directory '/opt/buildhome/.asdf/installs/nodejs/lts/iron': No such file or directory
15:46:59.582    Trying to update node-build... ok
15:46:59.615    node-build: definition not found: 20
15:46:59.623    Error: Exit with error code: 1
15:46:59.623        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
15:46:59.624        at Object.onceWrapper (node:events:652:26)
15:46:59.624        at ChildProcess.emit (node:events:537:28)
15:46:59.624        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
15:46:59.635    Failed: build command exited with code: 1
15:47:02.391    Failed: error occurred while running build command

15:46:59.046    Detected the following tools from environment: nodejs@lts/iron
15:46:59.046    , npm@9.6.7
15:46:59.046    Installing nodejs lts/iron
15:46:59.046    
15:46:59.114    mkdir: cannot create directory '/opt/buildhome/.asdf/installs/nodejs/lts/iron': No such file or directory
15:46:59.582    Trying to update node-build... ok
15:46:59.615    node-build: definition not found: 20
15:46:59.623    Error: Exit with error code: 1
15:46:59.623        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
15:46:59.624        at Object.onceWrapper (node:events:652:26)
15:46:59.624        at ChildProcess.emit (node:events:537:28)
15:46:59.624        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
15:46:59.635    Failed: build command exited with code: 1
15:47:02.391    Failed: error occurred while running build command

R

rennesz•12/20/24, 9:27 PM

Update: It works after setting

.nvmrc

.nvmrc

to

, but I'm wondering if it's possible to use the

lts/

lts/

syntax?

Rrennesz Update: It works after setting `.nvmrc` to `20`, but I'm wondering if it's possi...

C

Chaika•12/20/24, 9:30 PM

it's just asdf under the hood, so should be all the same limitations as here:

https://github.com/asdf-vm/asdf-nodejs

Many version managers allow you to use partial versions (e.g. v10) or NodeJS codenames (e.g. lts/hydrogen) in version files, which are resolved at runtime. However, this can be risky as it is not guaranteed that all developers will use the same version, leading to non-reproducibility. In asdf, we prioritize reproducibility, so you cannot use partial versions or codenames in a .tool-versions file.

R

rennesz•12/20/24, 9:31 PM

Thanks!

M

Mini•12/21/24, 12:24 PM

I see some sites force verify bot check on certain routes only, is it a pro feature ?

C

Celeste•12/21/24, 12:47 PM

does anyone know if it's possible to combine vue ssr with pages?

MMini I see some sites force verify bot check on certain routes only, is it a pro feat...

I

Isaac McFadyen•12/21/24, 3:24 PM

That would be a WAF rule. https://developers.cloudflare.com/waf/custom-rules/create-dashboard/

CCeleste does anyone know if it's possible to combine vue ssr with pages?

I

Isaac McFadyen•12/21/24, 3:24 PM

It's definitely possible. https://developers.cloudflare.com/pages/framework-guides/deploy-a-nuxt-site/

C

Celeste•12/21/24, 3:31 PM

I think i found a way

C

Celeste•12/21/24, 3:32 PM

I'm not using nuxt though

IIsaac McFadyen That would be a WAF rule. https://developers.cloudflare.com/waf/custom-rules/cre...

M

Mini•12/21/24, 3:37 PM

Oh great, thnx Isaac

JJkRoe Hi, I’m planning to use SvelteKit to develop a full-stack website, but I’m a bit...

H

Hello, I’m Allie!•12/22/24, 7:08 AM

Here's a fun thing, you can now use

adapter-cloudflare

adapter-cloudflare

on Workers. I would just not use

adapter-cloudflare-workers

adapter-cloudflare-workers

anymore

H

Hello, I’m Allie!•12/22/24, 7:09 AM

It 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

W

Walshy•12/22/24, 8:52 PM

what do you mean by not showing up?

W

Walshy•12/22/24, 8:52 PM

looks ok to me

W

Walshy•12/22/24, 8:53 PM

both show the same content

D

desmond•12/22/24, 8:53 PM

really?

W

Walshy•12/22/24, 8:53 PM

yep

D

desmond•12/22/24, 8:53 PM

my browser says it "can't find the server"

D

desmond•12/22/24, 8:54 PM

i think it may have been a problem with my cookies im sorry to waste your time

S

SuperHelpflare•12/22/24, 9:38 PM

DNS 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

T

Two•12/24/24, 1:17 AM

is it just me or env variables don't work in deployment when you set a root directory?

H

heze•12/24/24, 10:32 AM

Hi, tried starting with a new project but did not get far.

npm create cloudflare@latest -- site --framework=next && cd site && npm run dev

npm create cloudflare@latest -- site --framework=next && cd site && npm run dev

results in

ReferenceError: await is not defined

ReferenceError: await is not defined

. I chose pretty much the defaults. Node is

v22.12.0

v22.12.0

and npm is

11.0.0

11.0.0

. What am I missing?

I'm following https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/get-started/

T

TDA•12/24/24, 6:16 PM

When I deploy the next.js project which include dynamic routes, I failed.

T

TDA•12/24/24, 6:16 PM

Is there any solution with this?

D

dapperdandev•12/24/24, 7:00 PM

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

Ddapperdandev I'm planning on potentially creating a chron-job to delete old deployments. Befo...

C

Chaika•12/24/24, 7:19 PM

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

K

Kholis•12/25/24, 3:18 AM

anyone successfully enable

wrangler pages dev

wrangler pages dev

in https mode? with binding to a local durable object that https enabled too

I'm using this in pages

# command
NODE_EXTRA_CA_CERTS=./certs/ca.crt wrangler pages dev --https-cert-path ./certs/server.crt --https-key-path ./certs/server.key

# wrangle.toml
[dev]
ip = "0.0.0.0"
port = 443
local_protocol = "https"

# command
NODE_EXTRA_CA_CERTS=./certs/ca.crt wrangler pages dev --https-cert-path ./certs/server.crt --https-key-path ./certs/server.key

# wrangle.toml
[dev]
ip = "0.0.0.0"
port = 443
local_protocol = "https"

# command
NODE_EXTRA_CA_CERTS=./certs/ca.crt wrangler pages dev --https-cert-path ./certs/server.crt --https-key-path ./certs/server.key

# wrangle.toml
[dev]
ip = "0.0.0.0"
port = 443
local_protocol = "https"

# command
NODE_EXTRA_CA_CERTS=./certs/ca.crt wrangler pages dev --https-cert-path ./certs/server.crt --https-key-path ./certs/server.key

# wrangle.toml
[dev]
ip = "0.0.0.0"
port = 443
local_protocol = "https"

using this in DO worker

# command
wrangler dev --config ./wrangler.worker.do-websocket.preview.toml --https-cert-path ./certs/server.crt --https-key-path ./certs/server.key

# wrangle.toml
[dev]
ip = "0.0.0.0"
port = 8443
local_protocol = "https"

# command
wrangler dev --config ./wrangler.worker.do-websocket.preview.toml --https-cert-path ./certs/server.crt --https-key-path ./certs/server.key

# wrangle.toml
[dev]
ip = "0.0.0.0"
port = 8443
local_protocol = "https"

# command
wrangler dev --config ./wrangler.worker.do-websocket.preview.toml --https-cert-path ./certs/server.crt --https-key-path ./certs/server.key

# wrangle.toml
[dev]
ip = "0.0.0.0"
port = 8443
local_protocol = "https"

# command
wrangler dev --config ./wrangler.worker.do-websocket.preview.toml --https-cert-path ./certs/server.crt --https-key-path ./certs/server.key

# wrangle.toml
[dev]
ip = "0.0.0.0"
port = 8443
local_protocol = "https"

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:

node:internal/event_target:1101
  process.nextTick(() => { throw err; });
                           ^
Error: Cannot proxy to `wrangler dev` session for class "DOWebsocket" because it uses HTTPS. Please remove the `--local-protocol`/`dev.local_protocol` option.
...
(file:///Users/petrukngantuk/oprek/labs/mandor/node_modules/@sveltejs/kit/src/utils/fork.js:23:16)

Node.js v22.12.0

node:internal/event_target:1101
  process.nextTick(() => { throw err; });
                           ^
Error: Cannot proxy to `wrangler dev` session for class "DOWebsocket" because it uses HTTPS. Please remove the `--local-protocol`/`dev.local_protocol` option.
...
(file:///Users/petrukngantuk/oprek/labs/mandor/node_modules/@sveltejs/kit/src/utils/fork.js:23:16)

Node.js v22.12.0

node:internal/event_target:1101
  process.nextTick(() => { throw err; });
                           ^
Error: Cannot proxy to `wrangler dev` session for class "DOWebsocket" because it uses HTTPS. Please remove the `--local-protocol`/`dev.local_protocol` option.
...
(file:///Users/petrukngantuk/oprek/labs/mandor/node_modules/@sveltejs/kit/src/utils/fork.js:23:16)

Node.js v22.12.0

node:internal/event_target:1101
  process.nextTick(() => { throw err; });
                           ^
Error: Cannot proxy to `wrangler dev` session for class "DOWebsocket" because it uses HTTPS. Please remove the `--local-protocol`/`dev.local_protocol` option.
...
(file:///Users/petrukngantuk/oprek/labs/mandor/node_modules/@sveltejs/kit/src/utils/fork.js:23:16)

Node.js v22.12.0

annyone can point me how to work on local with https?

Hheze Hi, tried starting with a new project but did not get far. `npm create cloudflar...

D

derarion•12/25/24, 4:41 AM

I encountered the same problem. This issue is discussed here: https://github.com/cloudflare/next-on-pages/issues/925. Removing

await

await

makes the dev server work, but I’m also unsure about the side effects of doing this.

Dderarion I encountered the same problem. This issue is discussed here: https://github.com...

H

heze•12/25/24, 5:49 AM

Ahh, 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.txt

robots.txt

that disallows indexing these.

Dderarion I encountered the same problem. This issue is discussed here: https://github.com...

H

heze•12/25/24, 6:10 AM

Wait what. I just booted up my dev workstation and for the luls of it, ran

npm run dev

npm run dev

and now it works. I don't think I've changed anything but computers don't usually work differently on another day if nothing was changed.

Maybe there is something auto-updating under the hood but that would be very scary. Packages.json should have zero changes.

Hheze Wait what. I just booted up my dev workstation and for the luls of it, ran `npm ...

D

derarion•12/25/24, 8:24 AM

Glad to hear it seems to be resolved for you! As for me, the situation hasn’t changed...

If a deployment is stuck as queued, is there anything that I can do to check it's status/ prompt it

DNS cache

Quick fixes:

Similar Threads

Similar Threads

DNS cache

Quick fixes:

Similar Threads