[Bug]: Can't Deploy NextJS App via PNPM
Error Message and Logs
When trying to deploy a newly initialized NextJS app via Nixpack and PNPM, it's unable to resolve the install command due to an EHOSTUNREACH error.
Steps to Reproduce
- Create new NextJS app via
pnpm dlx create-next-app@latest - Push app to public Github repository
- Create a public github repository resource on Coolify
- Select the Nixpack deploy option
- Use the following commands:
- Install Command:
pnpm install - Build Command:
pnpm run build - Start Command:
pnpm run start
- Install Command:
- Deploy application
Example Repository URL
https://github.com/0-BSCode/NextJS-ISR-Test
Coolify Version
v4.0.0-beta.418
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 24.04
Additional Information
I saw one other issue that encountered the same problem, but it's now closed. OP said it was a temporary issue and it went away after a while, but another user commented a month later that they also ran into the same issue. The original issue was closed without providing a workaround.
Also ran into this problem !
this will be either a network issue related to your host location or an issue with the cdn you see from your host location, either way this isn't a bug with coolify, you need to wait till it's resolved
this will be either a network issue related to your host location or an issue with the cdn you see from your host location, either way this isn't a bug with coolify, you need to wait till it's resolved
Thanks for the speedy response! I was thinking the same, but I tried redeploying another one of my nextjs projects with a similar setup (PNPM + Nixpack) by selecting the "Force deploy (without cache)" button and the packages are installed without an issue.
My understanding is that the "Force deploy (without cache)" button will cause the packages to be re-installed as the deploy will ignore cache. Am I understanding this right and, if so, would it mean that this is not a networking or cdn issue?
@0-BSCode can you try changing the node version in your dockerfile to 20/22 or 24
Closing old issue. Reopen if still reproducible.