Cloudron Forum

@superhua can you send a mail to support@cloudron.io with your Cloudron details?

Update: cloudron-support --troubleshoot returns:

[WARN] netplan configuration is empty. this might be OK depending on your networking setup [FAIL] DNS is not resolving

Further, /etc/netplan/ is empty. How do I generate the correct .yaml file to include there?

Final Update: I was able to crate a netplan .yaml file by following these instructions.

Should be fixed with latest package now.

And I do not really get why did they remove the right to call their APIs?
Like if they don't want people to abuse their APIs. Wouldn't it be more reasonable to deploy rate limits? Like 1 API call for few hours would be enough for home usage.

@girish said in "Sorry, this file is too large – the maximum size is 1 MB":

@superhua you have to add export in front of the variables. So,

export FILE_STORAGE=local export FILE_STORAGE_UPLOAD_MAX_SIZE=26214400

A trick to remember this is that we use the .sh extension (shell) when export keyword is required.

Be useful to add that info to https://docs.cloudron.io/apps/outline/#custom-config 😉

Ah perfect, solved again then 😄

I've marked the app as stable now with the latest package update.

There's two DSN: CIVICRM_UF_DSN and right below the above screenshot CIVICRM_DSN . Both have to be updated after a clone.

Thank you. Good idea!

I ran traceroute and discovered that example.com resolved to the IP of an old server I once used.

Checking my registrar, I found that I had left example.com and www.example.com resolving to that old server's IP.

Deleting those entries has resolved the issue. When I check example.com it shows the expected "You are seeing this page because the DNS record of example.com is set to this server's IP but Cloudron has no app configured for this domain."

Thank you for your help!

Update: I installed Ubuntu 20.04 and then upgraded to Ubuntu 22.04. The Cloudron install then worked!

Thank you, @nebulon and @scooke!

After deleting the backups, checking various services, and restarting a number of times, everything is back.

Thank you again!