Cloudron Forum

Hi everybody,

yesterday, I installed JupyterHub and was so amazed by the smooth process. Now, I have some Notebook it'd like to save in a Git repository. As I already host Gitea on the same Cloudron instance, I would love to put it there. Unfortunately, I can't do a pull from there. Everytime I try, the answer is a "fatal: Authentication failed" (using the console in Jupyter and having set the remote repository to https://<url>/<user>/<repo>.git).

Has anyone seen something like this? My guess is that the problem has something to do with the SSO.

Best
RoboMod

Ah, sorry. That was my mistake. The update worked now (maybe after upgrade Cloudron to 8.0.3). Now the app is running version 4.0.0-1.

After updating a LAMP-App from 3.4.0 to 3.4.2 I got following error:

Docker Error: (HTTP code 500) server error - error creating overlay mount to /var/lib/docker/overlay2/dc16f22fedeaa91656319a27dff3b1878b7de4796f56881cc983f951c69435a4-init/merged: too many levels of symbolic links

Repeating the update task did not solve the problem.
Can you help me?

@girish That works great! Many many thanks for you prompt support!

@girish Yes, exactly. I think the necessary modules would be:

LoadModule ldap_module /path/to/mod_ldap.so
LoadModule authnz_ldap_module /path/to/mod_authnz_ldap.so

But I'm not 100% sure

@girish Wuhu! Thats nice. Would you be willing to activate it in the next release or so? (I'm not sure which modules it would require exactly. But I could search them.)

Hi there. I would like to use a .htaccess Protection in combination with the Cloudron LDAP. If I didn't miss it, the necessary modules are not loaded by the Apache config of the LAMP app. Would it be possible to active them?

Best
RoboMod

@andreasdueren Did you fix that in the meantime? (Sorry for not reacting )

@humptydumpty Sound like a path issue. All the folders and files for Grocy are in the "home" folder of the LAMP app. Hence, the "vendor" folder is also in the "home" folder so that the "app.php" can successfully load the path "/vendor/autoload.php". Does that help?

+1

There is already a Docker packaged version mentioned on that page.

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?