Closed the1812 closed 4 months ago
I haven't been able to get my Windows box running.. can you confirm that these specific ports are blocked on Windows in general or is it something specific to your machine? If it's the former, some Windows documentation about this would be useful also.
I can see a case for port finding in general here, but if it's specific to our machine, we will think about priority differently than if it's a problem for all Windows users by default.
I checked blocked ports using:
netsh interface ipv4 show excludedportrange protocol=tcp
Start Port End Port
---------- --------
1118 1217
1318 1417
1418 1517
5357 5357
7390 7489
14229 14328
14412 14511
14536 14635
14839 14938
50000 50059
Wikipedia have no record for 9789
port.
But I found running turbo login
in an elevated shell solved the problem. And after that a normal shell can listen on 9789
.
@the1812 thanks for looking into that. So do you think this is a problem for turbo to solve? It sounds specific to your setup. I am sure we could add some port finding mechanism, but I'm leaning towards documenting instead.
It sounds specific to your setup.
Yes, leaving some documentation should be fine.
Verify canary release
Link to code that reproduces this issue
https://github.com/vercel/turbo/tree/main/examples
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Windows
Which canary version will you have in your reproduction?
1.11.4-canary.2
Describe the Bug
I'm trying to setup Remote Caching following the docs:
When I run
turbo login
, my browser opened vercel authorize page but turbo CLI crashed instantly.Expected Behavior
turbo CLI should not crash but pick another port. See additional context below.
To Reproduce
Install turbo and run login command.
Additional context
Looks like listening on the
9789
port (and nearby ports) is not allowed in Windows. I confirmed no other process is using this port. Using serve can get similar result.Full crash report:
TURBO-2188