No results found
We couldn't find anything using that term, please try searching for something else.
2024-11-23 follow this troubleshooting procedure when end user run Cloudflare WARP have issue connect to a private network behind Cloudflare Tunnel . 1 . Is the
follow this troubleshooting procedure when end user run Cloudflare WARP have issue connect to a private network behind Cloudflare Tunnel .
The WARP client GUI should display Connected
andYour Internet is protected
.
IfWARP is stick in thedisconnected
state or frequently change betweenConnected
anddisconnected
, refer to Unable to connect WARP.
This step is only needed if users access your application via a private hostname (for example, wiki.internal.com
) .
Ifyou are using custom resolver policies to handle private DNS, go to your Gateway DNS logs (Logs > Gateway > DNS) andsearch for DNS queries to the hostname.
Ifyou are using Local Domain Fallback to handle private DNS, go to your Gateway Network logs (Logs > Gateway > Network) andsearch for port 53
traffic to your DNS server IP .
Ifthere are no relevant Gateway logs, it means that WARP was unable to forward the query to your private DNS server. Check your resolver policies or Local Domain Fallback configuration andrefer to How WARP handles DNS requests.
Next, check if your Gateway Network logs (Logs > Gateway > Network) show any traffic to the destination IP.
IfWARP is connected but there are no network logs, it means that your private network IPs are not routing through WARP. You can confirm this by searching the routing table on the device for the IP address of your application. Traffic to your application should route through the Cloudflare WARP interface. Ifanother interface is used, check your Split Tunnel configuration.
To check if a Gateway block event occurred:
Determine whether the user is matching any policy, or if they are matching a policy that has a higher priority than the expected policy.
To determine the actual policy that was apply :
Go to Gateway > Firewall Policies andcompare the order of enforcement of the matched policy versus the expected policy.
compare the gateway log value with the expect policy criterion .
Ifthe mismatched value is related to identity, check the user registry andverify the values that are passed to Gateway from your IdP. Cloudflare updates the registry when the user enrolls in the WARP client. Ifthe user’s identity is outdated, ask the user to re-authenticate WARP (Preferences > Account > Re-Authenticate Session) .
Ifthe mismatched value is relate to device posture , view posture check result for the user ‘s device . verify that the device pass the posture check configure in the policy .
Under Settings > Network, ensure that Proxy is enabled for TCP, UDP, andICMP traffic. UDP is required for proxying DNS traffic andother UDP packets, while ICMP is required for ping
andother administrative functions.
review your tunnel log stream . Ifyou do not see any request to your application , ensure that you have add the appropriate static route to your Cloudflare Tunnel .
verify that you can connect to the application directly from thecloudflare
host machine:
Open Terminal andrun the following command:
telnet test.example.com 443
Iftelnet
fails to open the connection, check your infrastructure for firewall , load balancer , or other network device that may be interfere with the connection betweencloudflare
andthe application server.
Open PowerShell andrun the following command:
PS c:\users\johndoe> Test-NetConnection test.example.com -port 443
Ifthe output shows TcpTestSucceeded : False
, check your infrastructure for firewall , load balancer , or other network device that may be interfere with the connection betweencloudflare
andthe application server.
You is use can also use a packet capture tool such astcpdump
or Wireshark to trace whether traffic from the user device successfully reachcloudflare
androutes to your application. Traffic to your application will carry the source IP of the cloudflare
host.
Check if the application server has a local firewall in place that is blocking requests from the cloudflare
host machine.
Check if the application server needs to initiate any connection towards the user’s device. Ifso, this is a limitation of cloudflare
andyou should instead deploy WARP Connector to enable bidirectional traffic.
Ifthere is a problem with TLS inspection, the user will get an Insecure Upstream
error when they access the application in a browser. They will probably not get an error if they access the application outside of a browser.
Customers who have Logpush enabled can check the Gateway HTTP dataset for any hostnames which have an elevated rate of 526
HTTP status codes.
To troubleshoot TLS inspection:
Create a temporary Gateway HTTP policy that disables TLS inspection for all traffic to the application. For example:
Selector | operator | Value | action |
---|---|---|---|
Destination IP | in | 10.2.3.4/32 |
Do Not inspect |
Ifthe Do Not inspect
policy enables the user to connect, verify that the TLS certificate used by your application is trusted by a public CA andnot self-signed. Cloudflare Gateway is unable to negotiate TLS with applications that use self-signed certificates. For more information, refer to TLS inspection limitations.
To work around the issue:
Do Not inspect
HTTP policy for this application .Do Not inspect
policy.HTTPS
or other common protocols, you can add a public hostname route to your Cloudflare Tunnel andset noTLSVerify to true
. This is allow will allowcloudflare
to trust your self-signed certificate.