Fly.io stopped deploying
Hi! I'm testing deployment of my Wasp app to Fly.io. It was working perfectly for a while, but stopped working. I'm not quite sure what to make of these logs, and could use some guidance. I'm not sure why it went from just magically working to not working.
I've attached the logs of my deployment attempt.
4 Replies
Wohooo @jason, you just became a Waspeteer level 3!
Hi @jason. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information provided in the knowledge sources, I can offer some guidance on troubleshooting your Fly.io deployment issue. While I don't have access to the specific logs you mentioned, I can suggest some general steps to investigate and potentially resolve the problem.
1. Check your Wasp version:
Make sure you're running the latest version of Wasp, as there have been bug fixes related to deployment. You can check your version by running
wasp version and upgrade if necessary using the command provided in the Discord support thread.
2. Inspect the server logs:
Look at the server logs on Fly.io to see if there are any specific error messages or issues being reported. This can give you more insight into what's causing the deployment to fail.
3. Verify database connection:
Ensure that your database is properly connected to your server. Sometimes, deployment issues can be caused by database connection problems. You can check this by looking at the server logs or database metrics on Fly.io.
4. Check for CORS issues:
If your client is deployed separately from your server, make sure that CORS is properly configured. This was mentioned as a potential issue in one of the Discord support threads.
5. Redeploy the application:
Try redeploying your application using the command wasp deploy fly deploy. Sometimes, a fresh deployment can resolve issues.
6. Verify environment variables:
Ensure that all necessary environment variables are properly set in your Fly.io configuration.
7. Check for certificate issues:
If you're using a custom domain, verify that your SSL certificate is valid and properly configured. In one case, reissuing the certificate resolved a deployment issue.
8. Inspect the build process:
Look for any errors during the build process in your deployment logs. This could reveal issues with dependencies or compilation.
If none of these steps resolve your issue, you may need to provide more specific information about the error messages you're seeing in your logs. The Wasp community on Discord is generally very helpful with troubleshooting deployment issues, so consider sharing more details there if the problem persists.
Remember, unexpected deployment failures can sometimes be caused by changes on the hosting provider's end. If you've ruled out issues with your application, it might be worth checking if there are any known issues or recent changes with Fly.io that could be affecting your deployment.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @jason, 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?Well, I deleted the node_modules and installed them again and after the 3rd or 4th time it deployed...
Error: failed to fetch an image or build from source: error building: input:3: ensureDepotRemoteBuilder {"code"=>"internal", "message"=>"internal error"}
This looks like a Fly error, not Wasp specific. Fly unfortunately sometimes has problems like these 🙂