Closed SSgumS closed 3 months ago
trudyhood
commented
3 months ago Hi, Thank you for trying to find issues in the VpnHood code. I understand that it may fail due to some of our check sites being blocked, but this happens only in diagnostic mode. VpnHood does not use that in a successful connection!
Anyway, perhaps we should choose better diagnostic check websites and increase the timeout.
SSgumS
commented
3 months ago Hi, Thank you for trying to find issues in the VpnHood code. I understand that it may fail due to some of our check sites being blocked, but this happens only in diagnostic mode. VpnHood does not use that in a successful connection!
Anyway, perhaps we should choose better diagnostic check websites and increase the timeout.
From when www.quad9.com blockage ran in Iran (I think it was a week ago if I'm not wrong), some of the users usually failed in the initial stages of the connection process (In a same environment but with different devices. I mean, a phone with same internet encounter net_io_eof error and another phone with the same internet connection succeed. This hints us that the problem may resides in something similar to the delay case we mentioned). In my own case, sometime I must try 2 or 3 times to successfully connect.
Are you sure that this kind of check doesn't exist in normal connection process?
trudyhood
commented
3 months ago Yes. they send you that report because after they failed to initialize the connection, VpnHood tries to start diagnostic procedure to report their network status to developers. and of course usually you can see those sites does reply properly because their network is not good. I know those sites maybe already blacked in some networks, but VpnHood doesnt count on it, thats just for diagnostic report and it does not reflect on their connection.
SSgumS
commented
3 months ago OK. Thank you. However, still I can't grasp the reason for the disruption in normal connection procedure by the explanation you kindly provided to me.
By the way, here is a video showing the normal connection procedure occurring sometimes for me. In the first time, in a glimpse, diagnosing icon appears and net_io_eof error occurs. But the second time, it connects smoothly.
https://github.com/vpnhood/VpnHood/assets/25867589/7bfb93bb-fb16-42ad-b4d3-f90cb176bef4
trudyhood
commented
3 months ago Does it happen all the time after opening the app or randomly? Can you find the situation that this happened?
SSgumS
commented
3 months ago Recently most of the times it happens. I don't know what specific situation is required to reproduce it; it is totally random in my eye.
Hello
When connecting to a VPN sever, the client waits for 2 seconds. Then, by assuming that the connection is established, it starts checking the VPN connection. I have seen in a lot of cases where the connection has not been fully established in the 2 seconds time frame and obviously in this situation the
NetworkCheckis checked using the homeland internet, not the VPN. So, it fails because one of the URLs is blocked in the homeland internet (for example in Iran, www.quad9.net is blocked). If there exists any method to detect the establishment of the VPN connection (instead of the 2 seconds delay), NetworkCheck should be checked after the detection was successful. And if there isn't any method for this, maybe the removal of this check would be better. Or maybe just removing www.quad9.net is sufficient, because blockage of www.google.com and www.microsoft.com is uncommon but www.quad9.net is more possible like what has happened is Iran.The section of the code I referred is here.
Here is the log that shows the situation I described:
Thanks in advance