You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/faq/troubleshooting.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -310,12 +310,12 @@ You can also examine logs in your identity provider to identify any denied reque
310
310
311
311
If your WSL2 environment is losing connectivity while using WARP, check your [split tunnel configuration](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/).
312
312
313
-
The issue may arise because the IP range that the WSL environment uses to communicate with the host device is included in the split tunnel configuration. Excluding (or not including) the WSL evironment's IP range should restore connectivity.
313
+
The issue may arise because the IP range that the WSL environment uses to communicate with the host device is included in the split tunnel configuration. Excluding the WSL environment’s IP range should restore connectivity.
314
314
315
315
You must ensure the host device is included in the WARP tunnel while excluding the WSL environment to prevent connectivity issues between WSL and the host device.
316
316
317
-
To debug this issue:
317
+
### To debug this issue:
318
318
319
319
1. Review the WSL2 environment's IP address and compare it with the laptop’s IP.
320
320
2. Check if the WSL network is [included in the split tunnel configuration](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#change-split-tunnels-mode).
321
-
3. If the WSL network included, exclude the WSL network from the split tunnel to prevent connectivity issues.
321
+
3. If the WSL network is included, exclude it from the split tunnel to prevent connectivity issues.
0 commit comments