Welp... I followed a few other posts about email not working, and found a file in the mail queue, removed it, restarted the mail... and now it works. I might delete all this... but I might leave it up as a suggestion to anyone else to do the same. At the very least, try restarting mail in the Dashboard.

Ok, thanks! Then we've to implement the whole deploy process inside the container (lamp app) and leave the host untouched. Wish you a nice weekend ️

@mdc773 said in Backups: @jdaviescoates so i am backing up from cloudron to my R2 Cloudflare Where is your Cloudron hosted? (which company and where physically) Where physically is your R2 Cloudflare?

Yes I think so can confirm it works thank you. [image: 1684921191514-9b24435c-6125-4a47-8604-b2257673828e-image-resized.png]

@aestela Atleast, the very first post was rejected because it only said "I am facing same problem" or something like that. We rejected it thinking this was spam. Pretty much all the bots now post generic messages like this. I will reply to your other post. (If you are not happy with the support, of course, just write to support@cloudron.io and we can refund as needed).

i have sent a mail

@girish I just wanted to say thank you for your help two weeks ago! I didn't get Postgres running because of too little storage on the disk, so I had no idea in this short time how to delete the things out of Postgres. For us this issue was very critical and I had to fix it very fast and so I just deleted the dump file which means the loss of the directus instance data, but that was okay in this case. Again: thank you very much and best regards!

Thank you. Good idea! I ran traceroute and discovered that example.com resolved to the IP of an old server I once used. Checking my registrar, I found that I had left example.com and www.example.com resolving to that old server's IP. Deleting those entries has resolved the issue. When I check example.com it shows the expected "You are seeing this page because the DNS record of example.com is set to this server's IP but Cloudron has no app configured for this domain." Thank you for your help!

Ok. I will doublecheck this. Give me a few hours for this. Thanks for the moment Update: Solution work fine! Thanks a lot.

@Stardenver Depends on how you use the volume. If you use the volume to store the app's data using data directory , then it's part of backup If you set it up as a mount of the app, then it's not.

redis logs are of the format pid:role timestamp loglevel message . pid is container local. Role is: X sentinel C RDB/AOF writing child S slave M master Unfortunately, there is no way to change the log format in redis (afaik). We just need the message really (others are not useful on Cloudron). See also https://github.com/redis/redis/issues/2545

@Stardenver said in Identify whats causing lags: So the graph showing 200% is 2 cores on 100% each (or something equal like 4 cores on 50% each)? The latter is more probable. If you really want to know, run 'htop' from the command line.

@oj right, best to have another domain added on Cloudron, so you can change things quickly if required. I wasn't aware of all the recent changes, I have to read up. My primary domain is .in ccTld .

Spam filters don't block delivery status messages as they're needed for troubleshooting. If someone else decided to use your address as the From: to spam, there isn't much you can do to stop it, only deal with it (filtering, etc) or turn off delivery to that address until the campaign is over. Forged source headers will always bounce to the source, and yours happens to be deliverable. Sorry.

@nebulon said in Cloudron CLI: ah. The cli is actually not built to run on Cloudron itself, but it would interact with a Cloudron via REST api. Is there a specific use-case where you need it on the server? I want to install the InfluxDB Package, I thought then via Cloudron CLI. So I have to install it on my Client, to install this package.