Skip to main content
sachitdas_FTNT
Staff
Staff
Sep 28, 2026 6:57 AM UTC

Troubleshooting Tip: FortiSwitch 108 model SSH issue in versions 7.6.6/7.6.7/7.6.8

  • Oct 6, 2026 5:55 AM UTC
  • 4 replies
  • 418 views
  • Translate All

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

4 replies

FranFisc1
Explorer
Sep 30, 2026 10:58 AM UTC

to regenerate ssh keys remotely,
you could login via the switch webgui (if https access is enabled, internal switch IP is routed and if you set a password before upgrade)
and open a console window there to regenerate ssh keys.
My logs were filled up with sshd up/down messages… deleted them as well.

Translate
New Member
Oct 5, 2026 8:54 PM UTC

I’m having the same issue going from 7.4.6 to 7.4.10 as well.  Speaking with the support teams 7.4.9 is currently scheduled for release on 11/16/26 with a backup of 11/18/26.  It seems 7.4.10 has a new version of OpenSSH which causes the same issue as well with needing to regenerate SSH keys.

Translate
New Member
Oct 6, 2026 2:52 PM UTC

What’s new in FortiSwitchOS 7.4.10
Release 7.4.10 provides the following new features:

  • FortiSwitchOS now uses a more recent version of OpenSSH.

What’s new in FortiSwitchOS 7.4.10 | FortiSwitch 7.4.10 | Fortinet Document Library

Translate
Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024