@girish Will changing to another account remove the previous account deployment?

@JOduMonT you're right. "official" was the wrong wording. What I meant was use is to use the notes functionality of Nextcloud and then use an app on ios that is designed to sync with it. Which honestly is a bit of a pity since most note sync applications are markdown or plaintext, while systems like Apple Notes and Microsoft Onenote allow for more functionality (multimedia, cross application integration and stylus support).

@therealwebmaster https://aws.amazon.com/premiumsupport/knowledge-center/ec2-launch-issue/ is another idea to cleanup the disk. But otherwise, do you have external Cloudron backups? It's quite easy to recover from cloudron backups - see https://docs.cloudron.io/backups/#restore-cloudron .

@krishnav Is https://aws.amazon.com/elasticloadbalancing/ the product you are referring to? Can you post a screenshot of how you have configured the load balancer? And where are you seeing this error message? Also, any reason to use this load balancer?

https://forum.cloudron.io/topic/7193/unable-to-install-cloudron/3?_=1654970145198. Please help me with this topic. A bit similar to this topic.

So I tried mounting the folder from the Synology NAS and then the storagebox again and everything is working fine. I have misnamed the remote directory. Sorry for the unnecessary topic.

You can find the referenced documentation for the docker addon at https://docs.cloudron.io/packaging/addons/#docker nowadays.

Just noticed the following in the 7.2.4 changelog 🥳 initial xfs support

@BrutalBirdie I did also check but I think I'm at 60% of capacity.

@girish Ah, thank you. Found them. That freed up 22GB for me

@girish wait ... true [image: 1654545805187-6a136902-e13f-47d9-b8be-68193a8688b4-image.png]

Hardened node developer here : long story short, nothing to worry about. NPM security warnings are completely broken, they have a near 100% false positive rate (technically, the "vulnerable" dependency is here, but the flaw is, in literally all instances I have seen, not exploitable). An interesting read about this if you want : https://overreacted.io/npm-audit-broken-by-design/

@girish perfect - that fixed that! now bumping to 7.2 - thanks mate

Also, please check if your router supports hairpinning https://en.wikipedia.org/wiki/Network_address_translation#NAT_loopback . This is what loops back a request to a public IP back into your private network.

@nebulon hey there, thanks for your reply, cloudron works now for me. maybe it was a dns propagation issue

@girish Oh, never mind, it was an SMTP OUT block by the VPS provider... I didn't think that it would apply to running email from another server through OpenVPN on this one... Sorry for taking your time with this, and thanks again.

@girish So I disabled the port forward rule in my router and it resolved the issue. Thank you!

@humptydumpty Err, I forgot that I already removed those last week as well - https://git.cloudron.io/cloudron/dashboard/-/commit/72ba61ad91d326c3f287a2f538809cc78afcfdc8 . So, this should be fixed in next release.

@adhithiyan I thought I fixed this in 7.2.2 . collectd has an option to disable FQDNLookup. Can you tell me which version of Cloudron you installed ? If you don't remember, you can check the file /home/yellowtent/box/VERSION. It's also in the Settings page of the dashboard (this appears only after you have setup cloudron).