``` 23:16:38.104 Cloning repository... 23:16:39.261 From https://github.com/kaankutan/kutan.de

23:16:38.104    Cloning repository...
23:16:39.261    From https://github.com/kaankutan/kutan.dev
23:16:39.261     * branch            93d203ed7a7c38795b849e34333e737c69d76c0d -> FETCH_HEAD
23:16:39.261    
23:16:39.305    HEAD is now at 93d203e Image optimization added
23:16:39.306    
23:16:39.390    
23:16:39.391    Using v2 root directory strategy
23:16:39.417    Success: Finished cloning repository files
23:17:32.083    Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH
23:17:32.083    Error: Failed to publish assets. For support, join our Discord (https://discord.gg/cloudflaredev) or create a ticket and reference the deployment ID: 755daaa4-ad45-428f-be89-84e3a2857977

23:16:38.104    Cloning repository...
23:16:39.261    From https://github.com/kaankutan/kutan.dev
23:16:39.261     * branch            93d203ed7a7c38795b849e34333e737c69d76c0d -> FETCH_HEAD
23:16:39.261    
23:16:39.305    HEAD is now at 93d203e Image optimization added
23:16:39.306    
23:16:39.390    
23:16:39.391    Using v2 root directory strategy
23:16:39.417    Success: Finished cloning repository files
23:17:32.083    Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH
23:17:32.083    Error: Failed to publish assets. For support, join our Discord (https://discord.gg/cloudflaredev) or create a ticket and reference the deployment ID: 755daaa4-ad45-428f-be89-84e3a2857977

23:16:38.104    Cloning repository...
23:16:39.261    From https://github.com/kaankutan/kutan.dev
23:16:39.261     * branch            93d203ed7a7c38795b849e34333e737c69d76c0d -> FETCH_HEAD
23:16:39.261    
23:16:39.305    HEAD is now at 93d203e Image optimization added
23:16:39.306    
23:16:39.390    
23:16:39.391    Using v2 root directory strategy
23:16:39.417    Success: Finished cloning repository files
23:17:32.083    Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH
23:17:32.083    Error: Failed to publish assets. For support, join our Discord (https://discord.gg/cloudflaredev) or create a ticket and reference the deployment ID: 755daaa4-ad45-428f-be89-84e3a2857977

23:16:38.104    Cloning repository...
23:16:39.261    From https://github.com/kaankutan/kutan.dev
23:16:39.261     * branch            93d203ed7a7c38795b849e34333e737c69d76c0d -> FETCH_HEAD
23:16:39.261    
23:16:39.305    HEAD is now at 93d203e Image optimization added
23:16:39.306    
23:16:39.390    
23:16:39.391    Using v2 root directory strategy
23:16:39.417    Success: Finished cloning repository files
23:17:32.083    Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH
23:17:32.083    Error: Failed to publish assets. For support, join our Discord (https://discord.gg/cloudflaredev) or create a ticket and reference the deployment ID: 755daaa4-ad45-428f-be89-84e3a2857977

KhaganOP•10/24/24, 8:25 PM

I'm getting this error. Any solution?

KKhagan ``` 23:16:38.104 Cloning repository... 23:16:39.261 From https://github.co...

Walshy•10/24/24, 8:29 PM

consistently getting it?

WWalshy consistently getting it?

KhaganOP•10/24/24, 8:29 PM

Walshy•10/24/24, 8:29 PM

let me escalate it up

KhaganOP•10/24/24, 9:06 PM

To test it, I pushed a different commit without changing anything. It is running now. Intersting. @Walshy

Donda•10/24/24, 9:16 PM

Hey everyone does anyone know where can I read about multi tenant project with cloud flare and nextjs

DoggeSlapper•10/25/24, 8:28 AM

anyone tried nextjs 15 on pages?

DDoggeSlapper anyone tried nextjs 15 on pages?

fry69•10/25/24, 8:30 AM

Not yet supported, only 13 and 14 are so far -> https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/supported-features/

Ffry69 Not yet supported, only 13 and 14 are so far -> https://developers.cloudflare.co...

DoggeSlapper•10/25/24, 8:31 AM

yeah I saw is not supported, but didnt expect it either to be officially listed considering it's so new

DDoggeSlapper yeah I saw is not supported, but didnt expect it either to be officially listed ...

fry69•10/25/24, 8:31 AM

Well, then try out and find out?

Ffry69 Well, then try out and find out?

DoggeSlapper•10/25/24, 8:32 AM

ye I will probably do, just trying 14 for now. Then will see

DDoggeSlapper ye I will probably do, just trying 14 for now. Then will see

fry69•10/25/24, 8:33 AM

There are some neat things is 15, but I think I'll wait until React 19 is out

Ffry69 There are some neat things is 15, but I think I'll wait until React 19 is out

DoggeSlapper•10/25/24, 8:34 AM

I was using canary already for some other project I have on remix and was thinking giving it a shot

DoggeSlapper•10/25/24, 8:35 AM

