Skip to content

Commit 4773323

Browse files
committed
additional feedback
1 parent 2d670a8 commit 4773323

File tree

2 files changed

+16
-4
lines changed

2 files changed

+16
-4
lines changed

src/content/docs/cloudflare-one/applications/non-http/browser-rendering.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ Cloudflare can render SSH, VNC, and RDP applications in a browser without the ne
1414
- Browser rendering is only supported for [self-hosted public applications](/cloudflare-one/applications/configure-apps/self-hosted-public-app/), not private IPs or hostnames.
1515
- You can only render a browser-rendered terminal on domains and subdomains, not on specific paths.
1616
- <Render file="access/self-hosted-app/ssh-sessions" />
17+
- Cloudflare uses TLS to secure the egress RDP connection to your Windows server. We do not currently validate the chain of trust.
1718

1819
## Turn on browser rendering
1920

src/content/docs/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-browser.mdx

Lines changed: 15 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ sidebar:
1010

1111
import { Render, GlossaryTooltip } from "~/components"
1212

13-
:::note
14-
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.
1515
:::
1616

1717
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
2626

2727
- An [active domain on Cloudflare](/fundamentals/setup/manage-domains/add-site/)
2828
- 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).
3030

3131
## 1. Connect the server to Cloudflare
3232

@@ -86,7 +86,18 @@ Ensure that only **Allow** or **Block** policies are present. **Bypass** and **S
8686

8787
19. Select **Save**.
8888

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`):
94+
95+
- **Type**: _CNAME_
96+
- **Name**: `app`
97+
- **Target**: `c1744f8b-faa1-48a4-9e5c-02ac921467fa.cfargotunnel.com`
98+
- **Proxy status**: On
99+
100+
## 5. Connect as a user
90101

91102
To connect to a Windows machine over RDP:
92103

0 commit comments

Comments
 (0)