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

VPN mode (TUN) Issue on Windows v0.3.8 #69

Open
alexsammers1 opened this issue Mar 2, 2024 · 8 comments
Open

VPN mode (TUN) Issue on Windows v0.3.8 #69

alexsammers1 opened this issue Mar 2, 2024 · 8 comments
Labels
bug Something isn't working TUN Issues related to TUN mode

Comments

@alexsammers1
Copy link

Hey Everybody!

Here's the situation: I'm able to connect via Proxy - no issues, great speed and performance. When I test TUN Mode, it connects successfully, but then has no internet access:
Internet Access

Based on the log, it seems to have an issue with the host domain on my server:

2024/03/02 18:40:34 [Warning] core: Xray 1.8.8 started
2024/03/02 18:40:38 127.0.0.1:61348 accepted //cloudflare-dns.com:443 [http >> proxy]
2024/03/02 18:40:40 127.0.0.1:62747 accepted //rts-us-fcht.freshworksapi.com:443 [http >> proxy]
2024/03/02 18:40:41 127.0.0.1:62748 accepted //play.google.com:443 [http >> proxy]
2024/03/02 18:40:41 127.0.0.1:62749 accepted //mtalk.google.com:5228 [http >> proxy]
2024/03/02 18:40:41 127.0.0.1:62750 accepted //mtalk.google.com:5228 [http >> proxy]
2024/03/02 18:40:42 127.0.0.1:62751 accepted http://cp.cloudflare.com/ [http >> proxy]
2024/03/02 18:40:42 [Warning] [28403595] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp: lookup super.alexsammers.quest: no such host] > common/retry: all retry attempts failed
2024/03/02 18:40:42 127.0.0.1:62752 accepted //rts-us-fcht.freshworksapi.com:443 [http >> proxy]
2024/03/02 18:40:43 [Warning] [2717618132] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp: lookup super.alexsammers.quest: no such host] > common/retry: all retry attempts failed
2024/03/02 18:40:43 127.0.0.1:62753 accepted //play.google.com:443 [http >> proxy]
2024/03/02 18:40:43 127.0.0.1:62754 accepted //play.google.com:443 [http >> proxy]
2024/03/02 18:40:43 127.0.0.1:62755 accepted //google.com:443 [http >> proxy]
2024/03/02 18:40:43 127.0.0.1:62756 accepted //rts-us-fcht.freshworksapi.com:443 [http >> proxy]
2024/03/02 18:40:43 udp:127.0.0.1:58782 accepted udp:8.8.8.8:53 [socks >> proxy]
2024/03/02 18:40:43 udp:127.0.0.1:58795 accepted udp:10.0.68.255:137 [socks >> proxy]
2024/03/02 18:40:43 [Warning] [165079264] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp: lookup super.alexsammers.quest: no such host] > common/retry: all retry attempts failed
2024/03/02 18:40:43 [Warning] [2759660428] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp: lookup super.alexsammers.quest: no such host] > common/retry: all retry attempts failed

Could you please let me know if I'm missing smth here? Happy to provide additional info or re-test, but def need some direction.

@LorenEteval
Copy link
Owner

If connection is successful in proxy mode then it should also work in TUN mode.

Application log is needed (i.e. Furious Log) to help identify the problem.

@LorenEteval LorenEteval added the question Further information is requested label Mar 8, 2024
@LorenEteval
Copy link
Owner

Try release 0.3.9

@alexsammers1
Copy link
Author

Update - Proxy Mode works perfectly on 0.3.9 - no issues. TUN Mode - same result as before, connects but no internet access.

[2024-03-09 20:22:35,350] [Furious.QtFramework.QtGui] [INFO] action is 'Show Furious Log'. Checked is False
[2024-03-09 20:22:36,590] [Furious.QtFramework.NetworkStateManager] [ERROR] connection test failed. Operation canceled
[2024-03-09 20:22:58,588] [Furious.QtFramework.NetworkStateManager] [ERROR] connection test failed. Operation canceled
[2024-03-09 20:23:40,595] [Furious.QtFramework.NetworkStateManager] [ERROR] connection test failed. Operation canceled
[2024-03-09 20:23:44,581] [Furious.QtFramework.QtGui] [INFO] action is 'Copy'. Checked is False

@LorenEteval
Copy link
Owner

TUN setup is fine based on your application log. However, connection test via http://cp.cloudflare.com never succeeds.

I can only assume that your server has some firewall rules blocking udp traffic in and/or out, which causes DNS resolution to fail in your case (also shown in your core log).

You can perform further test to verify it (e.g. using curl). In TUN mode:

  • All IP-based connections are fine.
  • Any connection based on the domain name will fail.

@alexsammers1
Copy link
Author

Update - I've checked everything I could think of, no go. For some reason, the TUN Mode always fails to get internet access. I've checked on my PC/VPS, no udp traffic restrictions or block lists.

I've even tested with another XRay Client and the TUN mode works there just fine. It is behind on the xray-core version though, 1.8.3

@LorenEteval LorenEteval added bug Something isn't working TUN Issues related to TUN mode and removed question Further information is requested labels Mar 14, 2024
@LorenEteval
Copy link
Owner

2024/03/02 18:40:43 [Warning] [165079264] app/proxyman/outbound: failed to process outbound traffic > proxy/vless/outbound: failed to find an available destination > common/retry: [dial tcp: lookup super.alexsammers.quest: no such host] > common/retry: all retry attempts failed

Reproduced this error after switching server address to a domain name. I doubt there's something misconfigured in the default Xray configuration. When I switch server address to domain name under hy2 everything works fine.

Xray-core failed to resolve server address successfully before transmiting everything in TUN mode.

Repository owner deleted a comment from alexsammers1 Mar 14, 2024
@alexsammers1
Copy link
Author

Yep, confirmed - once I changed the domain to Server IP, Tun Mode connected successfully, full internet access.

Thank you for looking into this - really appreciate it!

@hamid3pelh
Copy link

I had the same problem, and it was solved by changing the domain to the server IP. Is there anything you can do to make it work with the domain? thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working TUN Issues related to TUN mode
Projects
None yet
Development

No branches or pull requests

3 participants