Here is some update: the mobile app now supports the newest Grocy server version. I tried to get it using the Cloudron Ldap. This doesn't work out of the box but there is a patch waiting to be merged. I applied and tweaked it and can authentication as Cloudron user now.

(I'm thinking about packaging Grocy for Cloudron but might need some help on that ...)

Here it is: https://git.cloudron.io/RoboMod/minio-auto-deleter. If there are any questions, don't hesitate to ask!

I just installed it in a LAMP App. Works great.

The next major release brings LDAP support. I'll try to upgrade soon after next release of the Android app.

Hi Cloudron Team,

thank you for the great feature of letting people now about apps going down via E-mail. It now happened multiple times that this was just a temporary problem and the app was already back online when I checked my mails. So, it would be nice to have a "App XXX is up" or similar E-mail telling me that I don't have to take any action.

Best
RoboMod

@girish @jdaviescoates Yes, it is. But its still not fully compatible to Cloudron. I'll create a patch from my changes, soon.

Hey there, are there any plans to introduce some sort of distribution into Cloudron? I'm thinking of deploying apps to different machines controlled via one interface.

@ApplegateR But that was the version creating the backup. And the docs clearly say that it is required to use the identical version to restore a backup.

@lucidfox It works. But the next major release of Grocy breaks the API so the Android client has to catch up these changes.

Thanks for adding this feature!

Good news: I was able to get one step further! I modified the restore.js (changed "$scope.configureBackup.backupFolder" to "$scope.backupFolder") and now the restore process seems to be running.

Good news: I was able to get one step further! I modified the restore.js (changed "$scope.configureBackup.backupFolder" to "$scope.backupFolder") and now the restore process seems to be running.

@girish Reloading brings me back to the restore page. But I discover something else: watching the browsers consol there came up some errors:

angular.js:13920 TypeError: Cannot read properties of undefined (reading 'backupFolder')
    at $scope.restore (restore.js? [sm]:290:1)
    at fn (eval at compile (angular.js:14817:15), <anonymous>:4:212)
    at b (angular.js:15906:18)
    at e (angular.js:25885:17)
    at b.$eval (angular.js:17682:16)
    at b.$apply (angular.js:17782:20)
    at HTMLFormElement.<anonymous> (angular.js:25890:17)
    at HTMLFormElement.dispatch (jquery.min.js:3:8066)
    at r.handle (jquery.min.js:3:4767)
(anonymous) @ angular.js:13920

DevTools failed to load source map: Could not load content for https://my.xeac.de/3rdparty
/js/showdown.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

DevTools failed to load source map: Could not load content for https://my.xeac.de/3rdparty/js/angular-cookies.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Error: $scope.configureBackup is undefined
$scope.restore@https://my.xeac.de/js/restore.js:290:13
fn@https://my.xeac.de/3rdparty/js/angular.min.js line 233 > Function:4:212
b@https://my.xeac.de/3rdparty/js/angular.min.js:126:128
e@https://my.xeac.de/3rdparty/js/angular.min.js:276:196
$eval@https://my.xeac.de/3rdparty/js/angular.min.js:145:347
$apply@https://my.xeac.de/3rdparty/js/angular.min.js:146:52
Lc[b]</compile/</<@https://my.xeac.de/3rdparty/js/angular.min.js:276:247
dispatch@https://my.xeac.de/3rdparty/js/jquery.min.js:3:8066
add/r.handle@https://my.xeac.de/3rdparty/js/jquery.min.js:3:4767
angular.js:13920:17

From what I see here, I would guess the code behind does not fit the frontend. Any hint on how to solve this?

@ApplegateR But that was the version creating the backup. And the docs clearly say that it is required to use the identical version to restore a backup.

@girish Thats what the logs say:

2022-07-07T19:22:34.807Z box:server ==========================================
2022-07-07T19:22:34.809Z box:server            Cloudron 7.0.4  
2022-07-07T19:22:34.809Z box:server ==========================================
2022-07-07T19:22:34.958Z box:settings initCache: pre-load settings
2022-07-07T19:22:35.006Z box:tasks stopAllTasks: stopping all tasks
2022-07-07T19:22:35.008Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2022-07-07T19:22:35.081Z box:dockerproxy startDockerProxy: started proxy on port 3003
Cloudron is up and running. Logs are at /home/yellowtent/platformdata/logs/box.log
2022-07-07T19:22:35.120Z box:shell addCollectdProfile spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/configurecollectd.sh add cloudron-backup
2022-07-07T19:22:35.149Z box:shell addCollectdProfile (stdout): Restarting collectd

2022-07-07T19:22:35.321Z box:cloudron runStartupTasks: not activated. generating IP based redirection config
2022-07-07T19:22:35.323Z box:reverseproxy writeDefaultConfig: create new cert
Generating a RSA private key
.....+++++
....+++++
writing new private key to '/home/yellowtent/platformdata/nginx/cert/default.key'
-----
2022-07-07T19:22:35.421Z box:reverseproxy writeDefaultConfig: writing configs for endpoint "setup"
2022-07-07T19:22:35.423Z box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
2022-07-07T19:23:42.682Z box:box Received SIGTERM. Shutting down.
2022-07-07T19:23:42.684Z box:tasks stopAllTasks: stopping all tasks
2022-07-07T19:23:42.684Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2022-07-07T19:24:23.735Z box:server ==========================================
2022-07-07T19:24:23.739Z box:server            Cloudron 7.0.4  
2022-07-07T19:24:23.739Z box:server ==========================================
2022-07-07T19:24:23.927Z box:settings initCache: pre-load settings
2022-07-07T19:24:23.988Z box:tasks stopAllTasks: stopping all tasks
2022-07-07T19:24:23.989Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2022-07-07T19:24:24.045Z box:dockerproxy startDockerProxy: started proxy on port 3003
Cloudron is up and running. Logs are at /home/yellowtent/platformdata/logs/box.log
2022-07-07T19:24:24.112Z box:cloudron runStartupTasks: not activated. generating IP based redirection config
2022-07-07T19:24:24.123Z box:reverseproxy writeDefaultConfig: writing configs for endpoint "setup"
2022-07-07T19:24:24.125Z box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
2022-07-07T20:03:28.338Z box:box Received SIGTERM. Shutting down.
2022-07-07T20:03:28.340Z box:tasks stopAllTasks: stopping all tasks
2022-07-07T20:03:28.340Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2022-07-07T20:04:09.527Z box:server ==========================================
2022-07-07T20:04:09.537Z box:server            Cloudron 7.0.4  
2022-07-07T20:04:09.538Z box:server ==========================================
2022-07-07T20:04:09.724Z box:settings initCache: pre-load settings
2022-07-07T20:04:09.785Z box:tasks stopAllTasks: stopping all tasks
2022-07-07T20:04:09.786Z box:shell stopTask spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
2022-07-07T20:04:09.846Z box:dockerproxy startDockerProxy: started proxy on port 3003
Cloudron is up and running. Logs are at /home/yellowtent/platformdata/logs/box.log
2022-07-07T20:04:09.917Z box:cloudron runStartupTasks: not activated. generating IP based redirection config
2022-07-07T20:04:09.928Z box:reverseproxy writeDefaultConfig: writing configs for endpoint "setup"
2022-07-07T20:04:09.930Z box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
Box GET /well-known-handler/nodeinfo 404 Not Found No custom well-known config 7.545 ms - 71
Box GET /api/v1/instance 404   6.108 ms - 154
Box GET /well-known-handler/host-meta 404 Not Found Domain not found 49.745 ms - 60
Box GET /well-known-handler/nodeinfo 404 Not Found No custom well-known config 3.019 ms - 71
Box GET /api/v1/instance 404   2.883 ms - 154
Box GET /well-known-handler/host-meta 404 Not Found Domain not found 6.836 ms - 60

@girish Here is a screenshot of what I get after uploading the background config file and clicking restore:

I tested this with and without "Dry run".

I'm having trouble restoring cloudron from backup.

Today, I setup a fresh installation for cloudron. But at the point of restoring, I end up on screen with a running circle and three dots. I can't see any action on the system, no logs, no changes to files, nothing. What is happing there? I already searched the forum and docs. I fixed the owner of backup files and created a symlink to provide the same path to the backup. Restarting the restore did not changed anything. Can you give me some hint whats going wrong? I'm feeling lost here...

Best
RoboMod

@girish I'm generally looking for a monitoring system. I first thought about Icinga but then realised that Cloudron is using collectd already. So, I don't have a preferred monitoring setup, yet.

Does anyone has experience with monitoring Cloudron, e.q. in a setup with multiple Cloudrons?

Hi there,

would it be possible to somehow use the collectd metrics from outside Cloudron? I would like to add a few more metrics and aggregate them with data of other systems in my network.

Best
RoboMod

@necrevistonnezr Thank you so much! That is actually a great idea!!! I've thought this through and my new plan is a 500 GB SSD for system plus 1 TB HDD for backups.

Well, the thing is I'm using farely limited hardware with only two SATA-Ports. So, adding more space isn't that simple.

Anyone having experience with running Cloudron on a small home server?