@girish I think this is what you are or was looking for
caleno
Posts
-
Community support for Humhub -
Custom app install complains about subdomainUpdated cloudron cli, or so I thought. Running in WSL
Anyways, I mange to update cloudron cli and now it dont complain about subdomains.
-
Custom app install complains about subdomainIt seems the same happens for appstore apps
cloudron install --appstore-id com.documize.cloudronapp?version=0.6.0 -l sub.domain.com
Failed to install app: 400 message: subdomain is required
-
Custom app install complains about subdomainHey,
I am trying to install a custom app but I get an error.
Failed to install app: 400 message: subdomain is required
I get this even if I provide subdomain, and domain resolves to cloduron server.
Thanks for any insights to why this is happening.
-
Changed app to use bare domain, stuck Waiting for DNS propagation@girish No I've not patched manually, I have assumed sorry
I assumed the latest update was with the CNAME/A-record fix was live.The thing was that my home server has been offline for a while and when I started it up it updated to from v7.0.4 to v7.1.3 then v7.1.3 to v7.1.4.
After that the DNS propagation didnt work any longer, as it had done before.
-
Changed app to use bare domain, stuck Waiting for DNS propagation@girish After update I get error when propagating DNS. Or at least I thinks it is related because it worked before.
It is a subdomain pointing to a CNAME (duckdns) and it complains on all nsX.hyp.net.
Apr 09 11:33:38 box:dns/waitfordns resolveIp: Checking if xxx has A record at xxxx Apr 09 11:33:38 box:dns/waitfordns resolveIp: Checking if xxx has CNAME record at xxxx Apr 09 11:33:38 box:dns/waitfordns resolveIp: Resolving xxx CNAME record xxx Apr 09 11:33:38 box:dns/waitfordns isChangeSynced: NS ns1.hyp.net (151.249.124.1) errored when resolve xxx (A): Error: queryA EREFUSED xxx Apr 09 11:33:38 box:dns/waitfordns waitForDns: xxx at ns ns1.hyp.net: not done Apr 09 11:33:38 box:dns/waitfordns Attempt 7 failed. Will retry: ETRYAGAIN
Final error message
An error occurred during the install operation: DNS Error: DNS A Record is not synced yet: ETRYAGAIN
-
Plausible (Analytics Platform)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.
-
pq: null value in column "port" violates not-null constraintNot sure this is related but I get WOD on one site and login loading "forever" on another.
-
pq: null value in column "port" violates not-null constraintMar 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?
-
How to authenticate in gitlab pipline?@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.
-
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.
-
How to authenticate in gitlab pipline?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? ><
-
App removed from store?@nebulon Super! I can confirm that it is back in the store! Thank you
-
App removed from store?Hoi!
I can't find the yourls in the app store anymore, is it removed?
Br,
Lennart -
Can't backup/update Minio@girish no
-
Can't backup/update MinioWhen 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
-
Can't backup/update MinioFore some reason it is not possible to backup Minio app to another Minio app.
The backup/update process starts then stalls and eventually, after 4 hours, it crashes and spits out the error message below.(Hovering hover this app tells me that it is making a backup.)
Jun 13 11:44:23 node[23567]: box:backups runBackupTask: backup task taking too long. killing Jun 13 11:44:23 node[23567]: box:shell backup-snapshot/app_928befdc-82c6-4f1e-8947-6bb3424be216 code: EPERM, signal: undefined Jun 13 11:44:23 node[23567]: box:progress backup: 100 Backuptask crashed Jun 13 11:44:23 node[23567]: box:apptask s3.app error backing up app: BackupsError: Backuptask crashed Jun 13 11:44:23 node[23567]: box:apptask s3.app updating app with values: {"installationState":"installed","installationProgress":"Backuptask crashed"} Jun 13 11:44:24 node[23567]: box:apptask Apptask completed with error { BackupsError: Backuptask crashed Jun 13 11:44:24 node[23567]: at /home/yellowtent/box/src/backups.js:487:29 Jun 13 11:44:24 node[23567]: at f (/home/yellowtent/box/node_modules/once/once.js:25:25) Jun 13 11:44:24 node[23567]: at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:69:9) Jun 13 11:44:24 node[23567]: at emitOne (events.js:116:13) Jun 13 11:44:24 node[23567]: at ChildProcess.emit (events.js:211:7) Jun 13 11:44:24 node[23567]: at ChildProcess.kill (internal/child_process.js:395:12) Jun 13 11:44:24 node[23567]: at Timeout.<anonymous> (/home/yellowtent/box/src/backups.js:503:12) Jun 13 11:44:24 node[23567]: at ontimeout (timers.js:475:11) Jun 13 11:44:24 node[23567]: at tryOnTimeout (timers.js:310:5) Jun 13 11:44:24 node[23567]: at Timer.listOnTimeout (timers.js:270:5) Jun 13 11:44:24 node[23567]: name: 'BackupsError', Jun 13 11:44:24 node[23567]: reason: 'internal error', Jun 13 11:44:24 node[23567]: message: 'Backuptask crashed' } Jun 13 11:44:24 node[23567]: box:apptask Apptask completed for 928befdc-82c6-4f1e-8947-6bb3424be216 Jun 13 11:44:24 node[23567]: box:taskmanager Task for 928befdc-82c6-4f1e-8947-6bb3424be216 pid 27623 completed with status 50
Even if I change backup to local filesystem the Minio app won't be backed up nor updated.
I started an update yesterday at ~1245 and today at 07:30 it is still "updating".How can I debug this? Which logs should I parse? How do I stop a backup job?
Error message from daily backups when Minio daily backups are enabled
{ stack: 'BackupsError: Backuptask crashed\n at /home/yellowtent/box/src/backups.js:487:29\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:64:9)\n at emitTwo (events.js:126:13)\n at ChildProcess.emit (events.js:214:7)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)', name: 'BackupsError', reason: 'internal error', message: 'Backuptask crashed' }
-
Free PlanVery good! Thanks