ChrisMcMStone
Bind fail error
Hi, I am getting the following log when I am running the tool
Listening on TCP port 443
Address already in use (Bind failed)
How can i fix this issue? Thanks
Hi Zad,
That indicates that you have another service running on port 443. You'll need to kill that process as Spinner needs that port to run it's TLS proxy.
Chris
On 9 Apr 2018 19:35, Zad Basheer [email protected] wrote:
Hi, I am getting the following log when I am running the tool
Listening on TCP port 443
Address already in use (Bind failed)
How can i fix this issue? Thanks
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/ChrisMcMStone/Spinner/issues/6, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGGH7cbxe8ATstqwQC04gx6-JOflAtojks5tm6nvgaJpZM4TNBFz.
Hi Chris,
I was trying to set this up and received a similar issue to Zad. It appears that the "Address already in use" error will occur when either port 443 or 53 is in use. I got the same error output as Zad and it turned out it was because port 53 was in use by the OS (even though it is not entirely clear to me from that message).
The major hurdle I'm trying to get around is that on both Windows 10 and Linux (in my case Ubuntu) the OS by default has a process bound to port 53. For windows it appeared to be svchost.exe and on Ubuntu it was systemd-resolver. When I killed those processes and started the spinner service, my devices connected to a local AP were unable to resolve any urls.
Is this expected behavior? Do you have any suggestions on how to put together a test setup to get this working?
