@girish I can confirm. I had "Error : Task Error - Task 4237 stopped" and I did what you said, and it restore from backup normally. All my updates were stuck with the same error. Coincidentally, Contabo was having maintenance before, and every time they did a repair Cloudron acted a bit weird. I suspect it might have to do with the server hosting...

Hi there, I just double checked our support spam folder there and I can't find any related mails. Do you get bounces when sending mails? For your initial issue, you can also send a mail to sales@cloudron.io directly with your two email addresses used for those subscriptions, I should then be able to refund accordingly. Please also let us know if and which subscription you want to keep.

@jdaviescoates The first one is from redis, it can be ignored. The second is the healtheck bot. It appears when the app is not up yet. That can be ignored as well. The final one is because the apache config has ServerName unset. Which app is this? Setting the ServerName to some dummy name makes it go away.

@stvslkt What is the endpoint URL you are entering? It should be like https://s3.us-west-002.backblazeb2.com or just s3.us-west-002.backblazeb2.com.

@SirFiChi said in Server not available after reboot: I hope my system has now no lasting damage by apt-get update/upgrade/dist-upgrade and "apt autoremove". I hope so too but to be sure you can make a backup and restore on a fresh and clean installed Ubuntu 20.04 (or whatever you're currently using). Just make sure to restore to the same OS and Cloudron version and you should be fine. There are also guides what to do after a (planned) dist-upgrade so maybe check them out.

@girish Thank you! I really appreciate all the work you folks do and how much of user whishes you try to fulfill. This is something other vendors could take as example

@girish Hopefully that's coming out before the weekend here for beta, it's been a long time coming, been waiting for those fixes for a while now.

You can read more here - https://support.cloudflare.com/hc/en-us/articles/115000219871-Troubleshooting-redirect-loop-errors-

@nebulon thanks

This is already fixed in the upcoming patch release.

Thanks, it works.

@girish Not a problem

Have you seen https://docs.cloudron.io/troubleshooting/#recovery-after-disk-full with steps to bring a system back from such a disk full event? Regarding Nextcloud, you should be able to restore it to the previous version then.

@girish Yes, looks like it

@madmaneighteen can you share a bit more about your environment? Also when the routing and possible portforwarding are correctly setup, you should hit nginx on your Cloudron there, so for a start check if nginx is running in your Cloudron server systemctl status nginx and also maybe try to curl localhost within the server to ensure nginx is also responding correctly there at least.

Cloudron won’t skip an update and will install them per your defined schedule. I have a shut down Wordpress app but temporarily keeping it for archiving purposes and I had to update it several times to get to the latest. I know from experience that WP won’t play nice if you skip updates (especially major version ones).

@nebulon Yeah I did. Forgot to mention it here. Thank you @girish !!

@girish sorry, a school boy mistake, the Content-Type header did the trick, but I made a typo in the backupId, that's why I got the error.

@nebulon said in App Store "New Apps" tab broken: This should be fixed now. restore?