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/connections/connect-networks/private-net/cloudflared/connect-cidr.mdx
-26Lines changed: 0 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,32 +39,6 @@ To connect your infrastructure with Cloudflare Tunnel:
39
39
40
40
If you have applications clearly defined by IPs or hostnames, we recommend [creating an Access application](/cloudflare-one/applications/non-http/self-hosted-private-app/) and managing user access alongside your SaaS and other web apps. Alternatively, if you prefer to secure a private network using a traditional firewall model, you can build Gateway network and DNS policies for IP ranges and domains.
41
41
42
-
<Detailsheader="Example network policies">
43
-
The following example consists of two policies: the first allows specific users to reach your application, and the second blocks all other traffic.
For more information on building Gateway policies, refer to [Secure your first application](/learning-paths/replace-vpn/build-policies/create-policy/) and [Common network policies](/cloudflare-one/policies/gateway/network-policies/common-policies/#restrict-access-to-private-networks).
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/connections/connect-networks/private-net/cloudflared/connect-private-hostname.mdx
+13-28Lines changed: 13 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,7 +127,7 @@ For more details on configuring Split Tunnels, refer to [Route private network I
127
127
128
128
<Renderfile="tunnel/filter-network-traffic" />
129
129
130
-
#### Enable Gateway proxy
130
+
#### Enable the Gateway proxy
131
131
132
132
<Renderfile="tunnel/enable-gateway-proxy" />
133
133
@@ -148,25 +148,17 @@ If your private hostname points to an HTTPS application on port 443, you can sec
End users can now reach the application by going to its private hostname. For example, to test an HTTP application, open a browser and go to `wiki.internal.local`.
204
188
205
-
End users can now reach the application by going to its private hostname. For example, to test an HTTP application, you can open a browser and go to `wiki.internal.local`.
189
+
If you [enabled the Gateway proxy](#enable-the-gateway-proxy), you can view the traffic in your [Gateway activity logs](/cloudflare-one/insights/logs/gateway-logs/).
206
190
207
-
---- what's a good example for a non-HTTP app?---
191
+
### Troubleshooting
208
192
193
+
For a step-by-step troubleshooting procedure, refer to [Troubleshoot private network connectivity](/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/private-networks/).
Copy file name to clipboardExpand all lines: src/content/partials/cloudflare-one/tunnel/troubleshoot-private-networks.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ If WARP is stuck in the `Disconnected` state or frequently changes between `Conn
20
20
21
21
## 2. Is the WARP client connecting to your private DNS server?
22
22
23
-
This step is only needed if users access your application via a private hostname (for example, `wiki.internal.com`).
23
+
This step is only needed if users access your application via a private hostname (for example, `wiki.internal.local`).
24
24
25
25
- If you are using [custom resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) to handle private DNS, go to your Gateway DNS logs (**Logs** > **Gateway** > **DNS**) and search for DNS queries to the hostname.
0 commit comments