-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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]: Window outline client connected to server but can not access internet #2011
Comments
anyone can advise on this issue ?thanks |
Did you try 1.13.1? That should have fixed the issue. You may need to reinstall. |
already tried 1.13.1 today but till same problem, dont know why .... |
Can confirm this bug. Outline client 1.13.1 windows 10 - can't access to internet after connection to server. Version 1.10.1 with blocked autoupdate works just fine. |
Hi @manhte2 @mizhgan , would you please try running Outline Client in PowerShell to retrieve more logs so we can debug it? PS C:\Users\me> $env:OUTLINE_DEBUG="True"
PS C:\Users\me> & 'C:\Program File (x86)\Outline\Outline.exe' "C:\Program Files (x86)\Outline\Outline.exe" is where your Outline is located at. |
Application
Outline Client
Describe the bug
I facing this issue with some windows version even W10, W11 or W7, not all but some customer has connected to outline server but can not access internet.
Outline version tried with 1.12 and 1.13 but same problem.
outline-tap interface has been created and connected well. I checked "route print" and can see it has been added routing to VPN server 10.0.85.1
IP vpn interface is 10.0.85.2, but I cannot ping to 10.0.85.1
Firewall has been turn off, no proxy setting found.
Could you please advise ?
thanks much
Steps to reproduce
What did you expect to happen?
outline client interface cannot connect to server via virtual IP
What actually happened?
can not access internet
Outline Version
1.13 and 1.12
What operation system are you using?
Windows
Operating System Version
windows 11, 10, 7
Screenshots and Videos
No response
The text was updated successfully, but these errors were encountered: