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 da818e7fde53e4c..c646078ef0c1f47 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.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`. Clientless Web Isolation also supports connecting over private ports, for example `https://.cloudflareaccess.com/browser/http://192.168.2.1:7148`. :::note