gino
gino•3mo ago

Convex dev fails inside Docker dev-machine with 500 on /finish_push

Hi! 👋 I'm running into an issue with Convex inside my dev-machine (Docker container). When I run bunx convex dev, I consistently get this error:
✖ Error: Unable to finish push to http://127.0.0.1:3210
✖ Error fetching POST http://127.0.0.1:3210/api/deploy2/finish_push 500 Internal Server Error: InternalServerError: Your request couldn't be completed. Try again later.
Failed due to network error, retrying in 12.33ms...
✖ Error: Unable to finish push to http://127.0.0.1:3210
✖ Error fetching POST http://127.0.0.1:3210/api/deploy2/finish_push 500 Internal Server Error: InternalServerError: Your request couldn't be completed. Try again later.
Failed due to network error, retrying in 12.33ms...
Setup: - Dev environment is running entirely inside Docker. - Next.js 15.3.4 + Bun. - Convex ^1.25.0. - Node v18.20.8 (required for email usage)
3 Replies
Convex Bot
Convex Bot•3mo ago
Thanks for posting in <#1088161997662724167>. Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets. - Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.) - Use search.convex.dev to search Docs, Stack, and Discord all at once. - Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI. - Avoid tagging staff unless specifically instructed. Thank you!
Eliot
Eliot•3mo ago
Also running into this outside of Docker. Fixed by disabling local development.
gino
ginoOP•3mo ago
Hey Eliot, thanks for sharing! In my case disabling local development didn’t solve it I ended up nuking my dev-container and spinning it up again 😅 Though I think deleting the .convex folder(the one associated with the local deploy) might have done the trick too I suspect it could also be because I had 3 different Convex projects inside my dev-container (all running in local development without an account), so maybe that caused the issue

Did you find this page helpful?