From 92d7840b51b685f6ba914dc08e0056ade78f9d45 Mon Sep 17 00:00:00 2001 From: ranbel <101146722+ranbel@users.noreply.github.com> Date: Tue, 17 Sep 2024 12:14:12 -0400 Subject: [PATCH 1/2] Update clientless-browser-isolation.mdx --- .../browser-isolation/setup/clientless-browser-isolation.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx index da818e7fde53e4..4cb3e83ddb2395 100644 --- a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx +++ b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx @@ -58,7 +58,7 @@ If [TLS decryption](/cloudflare-one/policies/gateway/http-policies/tls-decryptio With Clientless Web Isolation, users can reach any private IP resource you have connected through [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/). For more information, refer to [Connect private networks](/cloudflare-one/connections/connect-networks/private-net/cloudflared/). -For example, if you added `192.0.2.1` to your tunnel, users can connect to your application through the remote browser by going to `https://.cloudflareaccess.com/browser/http://192.0.2.1`. +For example, if you added `192.168.2.1` to your tunnel, users can connect to your application through the remote browser by going to `https://.cloudflareaccess.com/browser/http://192.168.2.1`. :::note From bb1ac91d0ca5d2977c202e0afe4fd64f5847752f Mon Sep 17 00:00:00 2001 From: ranbel <101146722+ranbel@users.noreply.github.com> Date: Tue, 17 Sep 2024 12:30:33 -0400 Subject: [PATCH 2/2] Apply suggestions from code review --- .../browser-isolation/setup/clientless-browser-isolation.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx index 4cb3e83ddb2395..c646078ef0c1f4 100644 --- a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx +++ b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx @@ -56,9 +56,9 @@ If [TLS decryption](/cloudflare-one/policies/gateway/http-policies/tls-decryptio ### Connect private networks -With Clientless Web Isolation, users can reach any private IP resource you have connected through [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/). For more information, refer to [Connect private networks](/cloudflare-one/connections/connect-networks/private-net/cloudflared/). +With Clientless Web Isolation, users can reach any internal web server you have connected through [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/). For more information, refer to [Connect private networks](/cloudflare-one/connections/connect-networks/private-net/cloudflared/). -For example, if you added `192.168.2.1` to your tunnel, users can connect to your application through the remote browser by going to `https://.cloudflareaccess.com/browser/http://192.168.2.1`. +For example, if you added `192.168.2.1` to your tunnel, users can connect to your application through the remote browser by going to `https://.cloudflareaccess.com/browser/http://192.168.2.1`. Clientless Web Isolation also supports connecting over private ports, for example `https://.cloudflareaccess.com/browser/http://192.168.2.1:7148`. :::note