This is a known issue - https://forum.cloudron.io/topic/8149/can-t-manage-existing-email-address-since-v7-3-4-update . It's getting fixed for 7.3.5. As @subven said, the issue is related to getting the mailbox sizes. It takes a bit of time to get that information since we get it via dovecot . So, nginx -> box code -> mail server -> dovecot and all the way back.

The crash is fixed with https://git.cloudron.io/cloudron/box/-/commit/41b03e3fefca5559c6db58a29399d97ae312a4f3 for the next release.

@jdaviescoates you could set up a cron that gets usage info, and prints out a webpage you can monitor with Kuma for a keyword. When a threshold is met, you add/remove the keyword and fire off an alert via TG.

Similar for monitoring something with change detection app or n8n workflow.

@jjhill Can you check if nginx is running ? See https://docs.cloudron.io/troubleshooting/

i Had the same issue... but still works at ubuntu 20.04

You made the right decision, because using SSDs is a more productive solution than outdated HDDs. Especially since now you can find not new form factors, such as mSATA SSDs, which will be inexpensive. For example, the ROGOB 2TB mSATA SSD will cost you only $119. I think this is a fairly reasonable price.

@pbischoff thanks, I have fixed the link.

Hi, brilliant - that was the solution

thank you so much
kr, Andreas

@girish said in Forgot primary domain:

cloudron-support --admin-login

@nebulon I haven't investigate but certainly some extension that blocked the ability to write there.

@nebulon Thank you!

@nebulon said in Cloudron dashboard not loading after reboot after NextCloud "not responding":

Most likely you are hitting an unbound issue then. Checkout the unbound section at https://docs.cloudron.io/troubleshooting/

Unbound solved my issues, thank you! 🙂

Thanks for the reply @MooCloud_Matt!

Proxmox is set to bridge and works with ipv4 without any problem.

But the problem is probably elsewhere, I tried opening the ipv6 test page on my laptop and it said my provider doesn't support ipv6, which is bullshit. I actually have two public ipv6s assigned from it.

So I would need to somehow run the installation with only ipv4, is it possible to do that?

alt text

You can try ping6 ipv6.api.cloudron.io and see if that works. Without it, IPv6 won't work.

@girish well, that solved the problem i was facing, though i do not understand why it does, but anyway, thanks a lot that helped me 😌 ✌

Solved!!
Solution = <Just sign in to the app store in your Cloudron Server as Mr. @girish said>

Once more, thank you very much for the support 😃 .

@3246 I think this is a known problem for people how have CIF/SSHFS/possible other mounts which is already fixed in the next version.

@girish said in Cloudron 7.3.2: "Analyze Disk" doesn't do anything:

OK, I have fixed this now. The code is was not handling CIFS/SSHFS volumes correctly.

@girish said in Cloudron 7.3.4: "Analyze Disk" doesn't do anything and no statistics shown...:

Thanks all. This issue was already fixed as well last month - https://git.cloudron.io/cloudron/box/-/commit/67cde5a62cf0394c8bf2d78ee3408e5995a220e7 . It's already in 7.3.5.

Essentially, if you have CIFS/NFS/SSHFS, there is a crash.

@girish awesome! I think what would be helpful is to test the parameters before pressing 'restore', just to validate that both the connection and decryption keys are OK.

I found the error messages we have right where more confusing than helpful. I don't really know what I did wrong because to resolve it, I just took a fresh backup and restored it using the same details.

All good now though.

@girish Thank you for the reply, that's good to know!

@girish since it worked with my other NAS, I am pretty confident now that it is rather a Permission-Issue on the TrueNAS-Side which I dont understand well enough as of yet.

Thanks for the link!

@girish 👍🏻