Closed sambecker closed 7 months ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
exif-photo-blog | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Jan 21, 2024 5:50pm |
photos-sambecker | ✅ Ready (Inspect) | Visit Preview | Jan 21, 2024 5:50pm |
Is it a must to enable the R2.dev subdomain? I have a custom domain.
Just updated the integration @XahidEx you should now be able to use custom domains through the more general NEXT_PUBLIC_CLOUDFLARE_R2_PUBLIC_DOMAIN
environment variable.
Can you configure and let me know if it works as expected?
Just updated the integration @XahidEx you should now be able to use custom domains through the more general
NEXT_PUBLIC_CLOUDFLARE_R2_PUBLIC_DOMAIN
environment variable.Can you configure and let me know if it works as expected?
⚠ Sending SIGTERM signal to static worker due to timeout of 60 seconds. Subsequent errors may be a result of the worker exiting. ⨯ Static worker exited with code: null and signal: SIGTERM
It did build before. But It's kinda gets stuck while static page generation now. Also used r2.dev subdomain.
I believe this is a separate issue. Can you try building without static generation?
I believe this is a separate issue. Can you try building without static generation?
I was able to deploy it before. Just before the recent change. r2.dev also worked. Just didn't work with a custom domain. Now It's not working with either. Somehow the issue might be connected
For clarification is main
not building with Cloudflare R2, or is this on a customized branch?
For clarification is
main
not building with Cloudflare R2, or is this on a customized branch?
Ay! Tried the main branch!
Restarted static page generation for /p/u4Da2NDi because it took more than 60 seconds
I'm not sure how you saw this error on main
. Nothing should be statically generated on that branch. Any ideas where that's coming from (thus far, I've only seen it originating from generateStaticParams
)? Is this still the error you're seeing?
I am experimenting with static generation on the static
branch but that code is not ready for production.
Does that make sense?
Last question: does next build
work locally?
Restarted static page generation for /p/u4Da2NDi because it took more than 60 seconds
I'm not sure how you saw this error on
main
. Nothing should be statically generated on that branch. Any ideas where that's coming from (thus far, I've only seen it originating fromgenerateStaticParams
)? Is this still the error you're seeing?I am experimenting with static generation on the
static
branch but that code is not ready for production.Does that make sense?
Last question: does
next build
work locally?
Used vercel
I can't open that link—is it just building the latest commit on main
?
I can't open that link—is it just building the latest commit on
main
?
Yes + also tried the static branch. Having the same issue. Before this latest commit to main
I was able to deploy as well.
Can you find the last commit that was able to build correctly? Is it one behind main
?
Can you find the last commit that was able to build correctly? Is it one behind
main
?
I can't seem to find any significant changes since #abf3fc3.
I have two projects (one that uses Cloudflare, one that uses Vercel Blob) that are both building off main
, and only have 13 static pages (despite having different photo counts), because photos are not meant to be statically generated.
Your error message says that it's failing to build 85 pages, which makes me think different code is running.
Are there any other error messages you can share? If your code is public, can you share a link?
By the way, I am seeing similar errors on my static
branch, which uses ppr and is still experimental, in case that's helpful:
Last questions:
NEXT_PUBLIC_AWS_S3_BUCKET
or BLOB_READ_WRITE_TOKEN
), and if so, do those connect to valid stores?NEXT_PUBLIC_CLOUDFLARE_R2_PUBLIC_DOMAIN
? It should be a full host name without
"https," i.e., the value should look like, "pub-2039849...23048.r2.dv" or "my-custom-domain.com"Thank you. Now It's working ❤️ (Just crashed twice while uploading new photos. But still It did work. Also facing internal error 500
)
I'm just using R2 now. I used aws + Vercel blog before. But now It's all fresh r2.
I'm using this repo as it is, latest version
So glad you were able to get it working.
Feel free to open a new issue if uploading keeps breaking.
NEXT_PUBLIC_STORAGE_PREFERENCE
Request: #12 #18 #42