is normal that my deploy appear on the pages.dev subdomain but not on the linked domain yet (linked domain appear as active already on the pages dashboard of cloudflare)

DDoggeSlapper is normal that my deploy appear on the pages.dev subdomain but not on the linked...

fry69•10/25/24, 8:40 AM

Not tried pages yet, but for simple static asset only worker I know this works to deploy a static website ->

name = "some-name"
compatibility_date = "2024-10-18"
assets = { directory = "./public" }
routes = [
  { pattern = "test.example.com", custom_domain = true }
]

name = "some-name"
compatibility_date = "2024-10-18"
assets = { directory = "./public" }
routes = [
  { pattern = "test.example.com", custom_domain = true }
]

Ffry69 There are some neat things is 15, but I think I'll wait until React 19 is out

DoggeSlapper•10/25/24, 8:41 AM

yeah specially canary, "use cache" looks dope

Ffry69 Not tried pages yet, but for simple static asset only worker I know this works t...

DoggeSlapper•10/25/24, 8:46 AM

Something is off with my deploy It only works when I have the log streaming enabled o.O

DoggeSlapper•10/25/24, 8:46 AM

JJames You are welcome to make a docs PR if you would like to 🙂

hsnilsson•10/25/24, 8:47 AM

Might be hard for me to phrase it for you (it means that note would include a statement about where those products are heading in terms of support - which is usually something that triggers internal discussions around the phrasings

). But feeling helpful I tried. Realized it's hard not to turn it into a deprecation notice though, but it's still nice to be open with this info to all the users from the beginning, so putting a PR for the last suggestion: https://github.com/cloudflare/cloudflare-docs/pull/17788
"We will continue support this solution, but our long-term support and new development will focus on deploying Next.js apps to..." messes up the meaning of the original phrasing though, but it'll change anyway before the PR get's merged, it always does

GitHub

Update get-started.mdx by hsnilsson · Pull Request #17788 · cloudfl...

Summary
People starting out new projects should easily see where the support for different products are heading. To avoid some friction. Got this info from the next-on-pages discord and it was sugg...

Vveeque Come think of it, the comment you mentioned could be all that needs to be added ...

hsnilsson•10/25/24, 8:49 AM

https://github.com/cloudflare/cloudflare-docs/pull/17788 You can help phrase it better (or completely different) by commenting on the PR I did now.

DDoggeSlapper Click to see attachment

DoggeSlapper•10/25/24, 9:07 AM

@fry69 lol I forgot I used next15 xD

DoggeSlapper•10/25/24, 9:07 AM

guess that's the issue

DDoggeSlapper anyone tried nextjs 15 on pages?

num•10/25/24, 12:03 PM

I did but i'm having errors due to some static routes not being able to be build with next on pages

RR in Tokyo Did you get help yet?

Jakov•10/26/24, 12:27 PM

NO sad

fluf•10/26/24, 4:40 PM

Cloudflare asked me to export const runtime = "edge" in order to run my api routes, and after adding them it still won't build and gives the same errors:

01:52:20.142    ⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
01:52:20.142    ⚡️ 
01:52:20.142    ⚡️     The following routes were not configured to run with the Edge Runtime:
01:52:20.143    ⚡️       - /_not-found
01:52:20.143    ⚡️       - /index
01:52:20.143    ⚡️       - /login
01:52:20.143    ⚡️       - /settings
01:52:20.143    ⚡️       - /users
01:52:20.143    ⚡️       - /websites/[id]
01:52:20.143    ⚡️       - /websites
01:52:20.144    ⚡️ 
01:52:20.144    ⚡️     Please make sure that all your non-static routes export the following edge runtime route segment config:
01:52:20.144    ⚡️       export const runtime = 'edge';

01:52:20.142    ⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
01:52:20.142    ⚡️ 
01:52:20.142    ⚡️     The following routes were not configured to run with the Edge Runtime:
01:52:20.143    ⚡️       - /_not-found
01:52:20.143    ⚡️       - /index
01:52:20.143    ⚡️       - /login
01:52:20.143    ⚡️       - /settings
01:52:20.143    ⚡️       - /users
01:52:20.143    ⚡️       - /websites/[id]
01:52:20.143    ⚡️       - /websites
01:52:20.144    ⚡️ 
01:52:20.144    ⚡️     Please make sure that all your non-static routes export the following edge runtime route segment config:
01:52:20.144    ⚡️       export const runtime = 'edge';

