[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [v0](/c/v0/59) # v0 preview fails with "sh: line 1: next: command not found" error in sandbox 91 views · 24 likes · 23 posts Nisrineelhila 7447 (@nisrineelhila-7447) · 2026-03-16 · ♥ 2 ## Problem I’ve been building a website called Clinique Le RoseWood Aesthetic Medicine on `v0` by Vercel for the past 20 days, and this morning it suddenly stopped working completely. I’m almost finished with the project and urgently need help. The project was working fine, then without any changes on my end, it stopped loading. The preview panel is completely white and nothing renders. ## Error Message > **Error: The sandbox is temporarily unavailable and unable to install dependencies.** The system itself confirms this is not a code issue — my configuration is correct and `Next.js` is properly listed as a dependency. The problem is that the sandbox environment is failing to run `pnpm install` to create the `node_modules` folder. ## What I’ve Tried * Renaming the project * Bumping the version number * Creating an `.npmrc` file * Rewriting `package.json` * Refreshing the page * Closing and reopening the project * Waiting and trying again later * Restoring to an earlier version (`v112`) — preview is still white ## Current Status Even after restoring to a previous version (`v112`), the preview panel remains completely blank. The sandbox still cannot run `pnpm install`, which means the issue is on Vercel’s infrastructure side, not in my code. ## My Question Has anyone else experienced this? Is there a workaround to get the sandbox working again, or a way to export and continue working elsewhere while Vercel fixes this? Any help is greatly appreciated. If u can help please please please email me: nisrine.elhila@gmail.com MarnixB (@marnix-3108) · 2026-03-16 ## Problem My deployed project was working fine, but now I am getting the following error within the `v0` preview/sandbox: > **sh: line 1: next: command not found** ## What I've Tried 1. Updated and downgraded dependencies. 2. Refreshed the whole project. 3. Restarted the dev server and sandbox. 4. Duplicated to a new chat and a new project. All versions, new and old, return the same `sh: line 1: next: command not found` error. Please fix this asap, since the new sandbox stuff really is just working really bad. The team should really focus on deploying good stable updates, this is just not it. Chats: [https://v0.app/chat/fix-next-command-7bC5Z9SQiw1](https://v0.app/chat/fix-next-command-7bC5Z9SQiw1)  [v0.app](https://v0.app/chat/zzpregelrecht-website-design-2-G6Sp9pQ4V7O)  ### [Private Chat - v0 by Vercel](https://v0.app/chat/zzpregelrecht-website-design-2-G6Sp9pQ4V7O) Login to view  [v0.app](https://v0.app/chat/downgrade-dependencies-7bC5Z9SQiw1)  ### [Private Chat - v0 by Vercel](https://v0.app/chat/downgrade-dependencies-7bC5Z9SQiw1) Login to view And i want a refund for the credits that got wasted because of this. Community Backoffice (@community-backoffice) · 2026-03-16 Hi there, sorry that you are facing this issue. You can open a **Billing** support case from https://vercel.com/help to get your refund. If you've already opened a case, rest assured our support team will help you as soon as they get to the ticket. > Customers on all plan types are welcome to open a new case for any billing issue. Just describe the problem to the AI chat bot and click the “Create Case” button that appears at the bottom of the chat window. The AI will autofill the form based on the info provided. Then, you can review and adjust any info in the form before submitting it to reach our billing experts. Nypan (@tagile) · 2026-03-16 · ♥ 1 Same here, And i want a refund for the credits that got wasted because of this. MarnixB (@marnix-3108) · 2026-03-16 I got 1 version working again just now, by giving this picture:  But only worked on 1 version, the others still broken. Orengargir 4669 (@orengargir-4669) · 2026-03-16 · ♥ 2 I am getting a similar error. I have tried nearly all of those same steps and still see a white preview panel. The error I get on the log is the following: 6:10:52.690Z**\[SERVER\]** `sh: line 1: next: command not found` 16:10:52.704Z**\[SERVER\]** ` ELIFECYCLE Command failed.` Clerivet (@aclaytonscott-2753) · 2026-03-16 · ♥ 1 I’m also getting these errors suddenly today across several projects, including some that haven’t been modified in several days. Andrew 9507 (@andrew-9507) · 2026-03-16 · ♥ 1 I have the same issue on my end with all of my chats. I cannot publish a project, and can’t get the site to work. Tahu (@tajaehut-8587) · 2026-03-17 · ♥ 1 I am also having the same issue. I do see that the status page recently reported an outage but it’s in a completely different region for me. Is anyone able to confirm that outage is what’s causing this for some users (myself included)? Andrew 9507 (@andrew-9507) · 2026-03-17 · ♥ 1 I’m in USA and it’s showing the errr here only on the new UI layout chats. Old ui layout chats are functioning perfectly fine. Fernando Portela (@fernandoportelab) · 2026-03-17 · ♥ 2 Facing the same issue. I WANT A REFUND OF ALL MY WASTED CREDITS! Tahu (@tajaehut-8587) · 2026-03-17 · ♥ 2 I think i figured out a temporary “workaround”. Connect to Github and then restore a previous version and submit and merge the pull request. Then go back and restore the latest version and submit and merge the pull request again. For both times, you should be able to preview the version that you are restoring, so you know which branch you are pushing. But if you are trying to “push” your most recent changes and didn’t get a chance to (because of the outage), then this should help you see the most recent version once you merge whichever version you restore. hope that makes sense! MarnixB (@marnix-3108) · 2026-03-17 Hi @amyegan @mayven what is going on with this? Nypan (@tagile) · 2026-03-17 · ♥ 1 Yes, hello? they got to fix this or refund my day and my credits Nypan (@tagile) · 2026-03-17 · ♥ 1 same here, so enoying MarnixB (@marnix-3108) · 2026-03-17 · ♥ 1 Yup. same issues here; https://community.vercel.com/t/v0-preview-fails-with-sh-line-1-next-command-not-found-error-in-sandbox/36324/13 This really needs to get fixed asap, @anshumanb you know more about this? Anshuman Bhardwaj (@anshumanb) · 2026-03-17 · ♥ 1 Hi everyone, could you share a private chat URL like @marnix-3108 did? This will help us debug and narrow down the issue. Anshuman Bhardwaj (@anshumanb) · 2026-03-17 · ♥ 1 Hi @marnix-3108, could you try using the terminal to install dependencies manually: 1. Open chat terminal 2. Inside the Terminal tab, type `pnpm install` press **Enter** 3. If asked to Proceed, press **Enter**  After this try to restart the sandbox or dev server from the refresh button.  MarnixB (@marnix-3108) · 2026-03-17 · ♥ 1 [quote="Anshuman Bhardwaj, post:21, topic:36324, username:anshumanb"] pnpm install [/quote] Yeah, it looks like its working, needed a few tries tho, first i got this;  But after refreshing it worked. Why was this issue globally happening? bug in the sandbox? Anyways, thanks for fixing for now. Anshuman Bhardwaj (@anshumanb) · 2026-03-17 · ♥ 1 Hi @marnix-3108, glad it worked. Yes, there was a bug in sandbox for some users that our team patched earlier today but it required the users to restart the sandbox and dev server. Community Backoffice (@community-backoffice) · 2026-03-17 · ♥ 1 ## Solution summary To fix this v0 sandbox error, users can export their project as a ZIP file to run locally or use the "Publish" button to deploy the application directly to Vercel, where the production build environment is more stable. A temporary workaround involves connecting the project to GitHub, restoring a previous version to trigger a successful environment sync, and then restoring the latest version to force a fresh dependency installation. Fernando Portela (@fernandoportelab) · 2026-03-18 · ♥ 1 @anshumanb, here is mine: [https://v0.app/chat/tailwind-css-issues-dGhQS4EDx7r](https://v0.app/chat/tailwind-css-issues-dGhQS4EDx7r?ref=7WMM0F) Anshuman Bhardwaj (@anshumanb) · 2026-03-18 · ♥ 2 Hi @fernandoportelab, try restarting the sandbox using the refresh button as I shared above, this will fix it for you. Sorry for the inconvenience.
