<?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[Fail2ban (and other security activity) in Event Logs]]></title><description><![CDATA[<p dir="auto">Correct me if I'm wrong but currently there's no specific log for fail2ban activity, is there? If I'm correct, it would be great to have fail2ban logs (and / or other security activity) in the "Event Logs".</p>
]]></description><link>https://forum.cloudron.io/topic/2223/fail2ban-and-other-security-activity-in-event-logs</link><generator>RSS for Node</generator><lastBuildDate>Wed, 11 Mar 2026 10:54:15 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/2223.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 12 Mar 2020 11:22:25 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Fail2ban (and other security activity) in Event Logs on Tue, 09 Aug 2022 07:40:20 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> Thanks for the tip on updating SSH-keys.</p>
<p dir="auto">I wasn't talking about fail2ban reporting, only. I was also referring to the built-in "rate-limiting" of Cloudron (and other security features, e.g. the cloud firewall) where there's currently little or no transparency what's happening.</p>
<p dir="auto">Since Cloudron "takes over the server" I think it would be a good opportunity to add transparent monitoring of the system's security features similar to the "System info" tab...</p>
]]></description><link>https://forum.cloudron.io/post/51783</link><guid isPermaLink="true">https://forum.cloudron.io/post/51783</guid><dc:creator><![CDATA[necrevistonnezr]]></dc:creator><pubDate>Tue, 09 Aug 2022 07:40:20 GMT</pubDate></item><item><title><![CDATA[Reply to Fail2ban (and other security activity) in Event Logs on Mon, 08 Aug 2022 14:11:45 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/necrevistonnezr" aria-label="Profile: necrevistonnezr">@<bdi>necrevistonnezr</bdi></a> We have to look into fail2ban style reporting. But in the meantime, if you haven't already, you should move to ed25519 keys . We have done this with our support keys as well. Previously it was RSA, now it is ED25519 (<a href="https://docs.cloudron.io/support/#ssh-keys" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.cloudron.io/support/#ssh-keys</a>) .</p>
<p dir="auto"><a href="https://risanb.com/code/upgrade-ssh-key-to-ed25519/" target="_blank" rel="noopener noreferrer nofollow ugc">https://risanb.com/code/upgrade-ssh-key-to-ed25519/</a> has some good notes.</p>
]]></description><link>https://forum.cloudron.io/post/51747</link><guid isPermaLink="true">https://forum.cloudron.io/post/51747</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Mon, 08 Aug 2022 14:11:45 GMT</pubDate></item><item><title><![CDATA[Reply to Fail2ban (and other security activity) in Event Logs on Mon, 08 Aug 2022 08:04:10 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> said in <a href="/post/6459">Fail2ban (and other security activity) in Event Logs</a>:</p>
<blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/necrevistonnezr" aria-label="Profile: necrevistonnezr">@<bdi>necrevistonnezr</bdi></a> There is no fail2ban on Cloudron. Currently, we just rate limit all authentication routes to minimize risk (and with 2FA and app passwords risks are even lower now). We had a plan to implement firewalling this release (rate limits per IP, block specific IP etc), but already changes were piling up. So, we will have some more advanced firewalling features in a future release.</p>
</blockquote>
<p dir="auto">Hi, as I'm still pondering securing my home server Cloudron setup (with all those open ports), I'd like to re-visit this topic. It'd be very helpful as a first step if rate limiting incidents and other relevant information (e.g. <a href="https://docs.cloudron.io/security/#fail2ban" target="_blank" rel="noopener noreferrer nofollow ugc">fail2ban for SSH</a>) would be available in Cloudron without using the terminal and polling logs in several different places.</p>
]]></description><link>https://forum.cloudron.io/post/51708</link><guid isPermaLink="true">https://forum.cloudron.io/post/51708</guid><dc:creator><![CDATA[necrevistonnezr]]></dc:creator><pubDate>Mon, 08 Aug 2022 08:04:10 GMT</pubDate></item><item><title><![CDATA[Reply to Fail2ban (and other security activity) in Event Logs on Thu, 12 Mar 2020 20:37:23 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/necrevistonnezr" aria-label="Profile: necrevistonnezr">@<bdi>necrevistonnezr</bdi></a> There is no fail2ban on Cloudron. Currently, we just rate limit all authentication routes to minimize risk (and with 2FA and app passwords risks are even lower now). We had a plan to implement firewalling this release (rate limits per IP, block specific IP etc), but already changes were piling up. So, we will have some more advanced firewalling features in a future release.</p>
]]></description><link>https://forum.cloudron.io/post/6459</link><guid isPermaLink="true">https://forum.cloudron.io/post/6459</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 12 Mar 2020 20:37:23 GMT</pubDate></item></channel></rss>