JJakov NO [sad](https://cdn.discordapp.com/emojis/1046808820514566274.webp?size=48&qual...

fluf•10/26/24, 4:44 PM

not the vencord emoji

fluf•10/26/24, 4:55 PM

AWS Amplify seems to solve this issue

fluf•10/27/24, 2:14 AM

Why are pages needing a runtime

fluf•10/27/24, 2:14 AM

They're not even routes

fluf•10/27/24, 2:14 AM

James•10/27/24, 10:37 AM

Yes they are

wildcat•10/27/24, 4:42 PM

QQ: How to use cryptocrypto in next.js on workers? I found if I use edgeedge runtime, cryptocryptoX509Certificate would be available

byoungz•10/27/24, 10:00 PM

Hey everyone, I have a headless WordPress setup I'm deploying to pages. I'm trying to figure out how to add a hook to my account that is using next-on-pagesnext-on-pages and a

wrangler.toml

wrangler.toml

so that when I publish a new post, it makes a build with the new post. I know how ot make the hook with WP and such, but don't see a way to add it to my account. I also don't see a way to connect my github to account since I'm deploying with the deploy command.

Anyways, how can I connect my github so that when branched ar emerged into main, it deploys

how can I add a hook to my account so everytime I make a new published post, it builds?

Thanks in advance!

Bbyoungz Hey everyone, I have a headless WordPress setup I'm deploying to pages. I'm tryi...

fry69•10/27/24, 10:04 PM

Last I checked WordPress is written in PHP, Cloudflare Pages does not support running PHP, so you can use Cloudflare only as front end for where ever you host your PHP site. Next on Pages refers to Next.js
Or am I missing something?

byoungz•10/27/24, 10:08 PM

Yeha sorry, I'm bad at explaining. I'm using

@cloudflare/next-on-pages

@cloudflare/next-on-pages

to deploy my site and didn't connect it to github. I wanted to create a hook, like this https://developers.cloudflare.com/pages/configuration/deploy-hooks/#wordpress

However, I don't see a way to add hooks to my pages project using

@cloudflare/next-on-pages

@cloudflare/next-on-pages

but see it them if I set up pages connecting to github account.

ItsWendell•10/29/24, 3:41 PM

For people interested in unstable_afterunstable_after support with next-on-pages, it just required waitUntilwaitUntil which I managed to inject into it:

https://nextjs.org/docs/canary/app/api-reference/functions/unstable_after

https://gist.github.com/ItsWendell/2413b1932d365ee6b3edccef879c589d

Kimitri•10/30/24, 6:06 AM

I have a question. I will start a new personal nextjs project, my plan was not use nextjs as a backend, instead I would create an API with workers and bun, my question is, nextjs hosted on cloudflare when I use some server side function to fetching some date from a bun api hosted in cloudflare workers too, is it redundant? Because I don't know if server side functions on nextjs with next-on-pages are the same as a bun API with workers. I don't know if in this way I was making something like double requests that would like reduce the free tier from Cloudflare

Hhsnilsson Might be hard for me to phrase it for you (it means that note would include a st...

Epailes•10/30/24, 9:16 AM

Makes sense as open next will get support from multiple orgs, and I think the long term direction at cloudflare is to combine workers/pages into one product anyway

Thanks for the heads up, I'm just going to chill on my current working versions and I'll move over when things stabilise.

Victor Berchet•10/31/24, 7:24 AM

Hey,
We have a PR up to support middleware on @opennextjs/cloudflare, check the details at https://discordapp.com/channels/1283128968140161065/1288871672035803236/1301446458352074772

VVictor Berchet Hey, We have a PR up to support middleware on @opennextjs/cloudflare, check the ...

fry69•10/31/24, 7:27 AM

Can't check out, it links to another Discord (# unknown# unknown). Can you link the PR on GitHub for context?

Ffry69 Can't check out, it links to another Discord (`# unknown`). Can you link the PR ...

Victor Berchet•10/31/24, 7:28 AM

micooz•11/1/24, 3:17 AM

Are there any other benefits of migrating from next-on-pages to opennextjs besides being able to use Node.js runtime, like performance, responsiveness?

R in Tokyo•11/1/24, 11:03 AM

I’de just like to confirm next on pages can do SSR but not SSG correct?

RR in Tokyo I’de just like to confirm next on pages can do SSR but not SSG correct?

James•11/1/24, 5:57 PM

You can do SSR and SSG, but not ISR

Mmicooz Are there any other benefits of migrating from next-on-pages to opennextjs besid...

James•11/1/24, 5:58 PM

Long-term support will be for the OpenNext one, and it'll enable better compatibility with Next.js features. next-on-pages will eventually be phased out once the OpenNext adaptor is in a good place.

Kimitri•11/1/24, 6:10 PM

I'm about to start a Nextjs project and I want to host it on Cloudflare, but I need to know what in the NextJs app is charged by workers ? The rendered page is charged as one request or the fetch functions is charged as one request?

KKimitri I'm about to start a Nextjs project and I want to host it on Cloudflare, but I n...

fry69•11/1/24, 6:11 PM

Static assets do not get charged, functions count as workers (in fact they are workers).

Ffry69 Static assets do not get charged, functions count as workers (in fact they are w...

Kimitri•11/1/24, 6:14 PM

so basically fetch functions are charged right?

KKimitri so basically fetch functions are charged right?

fry69•11/1/24, 6:15 PM

Not every fetch call of course, but the whole function that calls fetch() must run inside a dressed up worker, that counts as one.

``` 23:16:38.104 Cloning repository... 23:16:39.261 From https://github.com/kaankutan/kutan.de

Similar Threads