I had the same "Authenticated user is not allowed access" error pop up. I read somewhere that once you have 10 domains registered with them the API works again. I already had 9 domains, so I thought what the heck! and I bought another one. Then, the API sharted working again shortly after. I am not happy about this and I don't trust them not to change things again in the long run. But, at least it lets me kick the can down the road until I have time to transfer to a different domain provider.

Thanks - that sounds interesting. Didn't know that - but this is a reason to rethink my approach.

Unfortunately, the backups fail to complete again. I have tried to manually initiate the backup process twice, but each time the backup fails with an error, specifically with the Matrix application. I have no idea what to do. I also tried using a Hetzner box, but the backups take even longer there.

Snímek obrazovky pořízený 2024-05-20 19-23-09.png

@jagadeesh-s2104 said in run out of disk space:

@timconsidine Yes, thank you!

I do that with other VMs. But I remember reading somewhere that we should not do anything with the Cloudron VM.

Yes, generally you don’t need to and shouldn’t do something on the server command line, but I think this is an exception. @staff will jump in here to clarify.

@nebulon I got impatient and wound up just restarting the full cloudron. The app states are now all resolved.

I found the final solution in an old post: https://forum.cloudron.io/topic/9053/app-stuck-in-restarting-after-upgrade-7-4-1/2

This seems to have fixed everything. Thank you for the help everyone!

# rm /home/yellowtent/platformdata/sftp/ssh/ssh_host_rsa_key # rm /home/yellowtent/platformdata/sftp/ssh/ssh_host_rsa_key.pub # systemctl restart box

My backup task crashes sometimes, but not always. It could work fine for a week, and then crash thrice in a row. Absolutely not predictable. I couldn't find any other logs. I am on Ubuntu 22.04 and Cloudron 7.7.2 and do updates regularly. The updates are being done to Backblaze and changing that could probably help, but I was wondering if I could investigate further before changing that. I played a little with the backup settings lowering the part sizes etc., but I can't say for sure if that actually helped as the issue occurs so randomly.

cloudron-support --troubleshoot runs okay and there are no other issues.

Right, that seems to work. Looks like something within infiniteWP is the issue? I will contact their support. I wonder why the loopback check within infiniteWP fails.

@girish on the ubuntu server 22.04?

@nebulon really love you guys for never failing to provide a helpful response, you even have this "rare case" covered in the docs

@girish When the cache is invalid, it causes a runtime error, and the error prevents the refresh button from getting enabled. I'm asking for the refresh button to immediately enable in the handler, so if there is an error in the handler from invalid data, one may still click the refresh button.

@girish said in Dynamic DNS and Mail Server Location:

@gerard that's quite brave to run a mail server with dynamic IP

@girish Yeah it's silly and unreliable 😉 But not meant for any serious usage.

Thank you for fixing it.

Just to further narrow down the issue are all Cloudron users affected by this? If only one user is, maybe something is off with only that?

@rollermy said in Backups:

I'd like to limit app backups to 3 total for the apps i choose.

Maybe create a feature request post about it? 🙂

@milzamsz this happens when you put the bucket name in the Endpoint field . Cloudflare displays the URL with the bucket name in the end. It should be like below. Remove the "/cloudron-backups" (the name of my bucket below) and put it in the bucket name like below:

image.png

@CRBear said in Mail server: IP address verification?:

Am I correct in understanding that the email server checks from which IP address a connection is established to send an email and by default, it verifies against the Spamhaus blacklist?

The mail server does not make any check for outbound email. The various checks you see in the Email Status tab are purely diagnostic. The idea is if one or more checks are failing there, most likely the email won't be delivered.

The Spamhaus is checked for inbound emails though. The DNSBL zone against which it checks is configurable at https://docs.cloudron.io/email/#dnsbl