@luckow The info has moved to a separate section called Info. The updates section looks a bit empty in 8.0.3 yes...

well I had to reset and reinstall to have access again.. can close the topic

Sounds good! It was also odd that some other apps were affected by the restart-looping Nextcloud instances.

Just to note here, a server reboot often is not the best idea if some services are still up and running. Nearly everything can be fixed while the server is active and a reboot might just bring down those unnecessarily.

Looks like some tmpfs corruption caused files to have incorrect permissions. The reboot cleared up tmp and the previous state was not there. Just redownloading 8.0.1 and updating again made it work.

Yes, /24 would only allow 250 or so addresses, we do need a /16 . I am not sure why 172.17 and 172.18 networks are conflicting though . In the original error message it says "172.18.0.1" is in use. If your local network is 172.18, it all makes sense. Currently, there is no workaround for this since the code has some places where it hardcodes 172.18 network.

@girish Interesting case, for 2 days it failed. There were attempts after clearing the browser, a trial on another device. Today it just started to work but for that it changes the permission after saving the file from ‘www-data’ to ‘root’. Edit: Good with the entitlement is good, just need to refresh the page.

I have submitted a new AMI in any case.

We haven't added a way to add custom persistent iptables rules . For SSH though, just move it port 202 and disable root auth and password auth. This usually cuts down all bots to 0.

Ok that file is showing regular checks but no packages marked for upgrade. I will keep an eye on this. Thanks for the support.

This is a very old issue, please create a separate topic with the details of the problem.

Hi, and thanks so much for the replies - much appreciated

Hi Nebulon, Thank you for your assistance regarding the backup issue for the mail application. Based on your suggestion and the error logs, I have decided to increase the memory limit for the backup process to 4.5 GiB. Here is the updated configuration: Memory Limit: 4.5 GiB Upload Part Size: 128 MiB I will monitor the backup process after this change to see if it resolves the issue. I have attached a screenshot of the updated settings for your reference. If the problem persists, I will provide additional logs and system metrics for further analysis. Thank you for your support. Best regards, Felipe Rubilar

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.

This was handled via support. The root cause was a bug in our addon handling. Fix is https://git.cloudron.io/cloudron/box/-/commit/01945675edfd705d1a19d6ed9e40633b721be8f7

@cocam123 as @timconsidine said, Cloudron is not designed to run alongside 3rd party software. The best approach here is to run your public stuff in a separate VM. Then, as @matix131997 said use the app proxy feature. This will set up nginx to proxy all the requests for the domain to this separate VM . App Proxy was designed specifically for the use case of running software outside of the VM and re-using the IP.

@Jarod In the AWS Marketplace Image (AMI) , route53 is disabled in the setup screen. It is apparently against Marketplace policy to take route53 API credentials (a member of their team had reached out to us and notified us about this). So, if you use the AMI, then the setup screen will not show route53 as an option anymore.

Unfortunately, we ended up breaking https://forum.cloudron.io/topic/11993/backuptask-crashing-after-8-0-update . But yeah, overall the fix is good.

@girish said in WordPress app container stuck on updating from package version 3.7.2 to 3.7.3: This happens with apps which contains files that change their size when the backup is going on. ... Maybe you have some plugin that writes to somewhere periodically? Thank you @girish Great advice and just the clue we needed. We figured out what that was, stopped it and then we could take a WP backup manually; and then we were also able to update to the latest packaged WP version 3.8.0 Thank you once again; your prompt help is much appreciated You can mark this ticket as resolved; cheers!

Hey @girish, @nebulon, thanks for coming back to me so quickly! Happy to report that the fix worked wonders, and the backup completed successfully. As for our setup, we set up the backup server a while ago now, my memories are not the freshest. But IIRC we are using OpenSSH Server for Windows Server. And from what I can see Windows shell uses mklink to create hard links. But I have never used it.