Re-Deployment issues with Fly.
Trying to re-deploy a project and running into this problem, at the client deployment
❌ --- [Error] Building of wasp project failed: -----------------------------------
1 errors found.
/home/lazi/.local/share/wasp-lang/0.16.3/data/packages/deploy/node_modules/zx/build/core.cjs:416
const output = self._output = new ProcessOutput(dto);
^
ProcessOutput [Error]:
at Proxy.set (/home/lazi/.local/share/wasp-lang/0.16.3/data/packages/deploy/node_modules/zx/build/core.cjs:277:18)
exit code: 1
at EventEmitter.end (/home/lazi/.local/share/wasp-lang/0.16.3/data/packages/deploy/node_modules/zx/build/core.cjs:416:41)
at EventEmitter.emit (node:events:536:35)
at ChildProcess.<anonymous> (/home/lazi/.local/share/wasp-lang/0.16.3/data/packages/deploy/node_modules/zx/build/vendor-core.cjs:502:16)
at Object.onceWrapper (node:events:639:26)
at ChildProcess.emit (node:events:524:28)
at maybeClose (node:internal/child_process:1101:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)
at Process.callbackTrampoline (node:internal/async_hooks:130:17) {
_code: [Getter],
_signal: [Getter],
_stdout: [Getter],
_stderr: [Getter],
_combined: [Getter],
_duration: [Getter]
}
Node.js v22.12.0
I've been deploying using wasp deploy fly deploy
7 Replies
Hi @lazi. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I can see you're having issues with redeploying your Wasp project to Fly.io. Based on the error message, there seems to be a problem during the client deployment process.
Here are a few potential solutions to try:
1. Update your Wasp version - Some deployment issues were fixed in newer Wasp versions. For example, version 0.12.4 fixed a specific client deployment issue:
Wasp Discord
2. Check your Node.js version - You're using Node.js v22.12.0, which might be too new for Wasp. Wasp has had issues with certain Node versions in the past. Try using an older, more stable version like Node.js 18 using NVM:
Wasp Discord
3. Try cleaning your project before redeploying:
Wasp Discord
4. Check environment variables - Make sure all necessary environment variables are properly set for your deployment.
5. Add organization flag - If you're using WSL on Windows or have multiple Fly.io organizations, try adding the
--org flag:
GitHub Issue
If the issue persists, you might need to check the generated code in the .wasp/build directory to see if there are any specific errors in your client code that might be causing the deployment to fail.
Note that Fly.io deployments can sometimes be flaky, and the Wasp team is aware of issues with error handling during deployment. They're working on improving how deployment errors are handled to make it clearer what went wrong and how to proceed.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @lazi, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Which Wasp version are you using? Could you try doing
wasp clean and then try deploying?lazi@Lazi:/mnt/d/Translate/T/app$ wasp version
0.16.3
I did wasp clean, even got a succesful build and it's working locally but when I do re-deploy on fly it fails with that
Could you retry with
0.16.2? Install it with curl -sSL https://get.wasp.sh/installer.sh | sh -s -- -v 0.16.2
Also, what's your OS? Did you update to a newer Node.js recently?
Also, could you paste some more output above the error messaage 😄Windows 11 with WSL2 (Ubuntu) - also on the nodejs i did have some changes.
The problem seemed to be with my client build/deployment - it succesfully passes the server deployment part (and it seems to be error handling errors mostly? )
I tried (and covered all of them) but then I was getting to the above mentioned error that i couldn't get past.
BUT ! This worked for me - I used wasp 0.16.2 and it deployed it properly with no errors (after also reverting my latest changes on fixing the above mentioned errors)
Thank you ❤️
It seems that we have some issues with the deployment command in the latest Wasp version. Could you try one more time deploying with the latest version and share the full error log with me in the DMs? 🙏 thanks
Sure thing, one second 😄