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
bash can't start port on 1703 #1845
Comments
Bash can not connect to Internet |
@andmeics no, i can use apt install the program ,can ping also,just can't open port |
Is it possible that you have a firewall that's blocking these ports? What IP address are you listening on? And what IP address are you connecting to? (Note that |
@aseering start nginx and redis use the default conf ,and in 1607,it works well,when i update to 1703,it has the problem |
@zuohl -- could you please answer my questions? |
@aseering where can i find log for bash ,may be i can find the reason for this |
@aseering sorry , now you can see ,i close the firewall,and i use the ipv4 ,it can't connet |
i tried change the port for nginx and disabled the ipv6,it also does't work |
@zuohl -- thanks for posting the additional information. Hm... So, nginx works just fine for me in 1703. I ran the following commands:
No errors were printed, just progress messages. (I can paste those messages here if they would be useful; let me know.) Then, I tried the following, at a separate bash prompt on the same machine:
I was also able to navigate to So, it works for me. Are you doing anything different than the steps above? (I haven't tried redis. If you manage to get nginx working and you still can't get redis working, let me know and I can give it a try.) |
Regarding logging: As far as I know (?), WSL doesn't log much by default. If you want a detailed log of an application's activity, you can use Linux
You might also want to look in |
execve("/usr/sbin/nginx", ["nginx", "-g", "daemon off;"], [/* 15 vars /]) = 0 |
Hm... Well, here's the bit of the strace where nginx connects to the socket:
So, nginx is binding to |
@aseering socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 6 |
Hm... Could you also post an strace of the telnet command that you use to try to connect? We'll see what that strace says, but this really does feel to me like you have installed a firewall that's blocking these packets. Is it possible that you have a third-party antivirus program installed? (Those usually include firewalls that scan for and block some unknown and/or untrusted types of traffic.) Or any other third-party Windows app that has anything to do with either networking or security? |
@aseering execve("/usr/bin/telnet", ["telnet", "127.0.0.1", "80"], [/* 16 vars /]) = 0 |
Ok, based on that trace, I think it's very likely that you do in fact have some sort of third-party program (if not firewall or antivirus, maybe a network driver?) that is interfering with bash's network connectivity. I can't tell you which program from this trace, though. Note that the problem with firewalls and similar programs is not that they might block connections on port 80. (That's also the case, but it's easy to fix.) The real problem with that sort of program is that most of them are implemented by injecting themselves into the Windows network stack, so that they can intercept packets. If they don't implement support for Linux sockets, then those sockets will simply error out, which is what you're seeing here. Some other programs also inject themselves into the Windows network stack. I don't know if there's a way in Windows to enumerate all loaded drivers that touch the network stack? It's not a process so you won't see it in the process list (though you may see the process that loaded it). If not a literal device driver, maybe you have some kind of nonstandard VPN client that works this way?, or maybe your machine has acquired some adware that's trying to sniff your network traffic by intercepting it with a bash-incompatible driver? Are you running stock vanilla Windows, or Windows as provided by your PC vendor or by your company? Maybe a third-party program that came bundled with your PC is doing something relevant? Anyway, I'm afraid I'm at a loss... I'm pretty confident that this is what's happening, but I don't know how to be more specific. |
@aseering - Thanks for all your support to this community. Invaluable! @zuohl - Apologize for the delay. Can you do this simple test (took from @aseering post) and dump the output of the netstat command?
|
Same question. All things work well in 1607. After upgrade to 1703 and Ubuntu 16.04, open port not working. run test provided by @sunilmut , there is no output after running |
same for me, i am 1703, ubuntu 16.04 |
Same issue here on public build 15063.138 |
same for me.can not connect by any port. |
@zuohl Do you mean 'Fiddler'? I didn't use it at all. After re-installing Win1703 using ISO file, all things work well. |
I am using 1703 @ 15063.250, creators update. Same problem, I could see sshd.exe is running but port is not listening. I tried disable firewall or change another port, but not work. Is this a bug? |
In my case the problem was the tcpipbm.sys file (Bytemobile Optimization Client file) installed by the GPRS modem software. After uninstalling, the ports open correctly. |
On 1703 on my desktop, my ports aren't listening. I've tried reinstalling the Creators Update and Bash multiple times with no success. However, today, I finally updated to 1703 on my laptop and my ports do get opened and I can access my local servers. Not sure how to approach debugging this. |
I have the same problem, nginx start successfully, but port 80 not listening, I can't access localhost via bash or browser in windows |
@namiltd - I am looking to install the |
Blueconnect compressor containing Bytemobile Optimization Client (Copyright ©2001-2006 Bytemobile, Inc.): blueconnectcompressor.zip |
Please try this on a more recent Insiders Build and reopen if you still hit this issue |
when i start redis or nginx in bash,it seems success,but when i test it for telnet ,it do not open,and then i go to cmd , use netstat,i can't find the port.i tried to reinstall the bash and the windows,it don't work either
15063.11
The text was updated successfully, but these errors were encountered: