search

wasp-lang / wasp

The fastest way to develop full-stack web apps with React & Node.js.
https://wasp-lang.dev
MIT License
12.75k stars 1.14k forks source link

When port 3000 is not available, and the db is already running, intermittent issues occur when running #2014

Closed Reikon95 closed 2 months ago

Reikon95 commented 2 months ago

I found this by accident today - if you're running the db, but already running something on port 3000 locally, you'll get random "cannot get" issues when loading certain pages on 3001 (or whatever it defaults to) - not sure if it makes a difference, but only when they were behind auth

Not a breaking issue, but could be a good idea to add a warning to the start script.

Martinsos commented 2 months ago

So server listens on port 3001 and client on port 3000 -> so if you already have sometihng running on 3000, then client wont run and there will be issues!

You are right, would be good if we have a better handling for this, but we didn't get to it yet. We do have an issue that aims to solve this in a way: https://github.com/wasp-lang/wasp/issues/730 .

Thanks for reporting this, I will be closign this one in favor or the issue I linked, but if you think there is more tot his let me know and we can reopen / add that info!