From cd92594992bbe14435db7b82d1a01c93317c12f1 Mon Sep 17 00:00:00 2001 From: Kate Tungusova Date: Fri, 10 Jan 2025 16:01:25 +0100 Subject: [PATCH 1/2] [CF1] azure and containers in warp exclusion --- .../warp/troubleshooting/common-issues.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx index 3084880a73ee35..c49dcdc77fc098 100644 --- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx +++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx @@ -144,6 +144,15 @@ To diagnose the issue, go to `https://zero-trust-client.cloudflareclient.com/v0/ In the third-party security product, disable HTTPS inspection and TLS decryption for the [WARP IP addresses](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/). +### Docker container is failing DNS resolution + +If you are using WARP and running a CI/CD pipeline inside a Docker container on Microsoft hardware to provide Github Actions with an egress IP, your container's `/etc/resolv.conf` file might be injecting a [custom nameserver with the IP address `168.63.129.16`](https://learn.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16) (specific to Azure infrastructure.) +The `168.63.129.16` IP address is only accessible to Azure VMs and causes the container's traffic to fail when routed through the Cloudflare WARP tunnel. + +#### Solution + +To fix this issue, you must exclude the Azure-specific nameserver IP (`168.63.129.16`) from being routed through WARP tunnel. Refer to [Split Tunnels](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#change-split-tunnels-mode) and follow the instructions to exclude the Azure-specific IP. + ## Cannot connect to a specific app or website Below are the most common reasons why turning on WARP blocks a specific application from loading. From 851b9235218d55cf72d468e82bab25c34fdda82d Mon Sep 17 00:00:00 2001 From: Kate Tungusova <70746074+deadlypants1973@users.noreply.github.com> Date: Mon, 13 Jan 2025 15:41:00 +0100 Subject: [PATCH 2/2] Update src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> --- .../connect-devices/warp/troubleshooting/common-issues.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx index c49dcdc77fc098..0c83e943aa98a5 100644 --- a/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx +++ b/src/content/docs/cloudflare-one/connections/connect-devices/warp/troubleshooting/common-issues.mdx @@ -146,7 +146,7 @@ In the third-party security product, disable HTTPS inspection and TLS decryption ### Docker container is failing DNS resolution -If you are using WARP and running a CI/CD pipeline inside a Docker container on Microsoft hardware to provide Github Actions with an egress IP, your container's `/etc/resolv.conf` file might be injecting a [custom nameserver with the IP address `168.63.129.16`](https://learn.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16) (specific to Azure infrastructure.) +If you are using WARP and running a CI/CD pipeline inside a Docker container on Microsoft hardware to provide GitHub Actions with an egress IP, your container's `/etc/resolv.conf` file might be injecting a [custom nameserver with the IP address `168.63.129.16`](https://learn.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16) (specific to Azure infrastructure.) The `168.63.129.16` IP address is only accessible to Azure VMs and causes the container's traffic to fail when routed through the Cloudflare WARP tunnel. #### Solution