hiddify
WhatsApp Connectivity Issue Persists in Version 2.0.0
Search first
- [X] I searched and no similar issues were found
What Happened?
After setting the "Region: Iran" option in the Config Options of Hiddify v2.0.0 (and in all versions above v1.4.0) on Samsung devices running Android v9, v11, and v13, the WhatsApp app is unable to connect to its servers. However, when the "Region" setting is changed to "Other," WhatsApp messages and calls function correctly. This issue did not exist in Hiddify v1.4.0, even when using the Chocolate4U Geosite & Geoip configurations for sing-box. Therefore, it is clear that the problem lies within Hiddify itself and not the Chocolate4U Geoip & Geosite files.
Minimal Reproducible Example (MRE)
- Go to "Config Options"
- Click On "Region"
- Choose Iran (ir)
- then go to Whatsapp app
- try to send any message or call a person
- Now you can see that when sending any messages, a clock icon appears under the messages, indicating that the messages can't be sent.
Expected Behavior
When using Iran geosite and geoip, WhatsApp should work correctly alongside bypassing Iranian sites and IPs, as it did in version 1.4.0.
Version
v2.0.0
Platform/OS
Android
Additional Context
This issue has persisted since above version 1.4.0 and continues in the latest version 2.0.0. The problem appears to be related to the "Region: Iran" setting and affects WhatsApp connectivity on various Samsung devices running Android versions 9, 11, and 13. The issue does not occur when the region is set to "Other".
It's worth noting that in version 1.4.0, WhatsApp worked correctly even with the Iran region setting and Chocolate4U Geosite & Geoip configurations. This suggests that recent changes in the app's handling of region-specific settings or DNS configurations may be contributing to the problem.
I recommend investigating the differences in network handling, DNS resolution, and proxy configurations between versions 1.4.0 and 2.0.0, particularly focusing on how the "Region: Iran" setting affects these aspects.
Potential similarity to Nekobox issue: There might be a connection to a similar issue observed in the Nekobox app. When the "Append HTTP Proxy to VPN" option was enabled (allowing HTTP Proxy to be used directly from browsers/supported apps without going through the virtual NIC device on Android 10+), WhatsApp experienced connection problems. This suggests that the way proxy settings are applied and how they interact with specific apps could be a factor in the current Hiddify issue.
Application Config Options
{
"region": "ir",
"block-ads": true,
"execute-config-as-is": false,
"log-level": "info",
"resolve-destination": false,
"ipv6-mode": "ipv4_only",
"remote-dns-address": "udp://1.1.1.1",
"remote-dns-domain-strategy": "",
"direct-dns-address": "local",
"direct-dns-domain-strategy": "",
"mixed-port": 10808,
"tproxy-port": 2335,
"local-dns-port": 6450,
"tun-implementation": "mixed",
"mtu": 9000,
"strict-route": true,
"connection-test-url": "http://cp.cloudflare.com",
"url-test-interval": 300,
"enable-clash-api": true,
"clash-api-port": 6756,
"enable-tun": true,
"enable-tun-service": false,
"set-system-proxy": false,
"bypass-lan": true,
"allow-connection-from-lan": true,
"enable-fake-dns": false,
"enable-dns-routing": true,
"independent-dns-cache": true,
"rules": [],
"mux": {
"enable": false,
"padding": false,
"max-streams": 8,
"protocol": "smux"
},
"tls-tricks": {
"enable-fragment": true,
"fragment-size": "110-120",
"fragment-sleep": "5-10",
"mixed-sni-case": true,
"enable-padding": false,
"padding-size": "5-10"
},
"warp": {
"enable": false,
"mode": "warp_over_proxy",
"clean-ip": "auto",
"clean-port": 0,
"noise": "1-3",
"noise-delay": "10-30"
},
"warp2": {
"enable": false,
"mode": "warp_over_proxy",
"clean-ip": "auto",
"clean-port": 0,
"noise": "1-3",
"noise-delay": "10-30"
}
}
Relevant log output
Line 150: +0330 2024-07-16 03:22:49 ERROR dns: exchange failed for g.whatsapp.net. IN AAAA: connection timed out
Line 151: +0330 2024-07-16 03:22:49 ERROR dns: exchange failed for g.whatsapp.net. IN A: connection timed out
Line 175: +0330 2024-07-16 03:22:59 ERROR dns: exchange failed for g.whatsapp.net. IN A: connection timed out
Line 178: +0330 2024-07-16 03:23:09 ERROR dns: exchange failed for g.whatsapp.net. IN A: connection timed out
Line 241: +0330 2024-07-16 03:23:19 ERROR dns: exchange failed for g.whatsapp.net. IN AAAA: connection timed out
Line 329: +0330 2024-07-16 03:23:32 ERROR dns: exchange failed for g.whatsapp.net. IN A: connection timed out
Line 368: +0330 2024-07-16 03:23:43 ERROR dns: exchange failed for g-fallback.whatsapp.net. IN A: connection timed out
Line 410: +0330 2024-07-16 03:23:53 ERROR dns: exchange failed for g-fallback.whatsapp.net. IN AAAA: connection timed out
Line 411: +0330 2024-07-16 03:23:53 ERROR dns: exchange failed for g-fallback.whatsapp.net. IN A: connection timed out | upstream: context canceled
Line 414: +0330 2024-07-16 03:24:03 ERROR dns: exchange failed for g-fallback.whatsapp.net. IN AAAA: connection timed out
Line 441: +0330 2024-07-16 03:24:13 ERROR dns: exchange failed for g-fallback.whatsapp.net. IN A: connection timed out
Line 477: +0330 2024-07-16 03:24:23 ERROR dns: exchange failed for g-fallback.whatsapp.net. IN AAAA: connection timed out
Are you willing to submit a PR? If you know how to fix the bug.
- [ ] I'm willing to submit a PR (Thank you!)
> @Chocolate4U are all WhatsApp domains & IPs excluded from Iran direct rules?
There is no Non-IR IP or Domain in my geoip:ir and geosite:ir. You can verify this yourself by looking at raw files here.
Originally posted by @Chocolate4U in https://github.com/hiddify/hiddify-next/issues/1065#issuecomment-2258800852
duplicate issue #1065
duplicate issue #1065
@titancomputer Unbelievable! You keep dodging the real issue here and had the gall to close the new issue as a duplicate. The WhatsApp connectivity problem has been a nightmare since versions above 1.4.0. Everything was working perfectly in version 1.4.0, even with the Chocolate4U files. Now, WhatsApp can't connect, calls fail, and messages are barely sent or received. Releasing version 2.0.0 should have been a major improvement, but it's just another pointless update that doesn't address the critical WhatsApp issue. You're wasting time on irrelevant updates while ignoring the core problems that users have been facing for so long. It's no wonder Iranian apps never gain international recognition with such abysmal support and maintenance. Developers like you refuse to take responsibility for your own failures. This glaring issue with WhatsApp, the world's most popular messaging app, didn't exist in version 1.4.0, but you won't fix it or even acknowledge it! I'm utterly disappointed in your inability to manage bugs properly. It's clear you closed the topic to avoid dealing with the issue. Your 2.0.0 release is just a pathetic attempt to mask your incompetence. Fix the WhatsApp problem and stop closing issues as duplicates without actually solving them!
the other issue that you made has more explanation and added to main project to recheck by developers.