Troubleshooting Tip: FortiSwitch 108 model SSH issue in versions 7.6.6/7.6.7/7.6.8
Description
This article describes an issue where, after upgrading FortiSwitch 108 to versions 7.6.6, 7.6.7, or 7.6.8, SSH access to the switch may fail.
Scope
FortiSwitch 108 running versions 7.6.6, 7.6.7, or 7.6.8.
Solution
While performing SSH to the FortiSwitch, the message below appears:
host:~$ ssh admin@FortiSwitch IP
admin@FortiSwitch IP's password:
client_loop: send disconnect: Broken pipe
While collecting sshd application debug, the following message appears on the FortiSwitch, and it fails at this point:
SSH: send packet: type 51
SSH: receive packet: type 50
SSH: userauth-request for user ansible service ssh-connection method
publickey
SSH: attempt 1 failures 0
In the FortiSwitch crash log, a constant crash of the sshd process can be seen
70: 2026-06-08 21:16:12 the killed daemon is /bin/sshd: status=0x100
71: 2026-06-08 21:16:14 the killed daemon is /bin/sshd: status=0x100
72: 2026-06-08 21:16:16 the killed daemon is /bin/sshd: status=0x100
73: 2026-06-08 21:16:18 the killed daemon is /bin/sshd: status=0x100
74: 2026-06-08 21:16:20 the killed daemon is /bin/sshd: status=0x100
75: 2026-06-08 21:16:22 the killed daemon is /bin/sshd: status=0x100
76: 2026-06-08 21:16:24 the killed daemon is /bin/sshd: status=0x100
77: 2026-06-08 21:16:26 the killed daemon is /bin/sshd: status=0x100
78: 2026-06-08 21:16:28 the killed daemon is /bin/sshd: status=0x100
79: 2026-06-08 21:16:30 the killed daemon is /bin/sshd: status=0x100
80: 2026-06-08 21:16:32 the killed daemon is /bin/sshd: status=0x100
81: 2026-06-08 21:16:34 the killed daemon is /bin/sshd: status=0x100
The issue is fixed in FortiSwitch version 7.6.9.
Workaround:
From the FortiSwitch console, regenerate the SSH keys using:
execute ssh-regen-keys