From 64e7bb12ffa1904a8955c0065b438ca809c1828c Mon Sep 17 00:00:00 2001 From: Logan Praneis Date: Fri, 29 May 2026 16:12:09 -0500 Subject: [PATCH 1/2] Update ZT SNI for new client versions --- .../devices/cloudflare-one-client/deployment/firewall.mdx | 2 +- .../partials/cloudflare-one/warp/client-orchestration-ips.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall.mdx index 9869808ed24..40310f0b4d2 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall.mdx @@ -22,7 +22,7 @@ The Cloudflare One Client connects to Cloudflare via a standard HTTPS connection -Even though `zero-trust-client.cloudflareclient.com` and `notifications.cloudflareclient.com` may resolve to different IP addresses, the Cloudflare One Client overrides the resolved IPs with the IPs listed above. To avoid connectivity issues, ensure that the above IPs are permitted through your firewall. +Starting with Cloudflare One Client version 2026.6.0, the client uses `api.devices.cloudflare.com` instead of `zero-trust-client.cloudflareclient.com`. Even though `api.devices.cloudflare.com` (or `zero-trust-client.cloudflareclient.com` in versions earlier than 2026.6.0) and `notifications.cloudflareclient.com` may resolve to different IP addresses, the Cloudflare One Client overrides the resolved IPs with the IPs listed above. To avoid connectivity issues, ensure that the above IPs are permitted through your firewall.
diff --git a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx index 885e29755b6..e5e308d9fab 100644 --- a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx +++ b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx @@ -5,4 +5,4 @@ - IPv4 API endpoints: `162.159.137.105` and `162.159.138.105` - IPv6 API endpoints: `2606:4700:7::a29f:8969` and `2606:4700:7::a29f:8a69` -- SNIs: `zero-trust-client.cloudflareclient.com` and `notifications.cloudflareclient.com` +- SNIs: `api.devices.cloudflare.com` and `notifications.cloudflareclient.com` (in Cloudflare One Client version 2026.6.0 and later) or `zero-trust-client.cloudflareclient.com` and `notifications.cloudflareclient.com` (in versions earlier than 2026.6.0) From 31cb64881ebaf9df853079ca53137721535d2057 Mon Sep 17 00:00:00 2001 From: Logan Praneis Date: Wed, 3 Jun 2026 09:48:18 -0500 Subject: [PATCH 2/2] note that notifications SNI is also not used --- .../devices/cloudflare-one-client/deployment/firewall.mdx | 2 +- .../partials/cloudflare-one/warp/client-orchestration-ips.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall.mdx b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall.mdx index 40310f0b4d2..df18f9b5cd9 100644 --- a/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall.mdx +++ b/src/content/docs/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall.mdx @@ -22,7 +22,7 @@ The Cloudflare One Client connects to Cloudflare via a standard HTTPS connection -Starting with Cloudflare One Client version 2026.6.0, the client uses `api.devices.cloudflare.com` instead of `zero-trust-client.cloudflareclient.com`. Even though `api.devices.cloudflare.com` (or `zero-trust-client.cloudflareclient.com` in versions earlier than 2026.6.0) and `notifications.cloudflareclient.com` may resolve to different IP addresses, the Cloudflare One Client overrides the resolved IPs with the IPs listed above. To avoid connectivity issues, ensure that the above IPs are permitted through your firewall. +Starting with Cloudflare One Client version 2026.6.0, the client uses `api.devices.cloudflare.com` instead of `zero-trust-client.cloudflareclient.com` and `notifications.cloudflareclient.com`. Even though `api.devices.cloudflare.com` (or `zero-trust-client.cloudflareclient.com` and `notifications.cloudflareclient.com` in versions earlier than 2026.6.0) may resolve to different IP addresses, the Cloudflare One Client overrides the resolved IPs with the IPs listed above. To avoid connectivity issues, ensure that the above IPs are permitted through your firewall.
diff --git a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx index e5e308d9fab..3cc39e00d32 100644 --- a/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx +++ b/src/content/partials/cloudflare-one/warp/client-orchestration-ips.mdx @@ -5,4 +5,4 @@ - IPv4 API endpoints: `162.159.137.105` and `162.159.138.105` - IPv6 API endpoints: `2606:4700:7::a29f:8969` and `2606:4700:7::a29f:8a69` -- SNIs: `api.devices.cloudflare.com` and `notifications.cloudflareclient.com` (in Cloudflare One Client version 2026.6.0 and later) or `zero-trust-client.cloudflareclient.com` and `notifications.cloudflareclient.com` (in versions earlier than 2026.6.0) +- SNIs: `api.devices.cloudflare.com` (in Cloudflare One Client version 2026.6.0 and later) or `zero-trust-client.cloudflareclient.com` and `notifications.cloudflareclient.com` (in versions earlier than 2026.6.0)