I’ve been using Cloudflare Tunnels to proxy HTTP traffic without any issue, and I’ve wanted to start using WARP in place of a VPN for other non-http services, but following the guide I have been unsuccessful.
I’ve completed all the steps and can confirm the tunnel is running, but I am unable to ping the host that the Cloudflare tunnel is running on, which is for sure in address range of the CIDR specified.
What I see is this if I try to access an address in the CIDR range through a web browser: A 502 bad gateway error that I haven’t been able to find elsewhere on the forums as a common error for WARP.
I’m not sure what the bad gateway implies since all connections to 10.0.0.0/8 generate this message. And it doesn’t matter if the Tunnel that is setup in the tutorial is up or down.
Ultimately I want to be able to connect to arbitrary TCP services on my private network, but it seems that something is blocking it. I cannot tell what though. There are no other firewalls enabled between the WARP client and destination I am trying to ping.
I can tell some form of firewall filtering by Cloudflare is working because removing and adding domains/addresses from the Split Tunnels exclusion list affects the accessibility of some non-CIDR web-services that don’t like going through the WARP tunnel.
Does anyone know what I can do to resolve the 502 bad gateway error in this scenario?