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

[Bug] Broken internet connection when using on windows hiddify in VPN mode #159

Open
sat0sh1c opened this issue Nov 25, 2024 · 3 comments
Open
Labels
type: bug Something isn't working

Comments

@sat0sh1c
Copy link

Describe the bug

When hiddify is launched in a VPN mode the entire connection is extremely unstable and tend to stop working after some period of time. I am sure that this issue is related to this app, as If I close it the connection is working completely fine

Reproduction

Download hiddify in settings select VPN mode to any server.
P.S: The connection was made via vless protocol

Stack trace or error logs (if applicable)

No response

Version number

2.5.1

@sat0sh1c sat0sh1c added the type: bug Something isn't working label Nov 25, 2024
@github-project-automation github-project-automation bot moved this to 📬 Needs triage in zebar Nov 25, 2024
@lars-berger
Copy link
Member

Which providers do you use in your config? If you're running one of the default configs, could you see if the issue's still reproducible with the network provider commented out?

@sat0sh1c
Copy link
Author

sat0sh1c commented Nov 28, 2024

Which providers do you use in your config? If you're running one of the default configs, could you see if the issue's still reproducible with the network provider commented out?

Yeah, that seems to solve it, I guess the network is the reason. Moreover when the network was enable the Wi-Fi icon was crossed. like there was no connection.

@fevzibabaoglu
Copy link

Moreover when the network was enable the Wi-Fi icon was crossed. like there was no connection.

I am also experiencing this when using Cloudflare WARP. There seems to be an issue with NetworkInterface.interface_type. It returns as undefined when the default interface is a tunnel type, instead of correctly identifying it as tunnel. While WARP is active, there are (at least) two interfaces active: WIFI and the WARP tunnel. Ideally, WIFI or Ethernet should be prioritized as the defaultInterface. However, the WARP tunnel is selected as the defaultInterface, and its interface_type is not properly defined.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
Status: 📬 Needs triage
Development

No branches or pull requests

3 participants