Can uninstall or install apps. Can't upload files

[nebulon]

For a start, try to disable all CloudFlare features like proxying and other things for that domain. They have often quite bad side-effects and cause random issues.

[dadams-AU]

So it's weird. I turned off proxying and even deleted the dns records for the apps. I was able to uninstall one app, but the other two i'm tyring to remove continue to time out. I still cannot upload files to apps that I'm keeping, and I can't access postresql through cli of an app. I still cannot install new apps.

[girish]

@dadams-AU what is the error ? any error message or screenshots ?

[dadams-AU]

I've been trying to figure this out for days. the only error I get is Timeout of 30000ms exceeded

[girish]

@dadams-AU please contact us at support@cloudron.io . you can also run cloudron-support --troubleshoot to see if it has any hints.

[girish]

@dadams-AU is this still a problem?

[vividly8450]

I'm having a similar issue on a week-old install. Like OP I was using Cloudflare, but never used the tunnel and have since disabled DNS proxying for the Cloudron subdomain. I was previously able to install / uninstall apps. However, starting within the last day or two, launching the app store just spins.

I have logged out, rebooted, launched a new private browser window, no dice.

[nebulon]

Any error in the browser console logs or server logs?

[girish]

I would also check Services -> unbound status and cloudron-support --troubleshoot output.

[vividly8450]

I didn't uncover the cause, but I believe it was related to the VM running out of disk space. I wound up reinstalling.

I let a large upload job run unattended and wound up completely filling the drive on the VM running Cloudron. I then cleared about 100 GB, rebooted for good measure, resized the partition using parted, expanded the filesystem, rebooted again, and let it run normally for a few days. That's when I noticed I couldn't install any new apps. I suspect that either the partition / filesystem resize or the disk being full broke something internally.

In hindsight I wish I had taken the time to dig into the logs a little more and see what was happening. But this is likely a direct result of my unusual environment fault.