Optimize OG Image Error

[xingfanxia]

Describe the bug

Build Error On Vercel with NEXT_PUBLIC_STATICALLY_OPTIMIZE_PHOTO_OG_IMAGES = 1 with R2 Storage, this error doesn't trigger with
NEXT_PUBLIC_STATICALLY_OPTIMIZE_PHOTOS = 1

Error occurred prerendering page "/p/Hc2J6Cyt/image". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Image size cannot be determined. Please provide the width and height of the image.
    at In (file:///vercel/path0/node_modules/.pnpm/next@15.1.6_@babel+core@7.24.5_@opentelemetry+api@1.9.0_react-dom@19.0.0_react@19.0.0__react@19.0.0/node_modules/next/dist/compiled/@vercel/og/index.node.js:15354:15)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at process.processTimers (node:internal/timers:516:9)
    at async Wt (file:///vercel/path0/node_modules/.pnpm/next@15.1.6_@babel+core@7.24.5_@opentelemetry+api@1.9.0_react-dom@19.0.0_react@19.0.0__react@19.0.0/node_modules/next/dist/compiled/@vercel/og/index.node.js:16119:16)
    at async Wt (file:///vercel/path0/node_modules/.pnpm/next@15.1.6_@babel+core@7.24.5_@opentelemetry+api@1.9.0_react-dom@19.0.0_react@19.0.0__react@19.0.0/node_modules/next/dist/compiled/@vercel/og/index.node.js:16127:22)
    at async Wt (file:///vercel/path0/node_modules/.pnpm/next@15.1.6_@babel+core@7.24.5_@opentelemetry+api@1.9.0_react-dom@19.0.0_react@19.0.0__react@19.0.0/node_modules/next/dist/compiled/@vercel/og/index.node.js:16127:22)
    at async Wt (file:///vercel/path0/node_modules/.pnpm/next@15.1.6_@babel+core@7.24.5_@opentelemetry+api@1.9.0_react-dom@19.0.0_react@19.0.0__react@19.0.0/node_modules/next/dist/compiled/@vercel/og/index.node.js:16103:42)
    at async Wt (file:///vercel/path0/node_modules/.pnpm/next@15.1.6_@babel+core@7.24.5_@opentelemetry+api@1.9.0_react-dom@19.0.0_react@19.0.0__react@19.0.0/node_modules/next/dist/compiled/@vercel/og/index.node.js:16127:22)
    at async Wt (file:///vercel/path0/node_modules/.pnpm/next@15.1.6_@babel+core@7.24.5_@opentelemetry+api@1.9.0_react-dom@19.0.0_react@19.0.0__react@19.0.0/node_modules/next/dist/compiled/@vercel/og/index.node.js:16103:42)
Export encountered an error on /p/[photoId]/image/route: /p/Hc2J6Cyt/image, exiting the build.
 ⨯ Static worker exited with code: 1 and signal: null
 ELIFECYCLE  Command failed with exit code 1.
Error: Command "pnpm run build" exited with 1

[sambecker]

This sounds like this issue:
vercel/satori#626

I do wonder if using Cloudflare as a CDN could complicate this process, especially if these errors only occur during prerendering

[xingfanxia]

This sounds like this issue: vercel/satori#626

I do wonder if using Cloudflare as a CDN could complicate this process, especially if these errors only occur during prerendering

Changed cloudflare to development mode, same issue.

[xingfanxia]

😂I mean the issue still persists

[sambecker]

Have you tried disabling Cloudflare proxy yet? That should be as simple as clicking the orange cloud on your DNS settings.

You may need to disable it on both subdomains:

• https://portfolio.xiax.xyz
• https://photos.xiax.xyz

[xingfanxia]

oh ok, let me try that

[xingfanxia]

}
Failed to load dynamic font for 互动 . Error: [TypeError: fetch failed] {
  [cause]: [AggregateError: ] { code: 'ETIMEDOUT' }
}
Failed to load dynamic font for 胡须 . Error: [TypeError: fetch failed] {
  [cause]: [AggregateError: ] { code: 'ETIMEDOUT' }
}
   Generating static pages (897/936) 
 ✓ Generating static pages (936/936)
   Finalizing page optimization ...
   Collecting build traces ...```

stills reports error but the build is able  to finish

[xingfanxia]

By the way, I don't see the camera model being included in the tags on the home page. Is it possible to also include that?

[sambecker]

I don't see the camera model being included

I'm seeing them it's just that they're under hundreds of tags!

[sambecker]

stills reports error but the build is able to finish

That may be as good as it gets? I'll keep an eye out on this one.

Out of curiosity, did the builds finish before?

Did you see an stability improvements by disabling Cloudflare proxy?

[xingfanxia]

oh haha... AI generated way too many tags..
Yeah disable proxy makes the build finish. It wasn't before disabling.

[sambecker]

disable proxy makes the build finish

Very good to know!

AI generated way too many tags

I'm thinking about changing the default AI generation content to be title,semantic instead of all. What do you think about that?