Wrangler@3 -- wrangler dev uses random port all the time

Hello everyone, before upgrading to wrangler@3 (and now using the fully local development mode) the port was normally on 8787. Now each start of the environment seems to have a random port (at the time of trying its 64278). As the Port is not always the same and a new restart creates a new port, it is a pain to update the development frontend env or my api testing client (insomnia) to always be at the correct port. Is this a bug on macOS or is there a way to force the port to be at 8787 ? Thanks in advance, David
3 Replies
Hello, I’m Allie!
IIRC, that happens if the old port isn’t available. Maybe some process is still stuck, hogging port 8787?
F0rce
F0rceOP2y ago
let me check 1 min thanks for the super fast reply tho, really appreciate it you were right:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
workerd 12374 daviddodlek 9u IPv4 0x2e16f19f0732d65 0t0 TCP *:msgsrvr (LISTEN)
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
workerd 12374 daviddodlek 9u IPv4 0x2e16f19f0732d65 0t0 TCP *:msgsrvr (LISTEN)
let me kill the process and see if the port is back to 8787 yep. 8787 is back. sometimes vscode is a pain as some terminal states are kept, eventhough I exited vscode completely. thanks for the info and fast resolving of my problem. Cheers
Hello, I’m Allie!
Happy to help!
Want results from more Discord servers?
Add your server