-
Notifications
You must be signed in to change notification settings - Fork 40
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
commBind: Cannot bind socket FD 10 to [::]:3128: (1) Operation not permitted #89
Comments
Hm I have it running on latest Win 10 but not the insider build of course :( might be something related to permissions with that default LOCAL SYSTEM user that runs the binary? Anything in the system/auth event log? |
Hi again. Thanks for prompt response. I've done some further testing and discovered that this is not an issue with Squid for Windows after all (just a bit unlucky that squid's default ports are affected) For some reason I just can't listen on some port ranges (1551-3489 and 7479-8278). Still trying to figure out exact cause & solution, as no application seems to be binding to those ports and firewall is off Will advise if I find a solution as it may assist other users who run into this problem, but since it is not technically a Squid issue, you may close this ticket if you wish as I don't expect a solution to come from here Thanks:)) |
Just a quick note to say that I've managed to track down the problem cause for this behavior... See following resources for more information: Apologies once again for the false issue report for Diladele Squid for Windows - Regards |
Oh good; but please be sure to check the issue #86 too. |
Hi
Failed to bind port on first run / new installation on Windows 10 (Version 2004 OS Build 19603.1000)
Could it be the fact that I'm running a version of Windows 10 for Insiders ?
Notes:
http_port 3128
to another portI presume it relates to this cause and has something to do with cygwin?
2020/04/20 11:15:40 kid1| WARNING: no_suid: setuid(0): (22) Invalid argument
Any advice?
In the meanwhile I'll try the VM Appliance ...
Thanks
The text was updated successfully, but these errors were encountered: