<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OpenSSH on Support Tools</title><link>https://support.tools/tags/openssh/</link><description>Recent content in OpenSSH on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://support.tools/tags/openssh/index.xml" rel="self" type="application/rss+xml"/><item><title>Fix sshd: no hostkeys available -- exiting (WSL, Ubuntu)</title><link>https://support.tools/post/wsl-ssh-server-keys/</link><pubDate>Sun, 30 Jun 2024 23:18:00 -0500</pubDate><guid>https://support.tools/post/wsl-ssh-server-keys/</guid><description>&lt;p&gt;&lt;code&gt;sshd: no hostkeys available -- exiting.&lt;/code&gt; is printed when the OpenSSH server starts and cannot load a single host key from &lt;code&gt;/etc/ssh&lt;/code&gt;. The fix is one command, &lt;code&gt;sudo ssh-keygen -A&lt;/code&gt;, which creates every missing host key type. This guide shows the exact output before and after, why WSL and container images ship without keys, the other two causes that print the same line (bad permissions and a wrong &lt;code&gt;HostKey&lt;/code&gt; path), and what clients see after the keys change.&lt;/p&gt;</description></item></channel></rss>