Error uploading blobs to deploy store - 403

Receive error inside deploy for netlify, build local OK

Uploading blobs to deploy store
────────────────────────────────────────────────────────────────
⠙ Uploading blobs to deploy store…
Error uploading blobs to deploy store: Netlify Blobs has generated an internal error (403 status code)

Internal error during “Uploading blobs”
────────────────────────────────────────────────────────────────

Error message
Error: Failed while uploading blobs to deploy store

Error location
During Uploading blobs

@mandinho Similar previous issues have needed intervention from Netlify staff, for example:
https://answers.netlify.com/t/deployment-failure-with-error-uploading-blobs/119130

I’ve updated the title of your thread to make it more relevant.

You should also provide a site name as Netlify’s team will probably need it to investigate.

In another company yarn build works normal in .next

The problem is only here really.

@mandinho Which is expected if it’s a Netlify issue.

But you should provide a site name.

When you create a ‘Support’ thread on the forum it says:

PLEASE help us help you by writing a good post!

* We need to know your netlify site name. Example: `gifted-antelope-58b104.netlify.app`

Yes, as Nathan mentioned, we’ll need the name of the site in order to assist further.

my url: https://eletronicox.netlify.app

hey? no have solution yet?

@mandinho Netlify’s team won’t have looked yet.

They usually seem to respond in approx 1 - 3 business days.

Internal error during “Uploading blobs”
────────────────────────────────────────────────────────────────

Error message
Error: Failed while uploading blobs to deploy store

Error location
During Uploading blobs
at coreStep (file:///usr/local/lib/node_modules/netlify-cli/node_modules/@netlify/build/lib/plugins_core/blobs_upload/index.js:56:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async fireCoreStep (file:///usr/local/lib/node_modules/netlify-cli/node_modules/@netlify/build/lib/steps/core_step.js:11:98)
at async tFireStep (file:///usr/local/lib/node_modules/netlify-cli/node_modules/@netlify/build/lib/time/main.js:18:63)
at async file:///usr/local/lib/node_modules/netlify-cli/node_modules/@netlify/build/lib/steps/run_step.js:69:283
at async pReduce.index (file:///usr/local/lib/node_modules/netlify-cli/node_modules/@netlify/build/lib/steps/run_steps.js:12:349)
at async runSteps (file:///usr/local/lib/node_modules/netlify-cli/node_modules/@netlify/build/lib/steps/run_steps.js:11:205)
at async runBuildStep (file:///usr/local/lib/node_modules/netlify-cli/node_modules/@netlify/build/lib/steps/run_core_steps.js:111:64)
at async executeBuildStep (file:///usr/local/lib/node_modules/netlify-cli/node_modules/@netlify/build/lib/steps/run_core_steps.js:72:68)
at async runCoreSteps (file:///usr/local/lib/node_modules/netlify-cli/node_modules/@netlify/build/lib/steps/run_core_steps.js:19:68)

Resolved config
build:

12:28:46 PM: Collecting page data …
12:28:50 PM: Generating static pages (0/1000) …
12:29:00 PM: Generating static pages (250/1000)
12:29:03 PM: Generating static pages (500/1000)
12:29:05 PM: Generating static pages (750/1000)
12:29:12 PM: ​
12:29:12 PM: “build.command” failed
12:29:12 PM: ────────────────────────────────────────────────────────────────
12:29:12 PM: ​
12:29:12 PM: Error message
12:29:12 PM: Command failed with exit code 1: yarn run build
12:29:12 PM: ​
12:29:12 PM: Error location
12:29:12 PM: In Build command from Netlify app:
12:29:12 PM: yarn run build
12:29:12 PM: ​
12:29:12 PM: Resolved config
12:29:12 PM: build:
12:29:12 PM: command: yarn run build
12:29:12 PM: commandOrigin: ui
12:29:12 PM: publish: /opt/build/repo/.next
12:29:12 PM: publishOrigin: ui
12:29:12 PM: plugins:
12:29:12 PM: - inputs: {}
12:29:12 PM: origin: ui
12:29:12 PM: package: ‘@netlify/plugin-nextjs’
12:29:13 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
12:29:13 PM: Failing build: Failed to build site
12:29:13 PM: Finished processing build request in 2m59.098s
12:29:13 PM: Failed during stage ‘building site’: Build script returned non-zero exit code: 2

3 DAYS?? where solution??

@mandinho Just a heads up that “3 business days” was just a general guide from me based on what I usually see them do, I don’t work for Netlify.

It’s also only been 39 hours since you provided your site name, not “3 business days”.

I’d suggest just waiting, if they don’t respond in another 48 hours, bump the thread again.

Related: Can't deploy using CLI: Failed while uploading blobs to deploy store. The issue as per their description was:

every single page in the website, as generated by Next.js, is 17MB!!! That’s because Nextjs prerenders all pages and loads them all in every single page. every single page in the website, as generated by Next.js, is 17MB!!! That’s because Nextjs prerenders all pages and loads them all in every single page.

It was an issue in the logic from my application. Uploading the blobs then kept crashing, it just couldn’t handle it. But once I fixed my app, it’s working ok again.

I have a documentation section on my site, with a navigation linking to all docs. For that, I fetched all docs, and passed them as props to some component. For some reason, Nextjs was then printing the whole data for all those docs into the HTML, to keep hydration for React. As a solution, instead of passing the whole document as props, I only pass the title and url, then it went from 17 MB to less than 500 kb

Because in vercel and coolify work?

Because in vercel and coolify work??

… 3 days now? … waiting yet…

@mandinho There’s no guaranteed response times with Netlify, (unless you have an appropriate ‘Enterprise plan’), all their other plans are considered ‘self service’. So you do have to wait between each response from Netlify’s staff.

If you believe what you’re encountering is a Netlify issue, not your own code, the fastest way to get attention would be to ‘prove it’.

Make a minimum reproduction that you can demonstrate works on Vercel, but does not work on Netlify.

Was it really necessary?
├ ├ /tags/asus

08:40:03.903

├ ├ /tags/samsung

08:40:03.903

├ └ [+69 more paths]

08:40:03.903

└ ○ /tutorial 989 B 88.1 kB

08:40:03.903

  • First Load JS shared by all 87.2 kB

08:40:03.903

├ chunks/117-6ab6176086f5ddbc.js 31.6 kB

08:40:03.904

├ chunks/fd9d1056-333f9d2ffca1f454.js 53.6 kB

08:40:03.904

└ other shared chunks (total) 1.9 kB

08:40:03.904

08:40:03.904

08:40:03.904

○ (Static) prerendered as static content

08:40:03.904

● (SSG) prerendered as static HTML (uses getStaticProps)

08:40:03.904

ƒ (Dynamic) server-rendered on demand

08:40:03.904

08:40:04.223

RSS feed generated…

08:40:04.967

Traced Next.js server files in: 72.673ms

08:40:05.204

Created all serverless functions in: 236.926ms

08:40:05.708

Collected static files (public/, static/, .next/static): 472.843ms

08:40:06.630

Build Completed in /vercel/output [4m]

08:40:08.157

Deploying outputs…

08:40:37.935

08:40:38.262

Deployment completed

08:40:48.456

Uploading build cache [110.94 MB]…

08:40:50.136

Build cache uploaded: 1.681s

And now my friend? ‘prove it’