Neat.

They'd look better on a dark background 😉

@subtlecourage this sounds like a config issue you need to adjust, not keys or users.

@nebulon Yes, I have.

It looks like this to me.

ba1c540a-d551-4941-aba9-515457ecf4cb-image.png

@d19dotca sounds like a good idea, i made a task - https://git.cloudron.io/cloudron/box/-/issues/783

@nebulon I could enable ssh on the cloudrons in question and you could take a look, should I do that and write down some timestamps of the restarts? maybe you see something that I don't, email is not my strongsuit and there is a lot happening that I don't know 😉

@subtlecourage Let me know what you think of those logs

@nebulon Thanks for the reply. Unfortunately that didn't help. The server has also been rebooted several times since first trying to uninstall.

May 16 14:48:13 box:settings initCache: pre-load settings May 16 14:48:13 box:taskworker Starting task 638. Logs are at /home/yellowtent/platformdata/logs/6287dbc7-a16c-4930-85d3-2dc713f3e83e/apptask.log May 16 14:48:13 box:tasks 638: {"percent":2,"error":null} May 16 14:48:13 box:apptask zulip.xx.com startTask installationState: pending_uninstall runState: running May 16 14:48:13 box:tasks 638: {"percent":20,"message":"Deleting container"} May 16 14:48:13 box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx May 16 14:48:14 box:apptask zulip.xx.com deleting app containers (app, scheduler) May 16 14:48:14 box:shell removeCollectdProfile spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/configurecollectd.sh remove 6287dbc7-a16c-4930-85d3-2dc713f3e83e May 16 14:48:14 box:shell removeCollectdProfile (stdout): Restarting collectd May 16 14:48:14 box:shell removeCollectdProfile (stdout): Removing collectd stats of 6287dbc7-a16c-4930-85d3-2dc713f3e83e May 16 14:48:14 box:shell removeLogrotateConfig spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/configurelogrotate.sh remove 6287dbc7-a16c-4930-85d3-2dc713f3e83e May 16 14:48:14 box:apptask zulip.xx.com updating app with values: {"containerId":null} May 16 14:48:14 box:tasks 638: {"percent":30,"message":"Teardown addons"} May 16 14:48:14 box:services zulip.xx.com teardownAddons: Tearing down ["localstorage","redis","postgresql"] May 16 14:48:14 box:services zulip.xx.com Tearing down addon localstorage with options {} May 16 14:48:14 box:services zulip.xx.com teardownLocalStorage May 16 14:48:14 box:services zulip.xx.com Tearing down addon redis with options {} May 16 14:48:14 box:shell removeVolume spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/rmaddondir.sh redis 6287dbc7-a16c-4930-85d3-2dc713f3e83e May 16 14:48:14 box:services zulip.xx.com Tearing down addon postgresql with options {} May 16 14:48:14 box:tasks 638: {"percent":40,"message":"Cleanup file manager"} May 16 14:48:14 box:tasks 638: {"percent":50,"message":"Deleting app data directory"} May 16 14:48:14 box:tasks 638: {"percent":60,"message":"Deleting image"} May 16 14:48:14 box:docker Error removing image https://hub.docker.com/r/zulip/docker-zulip : {"statusCode":301,"json":{"type":"Buffer","data":[]}} May 16 14:48:14 box:apptask zulip.xx.com error uninstalling app: BoxError: (HTTP code 301) unexpected - at Object.callback (/home/yellowtent/box/src/docker.js:591:29) at /home/yellowtent/box/node_modules/dockerode/lib/image.js:269:12 at /home/yellowtent/box/node_modules/docker-modem/lib/modem.js:309:7 at getCause (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:331:7) at Modem.buildPayload (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:300:5) at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:275:14) at IncomingMessage.emit (events.js:327:22) at endReadableNT (internal/streams/readable.js:1327:12) at processTicksAndRejections (internal/process/task_queues.js:80:21) { reason: 'Docker Error', details: [Object], nestedError: [Error] May 16 14:48:14 box:apptask zulip.xx.com updating app with values: {"installationState":"error","error":{"message":"(HTTP code 301) unexpected - ","statusCode":301,"json":{"type":"Buffer","data":[]},"taskId":"638","installationState":"pending_uninstall"}} May 16 14:48:14 box:taskworker Task took 1.128 seconds May 16 14:48:14 box:tasks setCompleted - 638: {"result":null,"error":{"stack":"BoxError: (HTTP code 301) unexpected - \n at Object.callback (/home/yellowtent/box/src/docker.js:591:29)\n at /home/yellowtent/box/node_modules/dockerode/lib/image.js:269:12\n at /home/yellowtent/box/node_modules/docker-modem/lib/modem.js:309:7\n at getCause (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:331:7)\n at Modem.buildPayload (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:300:5)\n at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:275:14)\n at IncomingMessage.emit (events.js:327:22)\n at endReadableNT (internal/streams/readable.js:1327:12)\n at processTicksAndRejections (internal/process/task_queues.js:80:21)","name":"BoxError","reason":"Docker Error","details":{},"message":"(HTTP code 301) unexpected - ","nestedError":{"stack":"Error: (HTTP code 301) unexpected - \n at /home/yellowtent/box/node_modules/docker-modem/lib/modem.js:301:17\n at getCause (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:331:7)\n at Modem.buildPayload (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:300:5)\n at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:275:14)\n at IncomingMessage.emit (events.js:327:22)\n at endReadableNT (internal/streams/readable.js:1327:12)\n at processTicksAndRejections (internal/process/task_queues.js:80:21)","name":"Error","message":"(HTTP code 301) unexpected - "}}} May 16 14:48:14 box:tasks 638: {"percent":100,"result":null,"error":{"stack":"BoxError: (HTTP code 301) unexpected - \n at Object.callback (/home/yellowtent/box/src/docker.js:591:29)\n at /home/yellowtent/box/node_modules/dockerode/lib/image.js:269:12\n at /home/yellowtent/box/node_modules/docker-modem/lib/modem.js:309:7\n at getCause (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:331:7)\n at Modem.buildPayload (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:300:5)\n at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:275:14)\n at IncomingMessage.emit (events.js:327:22)\n at endReadableNT (internal/streams/readable.js:1327:12)\n at processTicksAndRejections (internal/process/task_queues.js:80:21)","name":"BoxError","reason":"Docker Error","details":{},"message":"(HTTP code 301) unexpected - ","nestedError":{"stack":"Error: (HTTP code 301) unexpected - \n at /home/yellowtent/box/node_modules/docker-modem/lib/modem.js:301:17\n at getCause (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:331:7)\n at Modem.buildPayload (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:300:5)\n at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:275:14)\n at IncomingMessage.emit (events.js:327:22)\n at endReadableNT (internal/streams/readable.js:1327:12)\n at processTicksAndRejections (internal/process/task_queues.js:80:21)","name":"Error","message":"(HTTP code 301) unexpected - "}}}

