# Sshd fails to start after upgrade to Trixie **URL:** \ **Category:** AllStarLink\ **Created:** [September 15, 2025, 1:59pm UTC](https://community.allstarlink.org/t/sshd-fails-to-start-after-upgrade-to-trixie/23743 "2025-09-15T13:59:58Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![M7DHQ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/m7dhq/32/3032_2.png) [@M7DHQ](https://community.allstarlink.org/u/M7DHQ)\ **Post date:** [September 15, 2025, 1:59pm UTC](https://community.allstarlink.org/t/sshd-fails-to-start-after-upgrade-to-trixie/23743/1 "2025-09-15T13:59:58Z")
> **Version Details** > > ## \*\*\*\*\*\*\*\*\*\* AllStarLink [ASL] Version Info \*\*\*\*\*\*\*\*\*\* > > OS : Debian GNU/Linux 13 (trixie) > OS Kernel : 6.12.34+rpt-rpi-v8 > > Asterisk : 22.4.1+asl3-3.5.5-1.deb12 > ASL [app\_rpt] : 3.5.5 > > Installed ASL packages : > > Package Version > ============================== ============================== > allmon3 1.6.0-3.deb12 > asl3 3.8-1.deb > asl3-asterisk 2:22.4.1+asl3-3.5.5-1.deb12 > asl3-asterisk-config 2:22.4.1+asl3-3.5.5-1.deb12 > asl3-asterisk-modules 2:22.4.1+asl3-3.5.5-1.deb12 > asl3-menu 1.14-1.deb12 > asl3-pi-appliance 1.10.0-1.deb12 > asl3-tts 1.0.1-1.deb12 > asl3-update-nodelist 1.5.1-1.deb12 > cockpit 337-1 > cockpit-bridge 337-1 > cockpit-networkmanager 337-1 > cockpit-packagekit 337-1 > cockpit-sosreport 337-1 > cockpit-storaged 337-1 > cockpit-system 337-1 > cockpit-wifimanager 1.1.1-1.deb12 > cockpit-ws 337-1 > dahdi 1:3.1.0-2.1 > dahdi-dkms 1:3.4.0-7.asl > dahdi-linux 1:3.4.0-7.asl > dahdi-source 1:3.4.0-7.asl Updated 2 nodes over the weekend, these are both PIs using the PI image, which includes cockpit etc. Both updated fine, rebooted fine and never noticed until today that sshd has not started on both nodes. Luckily cockpit includes a terminal so I could do some debugging. In the services menu it reports: **`Failed to start ssh.service - OpenBSD Secure Shell server.`** Opening the terminal I manually run `/usr/sbin/sshd -T` which reports: `/etc/ssh/sshd_config line 123: Bad IPQoS value: 0x00` Line 123 of that file is the very last line and reads `IPQoS 0x00` To quote the manual for sshd\_config and that setting: > Accepted values are af11, af12, af13, af21, > af22, af23, af31, af32, af33, af41, af42, af43, cs0, cs1, > cs2, cs3, cs4, cs5, cs6, cs7, ef, le, lowdelay, > throughput, reliability, a numeric value, or none to use > the operating system default. So `0x00` is not a valid setting and sshd fails to start. I changed the value in my config to an accepted value and sshd starts with no issues. ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [September 17, 2025, 2:09pm UTC](https://community.allstarlink.org/t/sshd-fails-to-start-after-upgrade-to-trixie/23743/2 "2025-09-17T14:09:47Z")
I had a similar problem when updating my Mac to MacOS 26 Tahoe. I was getting this error: ```ini /Users/xxxxxxx/.ssh/config line 3: Bad key types '+ssh-rsa,ssh-dss'. /Users/xxxxxxx/.ssh/config: terminating, 1 bad configuration options ``` There was a line `#HostKeyAlgorithms +ssh-rsa,ssh-dss` in my Mac’s .ssh/config file which I’ve commented as shown. Problem solved. Just to be clear, this was not a Trixi problem. It occurred when using the Mac terminal to ssh to any Linux server. ---
**Author:** ![M7DHQ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/m7dhq/32/3032_2.png) [@M7DHQ](https://community.allstarlink.org/u/M7DHQ)\ **Post date:** [September 17, 2025, 3:13pm UTC](https://community.allstarlink.org/t/sshd-fails-to-start-after-upgrade-to-trixie/23743/3 "2025-09-17T15:13:35Z")
Thats odd, I updated to Tahoe yesterday on my works mac I didnt get any ssh issues with any server, is it an old mac install thats been upgraded over the years? Edit: I dont even have a config file in `~/.ssh/` so maybe that was something you added moons ago? Homebrew maybe? ---
**Author:** ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)\ **Post date:** [September 17, 2025, 3:50pm UTC](https://community.allstarlink.org/t/sshd-fails-to-start-after-upgrade-to-trixie/23743/4 "2025-09-17T15:50:54Z")
I use a Mac App called Shuttle. [Shuttle | A simple shortcut menu for macOS](https://fitztrev.github.io/shuttle/). It sits in the menubar providing a list of all your hosts like so… ![Screenshot 2025-09-17 at 8.39.31 AM](https://community.allstarlink.org/uploads/default/original/2X/3/30c085974f88b6db78aeefd9aee4f654365dd314.png) It reads the .ssh/config file for your ssh settings. It’s very handy Here’s an example config. Note the forward slash provides organization of your systems as seen above. ```auto ######## WD6AWP AllStar ######## Host 6AWP/ASL/node-xyz Hostname x.y.x User xyz IdentityFile ~/.ssh/xyz ``` Shuttle also has its own config file accessible from the menu. I use that for non ssh sessions like telnet. For more info Google something like **how to use the .ssh/config file on MacOS**. ---
**Author:** ![M7DHQ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/m7dhq/32/3032_2.png) [@M7DHQ](https://community.allstarlink.org/u/M7DHQ)\ **Post date:** [September 17, 2025, 4:08pm UTC](https://community.allstarlink.org/t/sshd-fails-to-start-after-upgrade-to-trixie/23743/5 "2025-09-17T16:08:06Z")
Anyway, to swing us back on topic I did notice that both the nodes were PIs using the “appliance” install with cockpit and the other two nodes that updated with no issue whatsoever are both on x86 ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [September 18, 2025, 12:42am UTC](https://community.allstarlink.org/t/sshd-fails-to-start-after-upgrade-to-trixie/23743/6 "2025-09-18T00:42:58Z")
> [@M7DHQ](#): > > /etc/ssh/sshd\_config line 123: Bad IPQoS value: 0x00 This appears to be introduced by the CustomPiOS builder we're using to generate the Pi Appliance. I never ran into it before but I will chop it out for the next release of the image. I will also add something to `postinst` in the asl3-pi-appliance package to remove it. For now, run this command before upgrading to Trixie: ```bash perl -pi -e 's/^IPQoS\s+0x00$//' /etc/ssh/sshd_config ``` ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [September 19, 2025, 1:22am UTC](https://community.allstarlink.org/t/sshd-fails-to-start-after-upgrade-to-trixie/23743/7 "2025-09-19T01:22:42Z")
asl3-pi-appliance v1.10.1-1 currently in beta and soon to promote to main will address this. Make sure v1.10.1-1 (or greater) is installed prior to a Trixie upgrade attempt. ---
**Author:** ![system](https://community.allstarlink.org/uploads/default/original/2X/4/42700284e201b031bd667c3f63bbae05a74b3104.png) [@system](https://community.allstarlink.org/u/system)\ **Post date:** [September 22, 2025, 1:23am UTC](https://community.allstarlink.org/t/sshd-fails-to-start-after-upgrade-to-trixie/23743/8 "2025-09-22T01:23:40Z")
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.