-
Notifications
You must be signed in to change notification settings - Fork 767
Troubleshooting Steps
Manoj Ampalam edited this page Feb 2, 2018
·
17 revisions
Troubleshooting steps for typical service startup and connection issues:
- Server side: run
sshd
in debug mode-
Stop-Service sshd
(if sshd service is running) - Open cmd as SYSTEM. Download psexec from here.
psexec -s cmd
sshd.exe -d
- This will dump debug logs in real time to stdout on the console
- You can also add additional
d
s for more detailed loggin:-
sshd.exe -dd
orsshd.exe -ddd
-
-
- Client side: start
ssh
in verbose modessh.exe -v ...
- This will dump verbose logs in real time to stdout on the console
- You can also add additional
v
s to get more verbose messages:-
ssh.exe -vv ...
orssh.exe -vvv
-
Troubleshooting more complex issues:
- Server side
- Stop
sshd
Stop-Service sshd
- Delete
sshd.log
andssh-agent.log
(under %programdata%\ssh\logs) - Set
LogLevel
toDEBUG
(orDEBUG2
/DEBUG3
for higher levels of logging) insshd_config
- Rerun the workflow that's giving you problems.
logs\sshd.log
will containsshd
related traces. - If the problem isn't clear, please post these logs along with some steps to help us reproduce your problem in our GitHub Issues.
- Stop
- Client side
- Set
LogLevel
toDEBUG
(orDEBUG2
/DEBUG3
for higher levels of logging) inssh_config
. - Run
ssh.exe
in verbose mode as detailed above
- Set
- MSI Install Instructions
- Script Install Instructions
- Alternative installation using the universal installer
- Retrieving download links for the latest packages