<?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 2.1 released]]></title><description><![CDATA[<p dir="auto">2.1 is now available for all. You can read more in our <a href="https://cloudron.io/blog/2018-04-20-cloudron-2.1.html" target="_blank" rel="noopener noreferrer nofollow ugc">blog post</a></p>
<p dir="auto">Highlights:</p>
<ul>
<li>We have reworked how mailboxes work. Mailboxes and aliases can now be managed in the email view. All Cloudron subscription plans include <strong>unlimited mailboxes and aliases</strong>.</li>
<li>Initial support for installation for apps from private a docker registries like Amazon ECR, <a href="http://quay.io" target="_blank" rel="noopener noreferrer nofollow ugc">quay.io</a>.</li>
</ul>
]]></description><link>https://forum.cloudron.io/topic/1305/cloudron-2-1-released</link><generator>RSS for Node</generator><lastBuildDate>Mon, 13 Jul 2026 22:25:30 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/1305.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 23 Apr 2018 17:25:34 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Cloudron 2.1 released on Wed, 25 Apr 2018 21:15:34 GMT]]></title><description><![CDATA[<p dir="auto">We have another issue related to docker not upgrading because of unmet deps.</p>
<p dir="auto">Check <code>journalctl -fa</code> and if it shows something like below over and over again:</p>
<pre><code>The following packages have unmet dependencies:
 docker-ce : Depends: libseccomp2 (&gt;= 2.3.0) but 2.2.3-3ubuntu3 is to be installed
E: Unable to correct problems, you have held broken packages.
</code></pre>
<p dir="auto">To fix:</p>
<pre><code>apt update
</code></pre>
<p dir="auto">You might have to run the above command a couple of times since it might says it cannot get the lock. Once the update is done, it should update automatically.</p>
]]></description><link>https://forum.cloudron.io/post/1473</link><guid isPermaLink="true">https://forum.cloudron.io/post/1473</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Wed, 25 Apr 2018 21:15:34 GMT</pubDate></item><item><title><![CDATA[Reply to Cloudron 2.1 released on Tue, 24 Apr 2018 23:47:06 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/vnr" aria-label="Profile: vnr">@<bdi>vnr</bdi></a> Can you check <code>journalctl -fa</code> logs?</p>
]]></description><link>https://forum.cloudron.io/post/1458</link><guid isPermaLink="true">https://forum.cloudron.io/post/1458</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Tue, 24 Apr 2018 23:47:06 GMT</pubDate></item><item><title><![CDATA[Reply to Cloudron 2.1 released on Tue, 24 Apr 2018 22:33:53 GMT]]></title><description><![CDATA[<p dir="auto">Hello</p>
<p dir="auto">This dosen't Works for me.<br />
i can't update from 2.0.1 to 2.1.0</p>
<p dir="auto">the update process remains at "Downloading and installing new version"<br />
i am using Ubuntu Server 16.04.3 LTS</p>
<p dir="auto">Please Help</p>
]]></description><link>https://forum.cloudron.io/post/1457</link><guid isPermaLink="true">https://forum.cloudron.io/post/1457</guid><dc:creator><![CDATA[vnr]]></dc:creator><pubDate>Tue, 24 Apr 2018 22:33:53 GMT</pubDate></item><item><title><![CDATA[Reply to Cloudron 2.1 released on Wed, 25 Apr 2018 19:54:27 GMT]]></title><description><![CDATA[<p dir="auto">We have a few Cloudrons that are failing to update because the disk is full for apt to work. A possible reason is that the many kernel updates pushed by the VPS providers for spectre/meltdown did not completely work.</p>
<p dir="auto">First check if <code>sudo du -hcs /var/tmp</code> has lots of data. Or check if <code>/boot</code> is full using <code>df -h /boot</code>. If <code>/boot</code> is full, you have to manually remove some of the old kernels:</p>
<pre><code>root@my:/boot# uname -nar
Linux my.cloudron 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@my:/boot# rm initrd.img-4.4.0-101-generic initrd.img-4.4.0-103-generic
</code></pre>
<p dir="auto">Now <code>/boot</code> should have some free space:</p>
<pre><code>apt -f install
purge-old-kernels   # this removes old kernels and cleans up /boot
rm -rf /var/tmp/mkinitramfs*
dpkg --configure -a
apt-get install
apt autoremove
</code></pre>
<p dir="auto">Check if <code>unbound</code> is working:</p>
<pre><code>systemctl status unbound
</code></pre>
<p dir="auto">It must say <code>active (running)</code>. If not, run the following commands:</p>
<pre><code>sudo unbound-anchor -a /var/lib/unbound/root.key
sudo systemctl restart unbound
</code></pre>
]]></description><link>https://forum.cloudron.io/post/1456</link><guid isPermaLink="true">https://forum.cloudron.io/post/1456</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Wed, 25 Apr 2018 19:54:27 GMT</pubDate></item><item><title><![CDATA[Reply to Cloudron 2.1 released on Mon, 23 Apr 2018 19:17:11 GMT]]></title><description><![CDATA[<p dir="auto">Known issues:</p>
<ul>
<li>(only multi-domain email setups) If there was an alias in one domain with name say 'foobar' and a mailbox in another domain with the same name 'foobar', then the migration code sometimes imports the mailbox of the second domain incorrectly as an 'alias' instead of a 'mailbox'. If you encounter this issue, please contact us at <a href="mailto:support@cloudron.io" target="_blank" rel="noopener noreferrer nofollow ugc">support@cloudron.io</a> (and enable ssh access). We have to patch up the DB by hand. Note that the mail server itself is running fine and there is no issue sending/receiving email. Just that the db entry is wrong which causes authentication to fail.</li>
</ul>
]]></description><link>https://forum.cloudron.io/post/1449</link><guid isPermaLink="true">https://forum.cloudron.io/post/1449</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Mon, 23 Apr 2018 19:17:11 GMT</pubDate></item></channel></rss>