<?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[Cloudron completely broken after update/reboot]]></title><description><![CDATA[<p dir="auto">Came into the Cloudron interface and found a reboot required message</p>
<p dir="auto">Did the reboot, and then found ipv6 broken - I was able to address this using the following approach;</p>
<pre><code>sudo sysctl -w net.ipv6.conf.ens18.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.tailscale0.disable_ipv6=1
sudo systemctl restart box
</code></pre>
<p dir="auto">That said, and after a reboot, I then found the Mailserver service was completely down both internally and externally - a closer examination revealed a mail container corruption overlay filesystem reference, preventing the service from starting - ie, mail configuration directory at <code>/home/yellowtent/platformdata/mail/</code> was missing, preventing automatic recreation by the box service</p>
<p dir="auto">Would also add that standard recovery attempts(sudo systemctl restart box), was not successful, in-that the mail container would be automatically recreated</p>
<p dir="auto">A closer look revealed the configuration was missing;<br />
sudo ls -la /home/yellowtent/platformdata/mail/</p>
<blockquote>
<p dir="auto">no such file or directory</p>
</blockquote>
<p dir="auto">And that a forced rebuild was needed;<br />
sudo rm /home/yellowtent/platformdata/INFRA_VERSION</p>
<p dir="auto">BTW, this same thing happened in previous months with Cloudron, following an automated update - granted, snapshots can(and should), be made priior-to any type of update/OS or otherwise, though I can't help but feel that issues like this should not occur so frequently, even on a personal use level</p>
<ul>
<li>hope this helps someone out there</li>
</ul>
]]></description><link>https://forum.cloudron.io/topic/14119/cloudron-completely-broken-after-update-reboot</link><generator>RSS for Node</generator><lastBuildDate>Wed, 15 Jul 2026 19:38:19 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/14119.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 26 Jul 2025 07:40:32 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Cloudron completely broken after update/reboot on Mon, 08 Sep 2025 10:50:10 GMT]]></title><description><![CDATA[<p dir="auto">Closing this issue for now since no further details where provided.</p>
]]></description><link>https://forum.cloudron.io/post/112489</link><guid isPermaLink="true">https://forum.cloudron.io/post/112489</guid><dc:creator><![CDATA[james]]></dc:creator><pubDate>Mon, 08 Sep 2025 10:50:10 GMT</pubDate></item><item><title><![CDATA[Reply to Cloudron completely broken after update/reboot on Mon, 28 Jul 2025 15:46:02 GMT]]></title><description><![CDATA[<p dir="auto">The more details the better.<br />
This is very uncommon.</p>
]]></description><link>https://forum.cloudron.io/post/110822</link><guid isPermaLink="true">https://forum.cloudron.io/post/110822</guid><dc:creator><![CDATA[james]]></dc:creator><pubDate>Mon, 28 Jul 2025 15:46:02 GMT</pubDate></item><item><title><![CDATA[Reply to Cloudron completely broken after update/reboot on Sat, 26 Jul 2025 18:25:47 GMT]]></title><description><![CDATA[<p dir="auto">The first time this took place(update, notification/broken Cloudron services), was on a VPS hosted by SSDnodes - thus constituting my first experience with the infamous IPv6 bug, and as a result of a reboot request(notification), following a Cloudron update.</p>
<p dir="auto">In this particular case, and though I did confirm the IPv6 issue, I chose not to repair, in-favor of rolling-back(snapshot), for the sake of brevity.</p>
<p dir="auto">Fast-forward to this round - and on a rather fresh Cloudron installation, on Proxmox VM w/different provider, I'd add that both instances would constituted what I'd call vanilla, in-that they were both simple mail servers, with a single SOGo application for webmail.</p>
<p dir="auto">Beyond that, there were no modifications made on either instances beyond the addition of nftables.</p>
<p dir="auto">NB, the first instance was on a network with IPv6 support, whereas the second(more recent), is on an IPv4 only network.</p>
<p dir="auto">PS, if you would like additional details on this particular incident, please don't hesitate to ask as the details remain fresh on my purview, and moreso, that I would really like to help in improving the Cloudron experience for others</p>
]]></description><link>https://forum.cloudron.io/post/110732</link><guid isPermaLink="true">https://forum.cloudron.io/post/110732</guid><dc:creator><![CDATA[JohnBee]]></dc:creator><pubDate>Sat, 26 Jul 2025 18:25:47 GMT</pubDate></item><item><title><![CDATA[Reply to Cloudron completely broken after update/reboot on Sat, 26 Jul 2025 10:15:47 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/johnbee" aria-label="Profile: JohnBee">@<bdi>JohnBee</bdi></a><br />
This is rather odd that it happened twice already.<br />
What is your provider for hosting the server and did you do any customization underneath Cloudron?</p>
]]></description><link>https://forum.cloudron.io/post/110722</link><guid isPermaLink="true">https://forum.cloudron.io/post/110722</guid><dc:creator><![CDATA[james]]></dc:creator><pubDate>Sat, 26 Jul 2025 10:15:47 GMT</pubDate></item></channel></rss>