Skip to content

Commit 40d1a76

Browse files
authored
Update troubleshoot-sftp-issues-using-openssh.md
Edit review per CI 7807
1 parent 4aced44 commit 40d1a76

1 file changed

Lines changed: 18 additions & 18 deletions

File tree

support/windows-server/system-management-components/troubleshoot-sftp-issues-using-openssh.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Troubleshoot Common SFTP issues
3-
description: Explains how to resolve common SFTP issues when using OpenSSH for Windows.
2+
title: Troubleshoot Common SFTP Issues
3+
description: Explains how to resolve common SFTP issues when you use OpenSSH for Windows.
44
ms.date: 11/05/2025
55
manager: dcscontentpm
66
audience: itpro
@@ -15,7 +15,7 @@ appliesto:
1515
---
1616
# Troubleshoot common SFTP issues when using OpenSSH
1717

18-
OpenSSH on Windows provides secure file transfer (SFTP) capabilities. This article describes how to resolve the most common issues that you might encounter while using SFTP and OpenSSH to administer Windows Server and Windows Client.
18+
OpenSSH on Windows provides secure file transfer protocol (SFTP) capabilities. This article describes how to resolve the most common issues that you might encounter when you use SFTP and OpenSSH to administer Windows Server and Windows Client.
1919

2020
## Best practices and additional resources
2121

@@ -24,14 +24,14 @@ OpenSSH on Windows provides secure file transfer (SFTP) capabilities. This artic
2424
- Every time that you change the OpenSSH Server configuration, validate the change by running `sshd -t`.
2525
- When you start troubleshooting, check Event Viewer for relevant events.
2626

27-
For more information about configuring OpenSSH on Windows and Windows Server, see the following articles:
27+
For more information about how to configure OpenSSH on Windows and Windows Server, see the following articles:
2828

2929
- [Get started with OpenSSH for Windows](/windows-server/administration/openssh/openssh_install_firstuse)
3030
- [OpenSSH Server configuration for Windows Server and Windows](/windows-server/administration/openssh/openssh-server-configuration)
3131

3232
### How to enable SFTP logging
3333

34-
To enable SFTP logging for the OpenSSH Server service, modify the sshd_config file, and restart the OpenSSH Server service. Follow these steps:
34+
To enable SFTP logging for the OpenSSH Server service, modify the sshd_config file, and then restart the OpenSSH Server service. Follow these steps:
3535

3636
1. Use an administrator-level account to open a text editor, and then open **%ProgramData%\ssh\sshd_config**. The default text of the "Logging" section should resemble the following excerpt:
3737

@@ -65,7 +65,7 @@ To enable SFTP logging for the OpenSSH Server service, modify the sshd_config fi
6565

6666
After the service restarts, it generates SFTP log data in %ProgramData%\ssh\logs. For more information about OpenSSH logging, see [How to enable OpenSSH verbose logging](enable-openssh-verbose-logging.md).
6767

68-
## Common SFTP Issues on Windows and Windows Server
68+
## Common SFTP issues on Windows and Windows Server
6969

7070
### SFTP users land in the wrong directory or outside the chroot jail
7171

@@ -75,29 +75,29 @@ Check the following settings:
7575

7676
- In the sshd_config file, make sure that `ChrootDirectory` points to a local directory and doesn't use a UNC path.
7777
- Make sure that SYSTEM/Administrators has owner permissions on the chroot directory.
78-
- Make sure that each user has a writeable directory within the chroot directory, and make sure that the directory has the correct permissions. Secure the /.ssh/authorized_keys files.
78+
- Make sure that each user has a writeable directory within the chroot directory, and that the directory has the correct permissions. Secure the /.ssh/authorized_keys files.
7979

