in fact in the directory only the dir data is left and it is empty but root:root is the owner [image: 1603584552046-fe2b1d58-3d79-4c28-bc6d-17bc1821095b-image-resized.png] after rmdir /home/yellowtent/appsdata/f266ef68-b01b-4a9e-954e-b8bc68010672/data the uninstallation went well

@girish Thanks so much for the great answers. I look forward to installing the cloudron cli on my computer running Linux Mint .

@ianhyzy Yes, the explanation for this behavior is here - https://docs.cloudron.io/apps/nextcloud/#email (at the bottom). Happy to clarify further.

@girish Looks good now, yeah likely just a Docker hiccup then I guess. Thanks Girish.

@robi The fsmetadata.json is only used in rsync backups. It's used to keep track of empty directories and 'x' bit of files when using rsync mode. We do this because object storage services (like s3, gcs and friends) cannot track this since they are not a filesystem but an object store. This is not needed in tgz because tgz format can encode this information inside the tarball. In essence, fsmetadata.json is usually owned by root. If it's owned by yellowtent, it's probably because maybe you restored the Cloudron in the past or something. The restore logic changes the permission of all files to yellowtent after downloading so that restore can continue as non-root user.

@scooke said in Installation on an AWS EC2 server (T2.Micro) at AWS China hangs: @andreas True, it doesn't matter where the host company, or head office is located. Anything in China, for China, is going to be under lots of scrutiny. Unfortunately true, we must accept this learning curve.

@girish Thank you for your world-class customer support! Sending blessing! ️️

That's not a docker config file with defaults I am looking to change various default parameters like runc, DNS, etc..

I am trying to only do this from the Cloudron hosted versions of Metabase/Grafana. I followed your instructions and this worked perfectly, took the username, password, port, host, and database name from the environment variables within the Wekan web console, entered them in Metabase, and was able to connect and see the data. Thank you!

@mehdi Very much interested in this topic. I love my American friends, but the EU certainly isn't without capability to respond to the data-mining free-for-all antics of the last decade. I share occasional posts on Twitter on these subjects if anyone's interested.

Thanks, fixed.

@girish In my case I was trying to mirror the content of a remote DO object storage to a local Minio instance. I can't recall the exact error but I remember it had to do with the handling of filenames.

@BrutalBirdie Yes ^^

@robi yeah, with ecommerce being our primary business, we're invested in this. We have 12 very experienced devs on the team but just a few of them have had time to start looking at Cloudron this week. In this for the long-term though so I'm sure you'll start to see our work filtering through very soon.

@bossbarnes07 It seems an 'A' record with the subdomain 'my' is missing. It should point to your IP (209.97.x.x). Cloudron should have added this automatically, I wonder why it didn't get added. Can you add an A record manually and then go to your server and do "systemctl restart box". You can then visit https://ip again and re-do the setup.

@girish Sorry for the late reply, I the default forum settings were to send me email notifications once a week, I have changed that to daily. I was trying to use the self-signed certificate for all apps. I have gone ahead and followed the steps in the blog article I linked to and was able to upload the full CA and web server cert chain to Cloudron and after getting the root certificate authority into all the devices accessing Cloudron everything is working well from Windows and iOS based devices. It looks like Apple is going to be decreasing the certificate lifetime further down to 398 days so you may want to lower the lifetime down to a year to get ahead of that change.

As long as the IP doesn't change from my. to mail. no clients need immediate reconfiguration. The Reverse DNS is something that I also wanted to change for vanity reasons, but not at the expense of email. Now I can.

@jdaviescoates said in "subdomain 'selfhost.cloud' is in use": use the File Manager Which is exactly what I did Actually the first time I used to nice new File Manager

@BrutalBirdie I thought of marking as solved but did not find the button. Now I understand why, it's buried somewhere

@girish I don’t think I’ve tampered with anything there, no. Very good, as long as there’s some mechanism to reliably start over I’m happy to do that. Thanks! In the longer term maybe some kind of ”Start over” mechanism doing this same thing can be exposed to the backup page…