<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Suggestion: Improvement on setup process, SSHD Listen port]]></title><description><![CDATA[<p dir="auto">Hello to everyone (feels like I forgot being polite in my other two posts),</p>
<p dir="auto">I recently installed cauldron on a VPS after having secured said VPS.<br />
Including in securing it was the following :</p>
<ul>
<li>moving SSH to port 39552 (or something alike)</li>
<li>installing fail2ban</li>
<li>whitelisting port 39552</li>
</ul>
<p dir="auto">After Cloudron installation, sshd was still listenning on the custom port while cloudron-firewall was blocking it.<br />
It was then impossible to use SSH to adress the issu and the remote KVM of my provider made it hard for me to resolv it the right way.</p>
<p dir="auto">My suggestion is to add the following steps in the setup :</p>
<ul>
<li>Check the current listening port of sshd</li>
<li>Whitelist this port</li>
</ul>
<p dir="auto">Regards,<br />
sholan</p>
]]></description><link>https://forum.cloudron.io/topic/10516/suggestion-improvement-on-setup-process-sshd-listen-port</link><generator>RSS for Node</generator><lastBuildDate>Sun, 16 Aug 2026 07:57:38 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/10516.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 24 Nov 2023 13:55:25 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Suggestion: Improvement on setup process, SSHD Listen port on Fri, 24 Nov 2023 15:29:57 GMT]]></title><description><![CDATA[<p dir="auto">right, so in the cases I've tested it just exits with:</p>
<pre><code>/usr/sbin/sshd -T
sshd: no hostkeys available -- exiting.
</code></pre>
]]></description><link>https://forum.cloudron.io/post/78124</link><guid isPermaLink="true">https://forum.cloudron.io/post/78124</guid><dc:creator><![CDATA[nebulon]]></dc:creator><pubDate>Fri, 24 Nov 2023 15:29:57 GMT</pubDate></item><item><title><![CDATA[Reply to Suggestion: Improvement on setup process, SSHD Listen port on Fri, 24 Nov 2023 15:01:23 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nebulon" aria-label="Profile: nebulon">@<bdi>nebulon</bdi></a> said in <a href="/post/78111">Suggestion: Improvement on setup process, SSHD Listen port</a>:</p>
<blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/sholan" aria-label="Profile: sholan">@<bdi>sholan</bdi></a> do you know a very robust way to detect the port SSHd is using with bare minimum built-in tools? Such detection may cause side-effects if init scripts fail due to parsing errors of config files or VPS provider customize their Ubuntu images. But generally sounds like a good idea, if of course chaning sshd port is a common use-case for our users. So maybe lets wait for other to raise interest.</p>
</blockquote>
<p dir="auto">Maybe this is naïve but:<br />
<code>/usr/sbin/sshd -T | grep "^port " | cut -d" " -f 2</code><br />
or with awk :<br />
<code>/usr/sbin/sshd -T | grep "^port " | awk '{print $2}'</code></p>
]]></description><link>https://forum.cloudron.io/post/78123</link><guid isPermaLink="true">https://forum.cloudron.io/post/78123</guid><dc:creator><![CDATA[sholan]]></dc:creator><pubDate>Fri, 24 Nov 2023 15:01:23 GMT</pubDate></item><item><title><![CDATA[Reply to Suggestion: Improvement on setup process, SSHD Listen port on Fri, 24 Nov 2023 14:24:01 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/nebulon" aria-label="Profile: nebulon">@<bdi>nebulon</bdi></a></p>
<p dir="auto">I am not of any help regarding the constraints, I'd go headlong towar parsing /etc/ssh/sshd_config ... grep Listen</p>
<p dir="auto">But as you said, drawbacks exist.<br />
netstat might not be present on the system and so on</p>
<p dir="auto">I'm just raising an idea, I'm far from having all the constraints in mind <img src="https://forum.cloudron.io/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=090c346130c" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
<p dir="auto">Thank you, this is really nice to be part of it, Cloudron is just a dream come true, wish I had heard about it years ago</p>
]]></description><link>https://forum.cloudron.io/post/78114</link><guid isPermaLink="true">https://forum.cloudron.io/post/78114</guid><dc:creator><![CDATA[sholan]]></dc:creator><pubDate>Fri, 24 Nov 2023 14:24:01 GMT</pubDate></item><item><title><![CDATA[Reply to Suggestion: Improvement on setup process, SSHD Listen port on Fri, 24 Nov 2023 14:17:24 GMT]]></title><description><![CDATA[<p dir="auto">ah and welcome to the community! <img src="https://forum.cloudron.io/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=090c346130c" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
]]></description><link>https://forum.cloudron.io/post/78112</link><guid isPermaLink="true">https://forum.cloudron.io/post/78112</guid><dc:creator><![CDATA[nebulon]]></dc:creator><pubDate>Fri, 24 Nov 2023 14:17:24 GMT</pubDate></item><item><title><![CDATA[Reply to Suggestion: Improvement on setup process, SSHD Listen port on Fri, 24 Nov 2023 14:17:07 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/sholan" aria-label="Profile: sholan">@<bdi>sholan</bdi></a> do you know a very robust way to detect the port SSHd is using with bare minimum built-in tools? Such detection may cause side-effects if init scripts fail due to parsing errors of config files or VPS provider customize their Ubuntu images. But generally sounds like a good idea, if of course chaning sshd port is a common use-case for our users. So maybe lets wait for other to raise interest.</p>
]]></description><link>https://forum.cloudron.io/post/78111</link><guid isPermaLink="true">https://forum.cloudron.io/post/78111</guid><dc:creator><![CDATA[nebulon]]></dc:creator><pubDate>Fri, 24 Nov 2023 14:17:07 GMT</pubDate></item><item><title><![CDATA[Reply to Suggestion: Improvement on setup process, SSHD Listen port on Fri, 24 Nov 2023 14:15:09 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/girish" aria-label="Profile: girish">@<bdi>girish</bdi></a> indeed, it is related.</p>
<p dir="auto">The idea here is to prevent locking out an admin, while the other topic is to help such admin do the same but after Cloudron installation</p>
]]></description><link>https://forum.cloudron.io/post/78110</link><guid isPermaLink="true">https://forum.cloudron.io/post/78110</guid><dc:creator><![CDATA[sholan]]></dc:creator><pubDate>Fri, 24 Nov 2023 14:15:09 GMT</pubDate></item><item><title><![CDATA[Reply to Suggestion: Improvement on setup process, SSHD Listen port on Fri, 24 Nov 2023 14:10:10 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/sholan" aria-label="Profile: sholan">@<bdi>sholan</bdi></a> I guess this is same (or related to) <a href="https://forum.cloudron.io/topic/10515/suggestion-in-the-doc-linking-ssh-access-securing-and-port-whitelisting">https://forum.cloudron.io/topic/10515/suggestion-in-the-doc-linking-ssh-access-securing-and-port-whitelisting</a> ?</p>
]]></description><link>https://forum.cloudron.io/post/78106</link><guid isPermaLink="true">https://forum.cloudron.io/post/78106</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Fri, 24 Nov 2023 14:10:10 GMT</pubDate></item></channel></rss>