ISP is blocking attempts to acquire warp config("warp identity") at the first launch

[teateasan]

@markpash
ISP is blocking attempts to acquire warp config at the first launch, we need a dedicated button or procedure to initialize this attempt WITHOUT disrupting existent VPN connection and means to upload external-generated warp config file in non-rooted devices.
Also app is disrupting VPN connection even in proxy mode!

[markpash]

@markpash ISP is blocking attempts to acquire warp config at the first launch, we need a dedicated button or procedure to initialize this attempt WITHOUT disrupting existent VPN connection and means to upload external-generated warp config file in non-rooted devices. Also app is disrupting VPN connection even in proxy mode!

Hi, good idea, besides that can you tell me which ISP/Country this is and share the first few lines of the generated logs from the debug page?

[teateasan]

Hi, good idea, besides that can you tell me which ISP/Country this is and share the first few lines of the generated logs from the debug page?

Hi! thanks for reply, this is in Russia on all major mobile providers and on some land ISP's, this feature also needed in desktop version. the logs are the same as in 476 or in 492
("failed to load identity", "creating new identity" and nothing happens)
this is known tactic of russian DPI systems to prevent warp connections.

Also some providers is blocking warp handshakes but it possible to get through with network packets modificators like ByeDPIAndroid with "disordered out-of-band" method

I don't really familiar with cloudflare services but it is possible to connect to free warp by other protocols(not wg) like ssh or vless\xray? because I'm anticipating that at some point in the future russian DPI will be block the usage of wireguard entirely