-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Cannot use Launch Coverage & Test Explorer
- Error: Failed to start wallaby app service: Can not find a free port
#2520
Comments
From our understanding, this problem has been introduced relatively recently on Windows machines because Docker and/or HyperV and/or WSL2 are now reserving the same ephemeral port ranges that are used by Wallaby. You may read about a few non-Wallaby issues related to ports reservations causing problems with other applications:
You can see which ports have been reserved using the command prompt:
There are two key services hosted by Wallaby to support Wallaby App:
In many cases, rebooting your machine will remove the ephemeral port reservation(s) that are causing your problem, but its possible that they will be reserved again at some time and then you'll have the same problem (needing to reboot to fix the problem). Right now we rely on well-known port numbers (for the web server, for saving Wallaby app as a browser favorite), and for Wallaby App Service for discovery from the web application. We're investigating how to fix this and will reply to this issue when we have a better solution (vs. rebooting) for you. |
Is there any configuration to change ports?
…On Thu, 24 Sep 2020, 00:47 Simon McEnlly, ***@***.***> wrote:
From our understanding, this problem has been introduced relatively
recently on Windows machines because Docker and/or HyperV and/or WSL2 are
now reserving the same ephemeral port ranges that are used by Wallaby.
You may read about a few non-Wallaby issues related to ports reservations
causing problems with other applications:
- WSL #5306 - Huge amount of ports are being reserved
<microsoft/WSL#5306>
- Docker for Windows #3171 - Unable to bind ports: Docker-for-Windows
& Hyper-V excluding but not using important port ranges
<docker/for-win#3171 (comment)>
You can see which ports have been reserved using the command prompt:
netsh interface ipv4 show excludedportrange protocol=tcp
There are two key services hosted by Wallaby to support Wallaby App:
1.
Web Server port (port 51245) - this is used to host Wallaby App so you
can access with http://localhost:51245. If this port is unavailable or
in use, you may use http://wallabyjs.com/app (note that the web app
connects to your localhost only and none of your project data is
communicated outside of localhost).
2.
Wallaby App Service - this is used to communicate with the web
application. Wallaby has a set of ports that it attempts to use and if none
are available, you will receive the error that you are seeing. The ports
Wallaby attempts to use are:
51235, 51236, 51237, 51238, 51239, 51240, 51241, 51242, 51243, 51244,
52742, 52743, 52744, 52745, 52746, 52747, 52748, 52749, 52750, 52751,
53578, 53579, 53580, 53581, 53582, 53583, 53584, 53585, 53586, 53587.
As you may be able to see, these ports are not contiguous so it
*should* be possible for Wallaby to get at least one of these ports.
*In many cases, rebooting your machine will remove the ephemeral port
reservation(s) that are causing your problem, but its possible that they
will be reserved again at some time and then you'll have the same problem
(needing to reboot to fix the problem).*
------------------------------
Right now we rely on well-known port numbers (for the web server, for
saving Wallaby app as a browser favorite), and for Wallaby App Service for
discovery from the web application. We're investigating how to fix this and
will reply to this issue when we have a better solution (vs. rebooting) for
you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2520 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGYQIY6GWA4FSN35TSOPS3SHKCJRANCNFSM4RXAU2TQ>
.
|
Not currently, but we're working on a fix. Our preference is to not have you specify a port manually. We should have the fix available to you by this time tomorrow (if not sooner). |
A fix for your problem is available in the latest version of Wallaby for VS Code (v1.0.243), and Wallaby core (v1.0.964). Wallaby should automatically update for you but if it does not, please update the Wallaby extension in Visual Studio Code and then run the VS Code command, Please note that to support the scenario when all Wallaby App should also update itself automatically when it is next used but if Wallaby App doesn't load properly after getting the latest version of the extension and Wallaby core, please clear the browser cache for the Wallaby App url. |
Issue description or question
Cannot use the Cannot use
Launch Coverage & Test Explorer
- Error:Failed to start wallaby app service: Can not find a free port
Wallaby diagnostics report
The text was updated successfully, but these errors were encountered: