Nah not really sorry, it should still be the same still from memory just using ```npm run dev```, ge
Nah not really sorry, it should still be the same still from memory just using , getting any error?
KI think the only issue i've had with it, is trying to use --turbo when running npm run dev which doesn't work with the auth js beta-19
TAhh gotcha. I think I am messing by while connecting to the d1 db. Let me try a bit more tho
HHello there
I'm having issue connecting my github account to my cloudflare pages for deployment, i keep getting
an error occurred, i should contact
I'm having issue connecting my github account to my cloudflare pages for deployment, i keep getting
an error occurred, i should contact
Hhello there
JAnyone else working with next-on-pages and having issues with the
__NEXT_ON_PAGES__KV_SUSPENSE_CACHE
Eyou can't, it's not supported
JHello everyone
Has anyone ever experienced an error where the data shows fine on local host but deployed get status 200 but the data is nowhere to be found
https://github.com/Jorgo55/newpages-for-freelancers
here is a more detailed description of the issue if you want to check it out
i am ready to reward anyone if they can help me
thanks for more info just hmu here on discord
Has anyone ever experienced an error where the data shows fine on local host but deployed get status 200 but the data is nowhere to be found
https://github.com/Jorgo55/newpages-for-freelancers
here is a more detailed description of the issue if you want to check it out
i am ready to reward anyone if they can help me
thanks for more info just hmu here on discord
GitHub
New Pages for freelancers to check out cloudflare and Next js problem on displaying data - Jorgo55/newpages-for-freelancers
JI don't know why there is a .pnp.cjs file in my ~/ directory(maybe there are some mistakes in setting up yarn). It shouldn't be there. After deleting it, everything worked fine. Thank you for your help 
JI updated my issue @ https://github.com/cloudflare/next-on-pages/issues/844 seems to be related to the worker version, will also cross post to those channel(s)
GitHub
next-on-pages environment related information System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.5.0: Wed May 1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000 CPU...
Jfwiw I disagree with using KV for fetch cache generally and have since we first implemented it since it's eventually consistent which means managing the manifest for the cache is unreliable (and fetch cache is supposed to be regional according to Vercel docs)
JBut it's described as "So for the above reasons the Workers KV storage solution is the one we recommend." in the docs?
Jyep and I disagree with that statement in the docs and don't think it should be there
AHow can I disable the cache without
Or is there no cache on production? There is in local.
cache: 'no-store'Or is there no cache on production? There is in local.
IYou can do
fetch(..., { next: { revalidate: 0 }})Is there a way for my D1 binding migrations to be executed when I deploy my next-on-pages app? I know you can do it using the CLI but I wonder if it also works automatically?
SIs there any update on Gradual Deployments for Pages?
FHey guys!
I am suddenly having an issue with my pages project, would love some help asap.
The project worked perfectly fine before and still does locally. However suddenly it just gives random 403 Forbidden on api requests and internal server errors on other pages.
Example:
I am suddenly having an issue with my pages project, would love some help asap.
The project worked perfectly fine before and still does locally. However suddenly it just gives random 403 Forbidden on api requests and internal server errors on other pages.
Example:
https://d8bad4bc.cloudnet-webinterface.pages.dev/en/sasag
FRe-deploying doesn't help.
Sometimes it fixes the internal server error and the next deployment it will do the same thing again.
And the signing in doesn't work at all. No matter what I do to the /api/user/signin url, it shows me a 403, and only on cloudflare pages. So annoying
Sometimes it fixes the internal server error and the next deployment it will do the same thing again.
And the signing in doesn't work at all. No matter what I do to the /api/user/signin url, it shows me a 403, and only on cloudflare pages. So annoying
FIt even works using wrangler pages dev.. https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/#build-and-preview-your-application-locally
Why not on cloudflare itself?
Why not on cloudflare itself?
FIf someone is able to help, please ping/reply so I get pinged.
WWhere's the API request to? Sounds like they may be blocking workers
FIt's to /api/user/signin, which has a POST in it going to a CloudNet instance (open source project), just making a normal basic btoa auth, cors is also on
*just an IP:2814
FHm.. thanks for the "tip", I just figured out that if you use a domain instead of IP, it does work. Took me days lol
FAlthough the internal server error has nothing to do with this issue AFAIK, as it's just a "not found" route
CWorkers can't fetch IPs and have restrictions on fetching specific ports
C(flowchart by community mvp albert)
MWhen using Nextjs, would you advise using Cloudflare Functions or nextjs-on-pages and Nextjs API route?
So what are the pros and cons besides Functions is Cloudflare exklusive?
So what are the pros and cons besides Functions is Cloudflare exklusive?
Jnextjs API routes if you want to use SSR. if you want your site to just be SSG, you don't need next-on-pages
MMy nextjs app is taking a long time to compile even sir small change is there any way to speed it up or it's my laptop problem
IDev mode or to compile for production?
MDev mode
ITry
next dev --turboIhi i manage to deployed a nextjs ssr on cloudflare page with the plugin @Cloudflare/next-on-pages , issue is when i deploy , first i did it manual and took from .vercel/output/static , if i try to take the whole folder containing function deploy is failing
where do i deploy my functions folder then ? thank
where do i deploy my functions folder then ? thank
Jare you referring to the cloudflare functions directory? you should be using nextjs API routes instead if you use next-on-pages
Nnext-on-pages build output are equivalentBut if i check the files in the
__worker.js manually and gzip them they don't seem to be bigger than 1MB so theoretically they won't exceed the limit.Any ideas what i could be missing?
DHi, I have a question, I am using cloudflare pages to host my nextjs (ssr) application, it has localhost everything is ok, no errors, but after deploying a new version of the application on one of the pages it shows an error "Internal Server Error". It's not an application error, it's kind of like cloudflare, nothing interesting is recorded in the logs. Any ideas?
Whow do you know it isn't an application error?
Wit sounds like one
PHello, I have a Cloudflare Pages app using NextJS (Pages router) in SSR. I'm trying to implement a custom 404 page. I have created a 404.tsx file using getStaticProps but when I go to a non-existent page on Cloudflare, the page displayed is the nextjs _error component and not my custom 404. However it was properly generated as a static html file.
Apparently using SSR with Cloudflare Pages removes the default behavior to automatically return 404.html pages deployed. Indeed when running in node runtime in local the correct 404 page is displayed but when running in edge runtime with local workers (wrangler pages dev), I have the issue.
How could I implement this logic ?
Apparently using SSR with Cloudflare Pages removes the default behavior to automatically return 404.html pages deployed. Indeed when running in node runtime in local the correct 404 page is displayed but when running in edge runtime with local workers (wrangler pages dev), I have the issue.
How could I implement this logic ?
Manyone have an example of email workers on next-on-pages?
JDo you get any errors logged when using log stream or tailing the deployment?
SHey everyone, have others had issues hitting the 25 MiB individual file limit when using a mix of SSR and static pages?
Feel like there might be something missing in our config and everything is contributing to the bundle.
We've got DatoCMS as our data store and only a couple of thousand pages.
Feel like there might be something missing in our config and everything is contributing to the bundle.
We've got DatoCMS as our data store and only a couple of thousand pages.
IHard to see what is happening here when we don't see how the pages are generated in e.g. the next.js build output, willing to share a snippet of that?
Vi have an app where the user has access to a dashboard, makes some customisations that get pushed to a db, then if a user's customer goes to
myapp.com/the-users-name they will see a page that gets rendered based on the customisations applied. to do this in vercel i would use isr with revalidatePath(), since cf doesn't support it, do i just have to put export const runtime = 'edge' on the dynamic route and just have every request count towards the workers usage quota, correct?