Skip to content

Commit 6dfbd51

Browse files
Apply suggestions from code review
Co-authored-by: lgmugnier <[email protected]>
1 parent 3dc3d3e commit 6dfbd51

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/use-cases/ssh/ssh-infrastructure-access.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -278,7 +278,7 @@ After you have verified that there are no issues with your tunnel's health, conf
278278

279279
### 3. Confirm user existence on the server
280280

281-
To verify the existence of the UNIX user on the server, run the `id <USERNAME>` command on the server to verify that the UNIX username exists. If the username does not exist, you must add the user to the server.
281+
To verify the existence of a user on a UNIX server, run the `id <USERNAME>` command on the server to verify that the username exists. If the username does not exist, you must add the user to the server.
282282

283283
If the user exists on the server, debug your `sshd_config` file in the following step.
284284

src/content/partials/cloudflare-one/warp/support-ticket-best-practices.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Refer to the following example of an ideal ticket description:
7070

7171
{props.sshMode ? (
7272
<>
73-
<p>On October 30, 2025, at approximately 3:45 PM UTC, Alice attempted to SSH into 10.116.0.3 (target hostname: prod-db-01) using Access for Infrastructure. The SSH client returned <code>Permission denied (publickey)</code> despite her email being included in the Access policy.</p>
73+
<p>On October 30, 2025, at approximately 3:45 PM UTC, Alice attempted to SSH into 10.116.0.3 (target hostname: prod-db-01) using Access for Infrastructure. The SSH client returned <code>Permission denied (none)</code> despite her email being included in the Access policy.</p>
7474

7575
<p>The <code>sshd</code> logs (captured with LogLevel DEBUG3) are attached and show the connection reaching the server but failing at the certificate validation step. The user exists on the server (<code>id alice</code> verified).</p>
7676

0 commit comments

Comments
 (0)