Clear Dev Ports
Hey all, this is probably more of a dev question than a wasp question, but I keep getting network errors when building out. I think this is because as I am 'vibe coding', the app usually crashes.
Is there a way I can see/clear the ports so I can start fresh?
3 Replies
Wohooo @Landyn, you just became a Waspeteer level 2!
Hi @Landyn. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Yes, this is a common issue during development with Wasp (and many other frameworks): if your app crashes, sometimes the processes running on ports 3000 or 3001 (the default Wasp dev ports) don't get cleaned up, which can cause network errors when you try to restart.
To see which processes are using those ports and clear them, you can use the following commands in your terminal:
This will kill any process using those ports, allowing you to start fresh. This workaround has been shared by Wasp contributors and is effective for clearing up port conflicts after crashes or abrupt stops during development. After running these commands, you should be able to run wasp start again without port issues Process is already running on port 3000.
If you want to do a more thorough cleanup (removing generated code and cached artifacts), you can also run:
This will reset your Wasp project environment, which can help resolve other lingering issues as well CLI Reference.
Let me know if you need more help!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Landyn, 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?
I keep getting network errors when building outcan you specify which errors and where you're getting them?