@luckow yes, good catch! fixed now. will be in 6.3.5

@nebulon Oh yeah, I had not thought to try the right-click, good catch. Right-clicking on a webpage never feels intuitive to me, except when I want the browser's context menu

hey @nebulon, no, only 2-3 ports tcp/udp (wireguard/snmp/ssh) and it happened inbetween again, without any reboots/upgrades/etc. I got notfied by network mgmgt system, that my cloudron server is down - luckily it was just the firewall…

@girish That did it! You are awesome! Thank you for all your help from a -1 rep person :). Thank you and the cloudron team for all you do in helping us newbies. (had to wait 3 minutes)

@girish HAH nevermind. Its me being a Linux noob... turns out I mounted the drive itself not the partition. The files are there.

@girish I use DBeaver with an SSH tunnel. I just found an option that I forgot to toggle on -- "Show all databases". Now it shows all the databases! On a side note, I did first try to configure an SSH tunnel and a post-command to execute "/usr/local/bin/docker exec -ti postgresql bash" and that worked as well. But, only one tunnel is needed to the cloudron server to login as root that allows access to all databases. I'm good to go. Thanks for the help!

@d19dotca Ah good point about editing those files. In the next release, I am hoping to make the filemanager be able to edit mail data (so admins can setup sieve rules etc for a mailbox), so this will atleast partly fix that issue.

Not 100% sure but are there any files under /home/yellowtent/boxdata/mail/spamd/<mailboxname> ? Those are the per mailbox spamassassin bayes databases. Maybe it's picking up something from there?

Good notes to follow up when we look into email in the next release. IIRC, whitelist setting is a bit dangerous because it allows "spoofed" emails as it pretty much bypasses all the SPF/DMARC/DKIM checks. Meaning, Cloudron does not reject mail if those checks do not pass because there are too many misconfigured mail servers out there. Instead we tag the failures and allow spamassassin to score the rules. whitelisting makes spamassassin bypass the checks altogether.

@americankulak Ah! thanks for the update.

Ok, I will mark this as solved but let's investigate further if this comes up again. FWIW, if you do docker exec -ti mysql /bin/bash then the details mysql logs are located at /tmp/mysqld.err .

This should work now.

@thetomester13 I came across this question after recently installing on Oracle Cloud, and thought I ought to put something in for the argument. I put in "OCI", saw it had been written to a file somewhere, but apart from that it all just worked so I forgot about it!

@msbt thanks! I will try to see if I can make this just "work" in the next release.

@qimmiq Great! Imma gonna uninstall that Discourse ram hog now!

@nebulon

@lg2_soft ah, it could be you are in a pretty old version of cloudron. The current version is 6.3

Just had a read over this support ticket: https://forum.cloudron.io/topic/5272/backup-size-growing/ should have added to this rather then create a new topic. I'm assuming once changing the lifecycle setting, an almost full reset of the bucket will be required as the 'Delete' function of Cloudron won't run correctly?

@d19dotca Also, it's probably not clear from the UI because the UI is not optimized for the early upgraders. You can see https://git.cloudron.io/cloudron/box/-/blob/master/CHANGES for what exactly is the fix in the patch release.