@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?

I remember being at the stage you are. Hearing how wonderful the world of Linux is... just run some simple commands and voila! The World At Your Feet. But it ain't working. As long as you don't bother looking up the errors that pop up, none of this will ever make sense and you will continue asking for help when at least the initial problems are clear as day to others. Cannot write to ‘cloudron-setup’ (Permission denied). Start there. In what directory are you? (Whats a directory, you ask... ok, start there then.) What causes "Permission denied" errors? Fix it. You can do it! It's a rewarding adventure!

@d19dotca to be honest, I think can be quite debatable, for example say three apps shape a rough sine curve across the time period, there would not be an easy visual winner. But what is also important here, currently we use what the graph library gives us and reworking this for little value is currently not worth while

@girish got it.. then perhaps use Surfer as the pw protected auth wall and redirect to the app from there via html or js.

I have submitted a PR upstream as a temporary fix - https://github.com/haraka/Haraka/pull/3104

@RazielKanos So 11GB docker is reasonable but the Everything else is almost 46GB. That one is not. Where do you store your backups ? Please note that if you moved to a location outside the server, Cloudron does not delete the previous backups! The default Cloudron backup location is /var/backups . So, you might have to delete the things in /var/backups manually.

@prusaman I have it on my list to test installation against a private zone. Let me get back once I make the changes.

So backups by default would end up in /var/backups unless otherwise configured. It is strongly recommended to use some backup storage, which is not on the same disk. It may be useful to checkout https://docs.cloudron.io/backups/ for more detail. Regarding the Nextcloud instance as such and the error you are facing, I am not sure how your setup now looks like, but is /media/aeternal.cloud some volume you have moved Nextcloud to and if so, is this properly mounted?

@zion I am not sure I fully understand your process there, but generally a disk partition is just a section of a hard drive. That section then has to be formatted with a filesystem, in this case ext4. This can be done via mkfs.ext4 /dev/<you partition identifier>. Once that is done, you should be able to just use the Cloudron dashboard UI to add it then. This makes Cloudron create the mountpoint for you.