Cloudron Forum

@Shai said in Is it worth it to upgrade to 24.04 from 22.04?: I might as well get a couple extra years before having to remember how to do this again. Shouldn't that be reason enough? 24.04 is already a year old, time to upgrade from the previous LTS.

@Shai You would need to edit your local computers /etc/hosts file and add in the old IP address of the previous Cloudron install for the domain name that you’d type in the browser bar. Then you should be able to use the hostname to still access the older Cloudron server.

Right, if you lost control of the domain. Switch the Domain provider in Domains view to manual or noop.

I found that I was using that domain name as an alias for another app.

oh that is true, I forgot about Cloudron 7 not being supported/tested on Ubuntu 24. So then yes you have to first install Ubuntu 22, then restore Cloudron, then update Cloudron, then follow the guide at https://docs.cloudron.io/guides/upgrade-ubuntu-24/

Dedicated servers from OVH are well priced too, worth it in my opinion but it likely depends greatly by region. I’m in Canada and there’s only so many local options, with OVH servers being the cheapest by far but still very powerful. I’d only recommend OVH if you’re a pretty decent sysadmin though because their support is not the quickest.

Hello @Shai The second level domain, also known as @ in most DNS providers e.g cloudron.io has a different propagation time then third level domains aka. example.cloudron.io. This could take up to 24 hours or more, depending on the hosters default TTL for the domain or what you've set. Might even be resolved now when you retry it after 7 hours.

@timconsidine said in Problem restarting Nextcloud after Disk Full Event: Worth considering some kind of free space monitoring? Various server monitor apps/agents is there a good tutorial somewhere? I also ran once into that case and would love automated monitoring. The new notification support of cloudron 8.2 does not cover that case?

@Shai yeah, better to remove it. On ubuntu, installing packages also enables them. So, this might cause problems in the future.

@nebulon Thanks. Ohh, I was so close last night. Your post gave me the courage to plunge back in. The username I gave to the user who owns the policy was a really wierd choice several years ago. So when I went to the aws users page, I didn't think of exploring there. Also the ID and secret were in a file on my local machine, filed well with a good file name. Last night I just wasn't careful in looking for it. So I'm all good now.

Yes, that was the problem. I was logged in under a second test user account that I had assigned admin role. Logged out and back in as my original cloudron owner account and all good on that front. Thanks.

@girish THANK YOU! I followed your instructions and all good now.

@girish thank you!

@msbt thanks so much. My interpretation of the fix suggested didn't work. I have posted a follow-up question there.

@shai Glad to hear it, I was going to give it a try this weekend, so this saves me a bit of time. Congrats.

@girish the local_infile is the approach the app uses to load data sets for optional functionality. I'll go to the forum for OpenEMR and see if there is a way for me to manually upload the data instead of being done through the webapp UI.

@girish Thank you!

@girish Now It's working, thanks for your help

Also note, that surfer has no concept of admins or normal users, so all Cloudron users, which are assigned to have access to the app can login and are the same.