I have been using 18.104.22.168 warp from India, and it was working fine until a few days it stopped working in 22.214.171.124 warp mode on the Jio network, but normal private DNS 126.96.36.199 is working. I tried Reset network settings, Reboot device, Always-on VPN, Clear cache and storage, Uninstall and install, Reset private keys. Did Jio block warp again?
It’s happening once again, I think there are some issues with BOM Colocation center here in India and maybe they are aware of this issue and fixing it even right now, so the best thing we can do right now is just wait for them to fix the BOM center in few days I guess.
Facing the same issue on Jio Network and BOM location. Hope this gets resolved swiftly.
Same here. Neither Jio Mobile nor JioFiber is able to connect using WARP Protocol. Jio is also not answering my query. Looks like the corporates are now careless about their services.
I’m facing the same issue with GTPL Broadband since the last few days. A similar thing happened in December too.
Here is my connection information:
188.8.131.52 — the Internet’s Fastest, Privacy-First DNS Resolver1i99ai2_gaNzc0NTI5MC4xNjM4Njk0NDQy_gid*OTY2NDQ0OTQ5LjE2NDM5OTMxNDk.#eyJpc0NmIjoiTm8iLCJpc0RvdCI6Ik5vIiwiaXNEb2giOiJObyIsInJlc29sdmVySXAtMS4xLjEuMSI6IlllcyIsInJlc29sdmVySXAtMS4wLjAuMSI6IlllcyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjExMTEiOiJObyIsInJlc29sdmVySXAtMjYwNjo0NzAwOjQ3MDA6OjEwMDEiOiJObyIsImRhdGFjZW50ZXJMb2NhdGlvbiI6IkJPTSIsImlzV2FycCI6Ik5vIiwiaXNwTmFtZSI6Ikx1bWVuIiwiaXNwQXNuIjoiMzM1NiJ9
Facing the same issue on JIO. Not able to connect to WARP but DNS is working fine?
WARP OR WARP + in connecting status
no just BOM, ACTUALLY many other
Same issue on Netplus Broadband and working fine on Airtel 4G mobile data.
I am able to ping 184.108.40.206 correctly just WARP+ doesn’t connect successfully.
If I change Settings > Advanced > Connection Options > DNS Settings > Protocol Options > DNS over HTTPS === This connects but internet doesn’t work.
Switching back to DNS over WARP again stuck on connecting.
In console logs can see both Colo LHR and BOM but this doesn’t look like Colo issue but ISP is blocking connection.
Diagnostic Console logs spam the following when state is stuck in connecting phase on WARP
2022-03-27T21:54:13.825+05:30 | class com.Cloudflare.app.vpnservice.exceptions.ConnectionException: UDP call timeout
2022-03-27T21:54:23.857+05:30 | class com.Cloudflare.app.vpnservice.exceptions.ConnectionException: UDP call timeout
What ports are used in WARP connection when Connection is established. Will check if ISP has blocked certain ports.
udp port 53 is working great in many vpn… since warp uses udp protocol … Cloudflare should immediatly look into this issue
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.