Any news on this?
I would also like to se Plausible in Cloudron app store.
They have gained much traction lately and are GDPR compliant which is nice.
I've tried their service and I liked it so now I am looking for self hosting option.
Plausible on Cloudron would be nice.
@nebulon Super! I can confirm that it is back in the store! Thank you 
Any news on this?
I would also like to se Plausible in Cloudron app store.
They have gained much traction lately and are GDPR compliant which is nice.
I've tried their service and I liked it so now I am looking for self hosting option.
Plausible on Cloudron would be nice.
Not sure this is related but I get WOD on one site and login loading "forever" on another.
Mar 08 11:00:17 (/source/database/database.go:439)
Mar 08 11:00:17 [2021-03-08 10:00:17] pq: null value in column "port" violates not-null constraint
Mar 08 11:00:17 ERRO[0000] pq: null value in column "port" violates not-null constraint device="map[arch:amd64 num_cpu:8]" os="map[name:linux]" runtime="map[go_maxprocs:8 go_numcgocalls:1 go_numroutines:14 name:go version:go1.15.6]" type=notifier
I see this error in two installations on different serveres.
Anyone knows what is wrong?
@caleno said in How to authenticate in gitlab pipline?:
I have token auth activated or at least configured and I can still log inn with Cloudron username and password + 2fa.
I'd like the token auth to work via Gitlab and maybe the case above points to a configuration issue.
I have to investigate further.
BTW. Maybe it is just working for the UI.
I have token auth activated or at least configured and I can still log inn with Cloudron username and password + 2fa.
I'd like the token auth to work via Gitlab and maybe the case above points to a configuration issue.
I have to investigate further.
If I understand it correctly the gitlab integration makes gitlab the authority for docker registry submitting jwt tokens for authentication. To create these tokens you either make a access token deploy token or a personal token (especially if you are using 2fa) and one should be able to authenticate to the registry, correct?
I've tried all sorts of tokens and changing the docker-client in authproxy and nginxconfig without success.
Has anyone manged to get this working? ><
@nebulon Super! I can confirm that it is back in the store! Thank you
Hoi!
I can't find the yourls in the app store anymore, is it removed?
Br,
Lennart
When the filsystem backup finally gave up it exited with this error message
Jun 14 11:48:42 node[23567]: box:backups runBackupTask: backup task taking too long. killing
Jun 14 11:48:42 node[23567]: box:shell backup-snapshot/app_928befdc-82c6-4f1e-8947-6bb3424be216 code: EPERM, signal: undefined
Jun 14 11:48:42 node[23567]: box:progress backup: 100 Backuptask crashed
Jun 14 11:48:42 node[23567]: box:apptask s3-oslo.uib.cloud update aborted because backup failed { BackupsError: Backuptask crashed
Jun 14 11:48:42 node[23567]: at /home/yellowtent/box/src/backups.js:487:29
Jun 14 11:48:42 node[23567]: at f (/home/yellowtent/box/node_modules/once/once.js:25:25)
Jun 14 11:48:42 node[23567]: at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)
Jun 14 11:48:42 node[23567]: at emitOne (events.js:116:13)
Jun 14 11:48:42 node[23567]: at ChildProcess.emit (events.js:211:7)
Jun 14 11:48:42 node[23567]: at ChildProcess.kill (internal/child_process.js:395:12)
Jun 14 11:48:42 node[23567]: at Timeout.<anonymous> (/home/yellowtent/box/src/backups.js:503:12)
Jun 14 11:48:42 node[23567]: at ontimeout (timers.js:475:11)
Jun 14 11:48:42 node[23567]: at tryOnTimeout (timers.js:310:5)
Jun 14 11:48:42 node[23567]: at Timer.listOnTimeout (timers.js:270:5)
Jun 14 11:48:42 node[23567]: name: 'BackupsError',
Jun 14 11:48:42 node[23567]: reason: 'internal error',
Jun 14 11:48:42 node[23567]: message: 'Backuptask crashed',
Jun 14 11:48:42 node[23567]: backupError: true }
Jun 14 11:48:42 node[23567]: box:apptask s3-oslo updating app with values: {"installationState":"installed","installationProgress":"","health":null,"updateConfig":null}
Jun 14 11:48:43 node[23567]: box:apptask Apptask completed with error { BackupsError: Backuptask crashed
Jun 14 11:48:43 node[23567]: at /home/yellowtent/box/src/backups.js:487:29
Jun 14 11:48:43 node[23567]: at f (/home/yellowtent/box/node_modules/once/once.js:25:25)
Jun 14 11:48:43 node[23567]: at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9)
Jun 14 11:48:43 node[23567]: at emitOne (events.js:116:13)
Jun 14 11:48:43 node[23567]: at ChildProcess.emit (events.js:211:7)
Jun 14 11:48:43 node[23567]: at ChildProcess.kill (internal/child_process.js:395:12)
Jun 14 11:48:43 node[23567]: at Timeout.<anonymous> (/home/yellowtent/box/src/backups.js:503:12)
Jun 14 11:48:43 node[23567]: at ontimeout (timers.js:475:11)
Jun 14 11:48:43 node[23567]: at tryOnTimeout (timers.js:310:5)
Jun 14 11:48:43 node[23567]: at Timer.listOnTimeout (timers.js:270:5)
Jun 14 11:48:43 node[23567]: name: 'BackupsError',
Jun 14 11:48:43 node[23567]: reason: 'internal error',
Jun 14 11:48:43 node[23567]: message: 'Backuptask crashed',
Jun 14 11:48:43 node[23567]: backupError: true }
Jun 14 11:48:43 node[23567]: box:apptask Apptask completed for 928befdc-82c6-4f1e-8947-6bb3424be216
Jun 14 11:48:43 node[23567]: box:taskmanager Task for 928befdc-82c6-4f1e-8947-6bb3424be216 pid 1331 completed with status 50