Question

Nextjs build error - ENOENT: no such file or directory BUILD_ID

Posted on February 13, 2025
Next.js App Platform
Asked by Solomon

Hey guys, I need your help here. I keep getting this error on every build, I tried bumping up the memory from 2GB to 8GB, still the same. Kindly help with this as its a production environment.

[2025-02-13 18:12:46]

Error: ENOENT: no such file or directory, open '/app/.next/BUILD_ID'

[2025-02-13 18:12:46]

at async open (node:internal/fs/promises: 639:25)

[2025-02-13 18:12:46]

at async Object.readFile (node: internal/fs/promises: 1246:14)

[2025-02-13 18:12:46]

at async setupFsCheck (/app/node_modules/next/dist/server/Lib/router-utils/filesy

[2025-02-13 18:12:46]

at async initialize (/app/node_modules/next/dist/server/lib/router-server.js:56:2

[2025-02-13 18:12:46]

at async Server. <anonymous> (/app/node_modules/next/dist/server/lib/start-server.

[2025-02-13 18:12:46]

errno: -2,

[2025-02-13 18:12:46]

code: 'ENOENT',

[2025-02-13 18:12:46]

syscall: 'open',

[2025-02-13 18:12:46]

path:

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev

Site Moderator

• February 16, 2025

Hi there,

Have you set the Output Directory in App Platform to .next? If not, it might be looking in a non-existing location.

Also, do you have a custom build command? If so, what is it?

If everything looks correct and it’s still failing, try redeploying from scratch. If the issue persists, reach out to DigitalOcean support for further debugging: https://do.co/support.

- Bobby