@jlx89 I can see that feature being useful to have a proper overview of archived apps, rather than trying to workaround with existing paradigms. Stopping the app would keep the allocated resources like domain and ports bound to this instance as well. Depending on the use-case this may be good or bad. Generally I think you can achieve that already by keeping a copy of the apps last backup around on some other storage (this is quite easy with tarball backend)

Maybe we add some UI for this later, but this is not on our feature list for next release at least, so we can explore this first a bit further here, so any input is welcome.

@robi That's the icon!

i am no dev, but as a common user i am looking forward to see this happen!! 🙂 keep as posted!

@jdaviescoates jealous ! but good to know 👍
I will crack on. Has to be resolvable.

@necrevistonnezr you can delete those files safely, of course you will lose all logs history, but if you don't have any immediate issue on your server besides log size, you can just remove them via ssh.

@moocloud_matt oh I see. Perfect yeah I have no problems waiting, thanks!

@girish Just wondering if there is any update on the thinking about this ? or if anyone else has self-packaged GrapesJS for cloudron ?

@nebulon thanks. works like a charm now.

@girish I'm not sure if that makes complete sense to me yet, but as always I appreciate the detailed explanation.

I can understand that Cloudron is checking to make sure an app hostname can be resolved, but I'd think it just needs to do a DNS lookup to make sure it can resolve the hostname of the app, then proceed forward. I don't quite understand why it care about the name server side of things. As long as the app hostnames are resolvable, shouldn't that be sufficient?

In my case, the IP isn't changing, nothing is changing other than I want to use DigitalOcean DNS whereas I currently use a Wildcard DNS backend. Everything is already working as-is and has been for quite some time. I should be able to link Cloudron up to DigitalOcean's DNS API to generate all the required DNS entries in the new service provider before needing to change name servers.

If Cloudron's main focus is to make sure the app "can be accessed via the browser immediately", then it should just need to care if the hostname is currently resolvable, right?

The best practice would be to switch name servers last when switching DNS providers for a domain, and the way Cloudron seems to currently work I cannot have Cloudron setup the new DNS service ahead of time before switching the name servers since it requires the name servers set first, which seems a bit backwards to me. Part of the beauty of that function is that Cloudron sets the DNS entries is automation, but this current behaviour is now requiring manual steps which seem unnecessary.

I guess the process just seems "off" to me, or rather backwards from how I'd think it should operate to achieve best practices and convenience to users.

@girish If something happened in the past (like the cifs mount being down) that caused the previous backups not to be deleted would there be any log on the system I could look through to see an error?

In the mean time I will manually delete everything not listed in the log output above and then report back in 7 days.

@jdaviescoates, I have been having problems with the backups being deleted automatically for 3+ months and have been trying different things and have several times moved the backups out of the directory they were in, deleted everything from cloudron, unconfigured the backups, and reconfigured them again, ran them for more than 7 days, confirmed that they still were not being cleaned up properly, rinse and repeat with different configurations and options.

I opened this support thread after reaching what I believe to be a correct/supported configuration that started fresh that has been running for longer than 12 days (with a 7 day retention period) with no prior backups in the directory and confirming that the issue is still occurring.

@d19dotca Swift based object stores are one of the least advanced.

IBMs is one of the most. (20GB free)

Brilliant!

For interest EspoCRM has this as a feature, and I prefer now as a business email client.

@rmdes try the same on my instance? up dot toldyouso dot com.

@jdaviescoates said in Jami:

Looking at this again, I don't think there is actually a web app nor any server components. It's all just desktop and mobile apps that communicate directly with each other, so I don't think it could really be an app on Cloudron.

Saying that, "JAMS - Jami Account Management Server" (as mentioned by @stoccafisso ) does sound very much like it's a server thing! So I guess that could be a Cloudron app?

@rmdes on the managed app, you cannot update WP. It will behave similar to what you faced i.e it will ask for credentials. This is because WP figures that it cannot write to the code directory and falls back to uploading code via FTP (a behavior I really dislike but I don't think this can be disabled).

@girish that's a great idea! I like the proxyAuth because it limits the number of credentials one needs to access their apps, but you're right in the way that it ends being less secure since you might end up using it in other places that might not be as secure.

I'll play around with the built-in auth!