@shai Yeah, it's tricky Thanks for your this hint, anyway, here's a screenshot for lazy ppl [image: 1607555574126-screenshot-2020-12-10-at-01.05.01.png] [image: 1607555601662-screenshot-2020-12-10-at-01.07.01.png]

It worked! My instance and dashboard are back online with all my data restored. I can feel the awesomeness of Cloudron again. In the end the install with ./cloudron-setup --version 5.6.3 seem to have worked on Ubuntu LTS (after a minor version downgrade of NGINX). Now that I've mastered the install/restore I can always go back to Ubuntu 18 if I have any problem. Thank you again for your help.

@marcusquinn said in Marking Topics Solved: @Shai yup, you have to change your post to be a Question, then tick "Solved". No permissions necessary to do that. Thanks! I'd often wondered (but not enough to actually figure it out!)

I found that in Thundberbird, if you press Ctrl+K, it will use IMAP search. On Android K-9, there is Settings -> Account Settings -> Search -> Enable server search.

Yes every single text string you see was replaced with translation templates. These were a lot of changes. I've also now made a change to all html files sourcing scripts to bust the cache for new releases. Hopefully it was just a caching related issue and then this shouldn't happen in the future.

@girish I successfully migrated my Cloudron from one server to another. I followed your directions and updated Cloudron to v 6.0.0 before making my final backup of the old server. Thank you.

@necrevistonnezr Don't upgrade yet, I have a blog post that I will publish later today on how to update. It's a bit different than 16 to 18. That main difference is that the mysql server has to be upgraded as well.

I managed to fix that. Will likely only be part of the next patch release though.

@girish it works like a charm, absolutely awsome!

@girish Thank you. I promise you I thought I looked through the docs.

@doodlemania2 assuming it was a reboot that did it. thanks for letting us know.

As I said on the other thread I seem to have managed to install cloudron on Ubuntu 20.04 LTS by following your advice to use ./cloudron-setup --version 5.6.3. I've disabled automatic upgrades and I'll wait a bit to upgrade to version 6. All is good!

Since, we got so many support tickets about this already I will paste what I said in the other thread. Let's Encrypt have started using R3 as the intermediary cert - https://scotthelme.co.uk/lets-encrypts-new-root-and-intermediate-certificates/ . This cert has issuer text slightly different. Since the text has changed, Cloudron tries to renew the certs too early and this results in the above notification. The notification can be ignored since it's a false alarm, the certs and sites will be fine. There are two ways to fix this: Update to Cloudron 6 - you can go to Settings -> Check For Updates and then Update. It will give a notification that it is unstable. It's reasonably safe to update, the notification exists because we roll out updates very slowly to keep support manageable for us. Please expect some downtime (like 10 mins) since the update re-configures all the docker containers. Alternately, you can make this one line change in your current Cloudron version - https://git.cloudron.io/cloudron/box/-/commit/3e62f1913ab05750a343c197c519d38bf17d5b3b . The file is /home/yellowtent/box/src/reverseproxy.js and then systemctl restart box.

I think we won't change the minimum requirement tested for in the cloudron-setup script for now. It seem quite the edge case to have that little storage available, however it is good that we know there is a possible workaround for those cases.

It looks like restarting docker and running configure again did the trick. Fixed!

I will put a cache busting hash for the other toplevel pages in the dashboard, just like we have for the main dashboard. This should mitigate that issue for the next release.

@brutalbirdie Yeah, I tried their Ghost hosting once, until I found how far behind their version updating lagged, which led me to discover Cloudron

@girish feeling lazy, will wait for the official update

@girish Increasing the swap seems to have cured the problem. Additionally, there may have been a problem caused by a misreading of the amount of swap as originally on the Linode it said there was only 512mb but in Cloudron it said there was almost 1GB. I have increased the swap from 512mb to 2048mb and I haven't received any app out of memory notifications since then so that seems to have cured it. Thank you for your help.