<metaname="description"content="Stuck with errors trying to get your SSH setup configured? See below for some common problems. Or as always, reach out to us by creating an Issue or start a Discussion"/>
<metaproperty="og:description"content="Stuck with errors trying to get your SSH setup configured? See below for some common problems. Or as always, reach out to us by creating an Issue or start a Discussion"/>
{"datePublished":"2023-10-13T02:42:45+00:00","description":"Stuck with errors trying to get your SSH setup configured? See below for some common problems. Or as always, reach out to us by creating an Issue or start a Discussion","mainEntityOfPage":{"@type":"WebPage","@id":"/enigma-bbs/troubleshooting/ssh-troubleshooting.html"},"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"/enigma-bbs/assets/images/enigma-logo.png"}},"url":"/enigma-bbs/troubleshooting/ssh-troubleshooting.html","@type":"BlogPosting","headline":"Troubleshooting SSH","dateModified":"2023-10-13T02:42:45+00:00","@context":"https://schema.org"}</script>
<p>Stuck with errors trying to get your SSH setup configured? See below for some common problems. Or as always, reach out to us by creating an <ahref="https://github.com/NuSkooler/enigma-bbs/issues">Issue</a> or start a <ahref="https://github.com/NuSkooler/enigma-bbs/discussions">Discussion</a></p>
<h2id="no-such-file-or-directory">No Such File or Directory</h2>
<p><strong><em>Symptom:</em></strong>
BBS not starting with an error similar to the following:</p>
<divclass="language-shell highlighter-rouge"><divclass="highlight"><preclass="highlight"><code>Error initializing: Error: ENOENT: no such file or directory, open <spanclass="s1">'<path>/config/security/ssh_private_key.pem'</span>
</code></pre></div></div>
<p><strong><em>Solution:</em></strong>
Several things can cause this:</p>
<ol>
<li><codeclass="language-plaintext highlighter-rouge">ssh_private_key.pem</code> was installed to the wrong location. Make sure that it is in the <codeclass="language-plaintext highlighter-rouge">config/security</code> directory and has the name matching the error message. You can also change your <codeclass="language-plaintext highlighter-rouge">config.hjson</code> if you prefer to point to the location of the key file.</li>
<li><codeclass="language-plaintext highlighter-rouge">ssh_private_key.pem</code> has the wrong file permissions. Verify that the file will be readable by the user that the BBS is running as. Because it is a cryptographic key however, we do recommend that access is restricted only to that user.</li>
</ol>
<h2id="error-with-netrunner">Error With Netrunner</h2>
<p><strong><em>Symptom:</em></strong>
Some ssh clients connect, but Netrunner (and other older clients) get a connection failed message and the following is in the log:</p>
<p>The key was most likely not generated with the <codeclass="language-plaintext highlighter-rouge">-t rsa</code> option, and is using a newer algorithm that is not supported by Netrunner and similar clients. Regenerate the certificate with the <codeclass="language-plaintext highlighter-rouge">-t rsa</code> option.</p>
<p><strong><em>Symptom:</em></strong>
Some ssh clients connect, but Netrunner (and other older clients) get a connection failed message and the following is in the log:</p>
<divclass="language-shell highlighter-rouge"><divclass="highlight"><preclass="highlight"><code><spanclass="s2">"level"</span>:40,<spanclass="s2">"error"</span>:<spanclass="s2">"Group exchange not implemented for server"</span>,<spanclass="s2">"msg"</span>:<spanclass="s2">"SSH connection error"</span>
</code></pre></div></div>
<p><strong><em>Solution:</em></strong></p>
<p>Remove the following encryption protocols from your <codeclass="language-plaintext highlighter-rouge">config.hjson</code>: <codeclass="language-plaintext highlighter-rouge">diffie-hellman-group-exchange-sha256</code> and <codeclass="language-plaintext highlighter-rouge">diffie-hellman-group-exchange-sha1</code></p>
