Skip to content

Commit 132a320

Browse files
fixed formatting
1 parent 44d5bdb commit 132a320

File tree

2 files changed

+19
-15
lines changed

2 files changed

+19
-15
lines changed

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

Lines changed: 19 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,6 @@ pcx_content_type: how-to
33
title: Browser-rendered terminal
44
sidebar:
55
order: 3
6-
76
---
87

98
Cloudflare can render certain non-web applications in your browser without the need for client software or end-user configuration changes. Cloudflare currently supports rendering a terminal for SSH and VNC connections in a user's browser.
@@ -16,11 +15,24 @@ You can only enable browser rendering on domains and subdomains, not for specifi
1615

1716
To enable browser rendering:
1817

19-
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
20-
2. Locate the SSH or VNC application you created when [connecting the server to Cloudflare](/cloudflare-one/connections/connect-networks/use-cases/ssh/). Select **Configure**.
21-
3. In the **Policies** tab, ensure that only **Allow** or **Block** policies are present. **Bypass** and **Service Auth** are not supported for browser-rendered applications.
22-
4. Go to **Advanced settings** > **Browser rendering settings**.
23-
5. For **Browser rendering**, choose _SSH_ or _VNC_.
24-
6. Select **Save application**.
18+
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
19+
2. Locate the SSH or VNC application you created when [connecting the server to Cloudflare](/cloudflare-one/connections/connect-networks/use-cases/ssh/). Select **Configure**.
20+
3. In the **Policies** tab, ensure that only **Allow** or **Block** policies are present. **Bypass** and **Service Auth** are not supported for browser-rendered applications.
21+
4. Go to **Advanced settings** > **Browser rendering settings**.
22+
5. For **Browser rendering**, choose _SSH_ or _VNC_.
23+
24+
:::note
25+
26+
When connecting over SSH, Cloudflare supports following key exchange algorithms:
27+
28+
29+
- `curve25519-sha256`
30+
- `ecdh-sha2-nistp256`
31+
- `ecdh-sha2-nistp384`
32+
- `ecdh-sha2-nistp521`
33+
34+
:::
35+
36+
6. Select **Save application**.
2537

2638
When users authenticate and visit the URL of the application, Cloudflare will render a terminal in their browser.

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

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,6 @@ Clientless access methods are suited for organizations that cannot deploy the WA
2929

3030
Cloudflare's [browser-based terminal](/cloudflare-one/applications/non-http/browser-rendering/) allows users to connect over SSH and VNC without any configuration. When users visit the public hostname URL (for example, `https://ssh.example.com`) and log in with their Access credentials, Cloudflare will render a terminal in their browser.
3131

32-
When connecting over SSH, Cloudflare supports following key exchange algorithms:
33-
34-
35-
- curve25519-sha256
36-
- ecdh-sha2-nistp256
37-
- ecdh-sha2-nistp384
38-
- ecdh-sha2-nistp521
39-
4032
### Client-side cloudflared (legacy)
4133

4234
:::note

0 commit comments

Comments
 (0)