8080
> [!NOTE]
81-
> To verify and fix NTFS permissions, use [icacls](/windows-server/administration/windows-commands/icacls) command at an administrative Command Prompt window.
81+
> To verify and fix NTFS permissions, use the [icacls](/windows-server/administration/windows-commands/icacls) command in an administrative Command Prompt window.
8282
83-
- In the sshd_config file, use`ForceCommand internal-sftp`, and use the `-d` switch with the `Subsystem sftp sftp-server.exe` command to set an upload directory. You can use these settings in `Match` blocks to specify users.
83+
- In the sshd_config file, use`ForceCommand internal-sftp`, and use the `-d` switch together with the `Subsystem sftp sftp-server.exe` command to set an upload directory. You can use these settings in `Match` blocks to specify users.
8484

85-
### Particular users can't use SFTP or receive "Access denied" errors
85+
### Specific users can't use SFTP or they receive "Access denied" errors
8686

8787
This behavior indicates ownership or permissions issues. Check the following settings:
8888

8989
- Make sure that SYSTEM/Administrators has owner permissions on the chroot directory.
90-
- Make sure that each user has a writeable directory within the chroot directory, and make sure that the directory has the correct permissions. Secure the /.ssh/authorized_keys files.
90+
- Make sure that each user has a writeable directory within the chroot directory, and that the directory has the correct permissions. Secure the /.ssh/authorized_keys files.
9191

9292
> [!NOTE]
93-
> To verify and fix NTFS permissions, use [icacls](/windows-server/administration/windows-commands/icacls) command at an administrative Command Prompt window.
93+
> To verify and fix NTFS permissions, use the [icacls](/windows-server/administration/windows-commands/icacls) command in an administrative Command Prompt window.
9494
95-
### Users can't sign in or receive "Authentication failed," or "Server refused our key" errors
95+
### Users can't sign in or they receive "Authentication failed" or "Server refused our key"
9696

9797
This behavior indicates public key or password issues. Check the following configurations:
9898

9999
- Use C:\ProgramData\ssh\administrators_authorized_keys to store keys, and use `icacles` to check the file and folder permissions.
100-
- If the server refused the key, add the following lines to sshd_config:
100+
- If the server refuses the key, add the following lines to sshd_config:
101101

102102
```console
103103
PubkeyAcceptedKeyTypes +ssh-rsa
@@ -113,20 +113,20 @@ To resolve these issues, try the following actions:
113113

114114
- To validate the sshd_config settings, run the `sshd -t` command.
115115
- Review Event Viewer for any relevant events.
116-
- To check and repair ACLs on the chroot directory tree, run the `icacles` command.
116+
- To check and repair Access Control Lists (ACLs) on the chroot directory tree, run the `icacles` command.
117117
- Review the sshd_config settings. Make sure that the entries don't have any trailing spaces, and make sure that the `Subsystem sftp sftp-server.exe` command is present.
118118

119-
If none of these actions resolve the issue, uninstall OpenSSH Server and then reinstall it.
119+
If none of these actions resolve the issue, uninstall and reinstall OpenSSH Server.
120120

121121
### SFTP logs are missing or incomplete
122122

123-
Review the log settings in ssdh_config. As described in [How to enable SFTP logging](#how-to-enable-sftp-logging), SFTP log data is stored in %ProgramData%\ssh\logs.
123+
Review the log settings in ssdh_config. SFTP log data is stored in %ProgramData%\ssh\logs.
124124

125125
To check and repair ACLs on the log folder, run the `icacles` command.
126126

127127
### Users can't upload or download files
128128

129129
- In the sshd_config file, make sure that `ChrootDirectory` points to a local directory and doesn't use a UNC path.
130130
- Make sure that SYSTEM/Administrators has owner permissions on the chroot directory.
131-
- Make sure that each user has a writeable directory within the chroot directory, and make sure that the directory has the correct permissions. To check and repair ACLs, run the `icacles` command.
131+
- Make sure that each user has a writeable directory within the chroot directory, and that the directory has the correct permissions. To check and repair ACLs, run the `icacles` command.
132132
- Make sure that users don't have writer permission on the chroot directory.

0 commit comments

Comments
 (0)