Skip to content
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

Binding failed with error 10013 - Cant bind to ANY ports #532

Closed
W1BTR opened this issue May 30, 2024 · 3 comments
Closed

Binding failed with error 10013 - Cant bind to ANY ports #532

W1BTR opened this issue May 30, 2024 · 3 comments

Comments

@W1BTR
Copy link

W1BTR commented May 30, 2024

Direwolf suddenly is failing to bind to any ports.

image

Bind failed with error: 10013
Some other application is probably already using port 8000.
Try using a different port number with AGWPORT in the configuration file.
Bind failed with error: 10013
Some other application is probably already using port 8001.
Try using a different port number with KISSPORT in the configuration file.

I was able to verify that no programs are using these ports. I also tried setting it to a variety of other ports I know are available, and they all fail with error 10013.

image

@dranch
Copy link
Collaborator

dranch commented May 30, 2024

Hmmm.. we need more details here before we can help. It looks like you're running Windows but WHICH version? Which version of Direwolf? Googling around a bit, it could be security software installed on your machine that's blocking Direwolf from opening the socket ( https://forum.beammp.com/t/core-bind-failed-with-error-10013/102578 ).

@wb2osz
Copy link
Owner

wb2osz commented May 30, 2024

Interesting. I tried the netstat command as shown and it behaves as expected.
I have Windows 10 here, 11 might be fussier.
I don't have any good ideas other than what David suggested.
Can you try running with admin privilege?

73,
John WB2OSZ

@W1BTR
Copy link
Author

W1BTR commented Jun 3, 2024

It is Windows 11, and I tried running as admin, no change. Restarting didnt fix it. However, a Windows update did fix it, so maybe Microsoft broke it temporarily with an update?

Either way, cant seem to get it to break now.

@W1BTR W1BTR closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants