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/applications/non-http/browser-rendering.mdx
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,7 @@ Cloudflare can render SSH, VNC, and RDP applications in a browser without the ne
14
14
- Browser rendering is only supported for [self-hosted public applications](/cloudflare-one/applications/configure-apps/self-hosted-public-app/), not private IPs or hostnames.
15
15
- You can only render a browser-rendered terminal on domains and subdomains, not on specific paths.
Browser-based RDP is currently in closed beta. To try out the feature, contact your account team.
13
+
:::note[Availability]
14
+
Browser-based RDP is currently available in closed beta to Enterprise customers. Availability for Free and Pay-as-you-go customers is coming soon. To request access, contact your account team.
15
15
:::
16
16
17
17
With Cloudflare Zero Trust, users can connect to an RDP server without installing an RDP client or the [WARP client](/cloudflare-one/connections/connect-devices/warp/) on their device. Browser-based RDP leverages [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/), which creates a secure, outbound-only connection from your RDP server to Cloudflare's global network. Setup involves running the `cloudflared` daemon on the RDP server (or any other host machine within the private network) and routing RDP traffic over a public hostname.
@@ -26,7 +26,7 @@ Browser-based RDP can be used in conjunction with [routing over WARP](/cloudflar
26
26
27
27
- An [active domain on Cloudflare](/fundamentals/setup/manage-domains/add-site/)
28
28
- Domain uses either a [full setup](/dns/zone-setups/full-setup/) or a [partial (`CNAME`) setup](/dns/zone-setups/partial-setup/)
29
-
- RDP server runs Windows XXX or above.
29
+
-Windows machine supports RDP connections. For a list of supported operating systems, refer to the [Windows documentation](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remotepc/remote-desktop-supported-config).
30
30
31
31
## 1. Connect the server to Cloudflare
32
32
@@ -86,7 +86,18 @@ Ensure that only **Allow** or **Block** policies are present. **Bypass** and **S
86
86
87
87
19. Select **Save**.
88
88
89
-
## 4. Connect as a user
89
+
## 4. Create a DNS record
90
+
91
+
In the [Cloudflare dashboard](https://dash.cloudflare.com/login), go to **DNS** > **Records** and verify that a [DNS record](/dns/manage-dns-records/how-to/create-dns-records/) exists for your domain. The DNS record allows Cloudflare to proxy browser-based RDP traffic to your private network. Any arbitrary DNS record will work.
92
+
93
+
If you do not already have a DNS record, [create a new DNS record](/dns/manage-dns-records/how-to/create-dns-records/#create-dns-records). For example, you could create a `CNAME` record that points your Access application public hostname (`app.example.com`) to your Cloudflare Tunnel (`<tunnel-id>.cfargotunnel.com`):
0 commit comments