I have submitted a PR upstream as a temporary fix - https://github.com/haraka/Haraka/pull/3104

@RazielKanos So 11GB docker is reasonable but the Everything else is almost 46GB. That one is not. Where do you store your backups ? Please note that if you moved to a location outside the server, Cloudron does not delete the previous backups! The default Cloudron backup location is /var/backups . So, you might have to delete the things in /var/backups manually.

@prusaman I have it on my list to test installation against a private zone. Let me get back once I make the changes.

So backups by default would end up in /var/backups unless otherwise configured. It is strongly recommended to use some backup storage, which is not on the same disk. It may be useful to checkout https://docs.cloudron.io/backups/ for more detail. Regarding the Nextcloud instance as such and the error you are facing, I am not sure how your setup now looks like, but is /media/aeternal.cloud some volume you have moved Nextcloud to and if so, is this properly mounted?

@zion I am not sure I fully understand your process there, but generally a disk partition is just a section of a hard drive. That section then has to be formatted with a filesystem, in this case ext4. This can be done via mkfs.ext4 /dev/<you partition identifier>. Once that is done, you should be able to just use the Cloudron dashboard UI to add it then. This makes Cloudron create the mountpoint for you.

@zion you have to ask to set it up to the company that rent you the IPv4/v6. Most likely they have an option on their control panel to do that. If you have ownership of the IP, just do it from Virtualizor, google "Virtualizor ptr" and the first result is https://www.virtualizor.com/docs/admin/configure-reverse-dns/ --> you can do this only if you bought it and the ip is yours

But, woah, diskspace fills up quickly when running a Mastodon server!

@girish Thanks, that works.

@matthewdykstra issue is somewhere on the DNS side. Is that domain using Cloudflare? If so, for a start I would disable Cloudflare proxying for my.mjsiebolt.pro and just make that point to your server (so a single A record). Once that starts working, you can re-enable Cloudflare proxying and see.

@nebulon In which release will this fix be included

@nebulon Thanks guys.

so this should be fixed with the next release now, where we replaced https://www.npmjs.com/package/@sindresorhus/df with our own implementation which calls the df command in a more locale safe way.

@d19dotca ext4 is the filesystem type in this case from your root / partition and ext4 has a feature of reserved blocks for the root user. Other disks may or may not be ext4 like for volumes or backup.

@girish It sure did. I thought it was a simple matter of brute forcing 16 characters. I’m glad that’s not the case. Thanks for the clarification!

@girish with help from vps and hosting it is been solved. thank you for replying here

@YoMaCloud thank you for the correction / update, useful to know.

Not sure why that slipped through. Is this sorted by now? We had a case where slow I/O caused the issue resulting in a timeout. Could this have been the case? https://forum.cloudron.io/topic/4780/postgresql-database-won-t-start/8

@girish said in Incorrect error when removing an obsolete alias for a service: Did you happen to set this up manually? Hmm, I don't actually know. It's not impossible I guess... Good to know though, I'll work on cleaning DNS up

@Jonaz said in You are seeing this page because the DNS record of x.x.x.x is set to this server's IP but Cloudron has no app configured for this domain.: I updated DNS, and my.cloudron works but not cloudron. which is fine with me. Thanx As @subven said, wildcard DNS entry does not include the bare domain. So, you have to put cloudron separately in DNS and not just *.cloudron