Okay, so after some testing I still don’t know why the changes in htaccess disappear. But on one server it works fine, and on the other it reports a 5 GB file size limit — no idea why. At least normal uploads in the web interface now work. However, all my previous tests failed because I was always testing with a shared link that has edit rights. With that, I still get a 413 error and the following message: BadRequest – Expected file size of 3099309687 bytes, but 0 bytes were read (from the Nextcloud client) and written (to the Nextcloud storage). This can be caused by a network issue on the sending side or a writing issue on the server side. So it seems that the upload limit only works for regular logged-in uploads, but not for uploads via share links. Any idea what might cause this difference? Guess this is a nextcloud issue.

@girish Increasing the task memory did it. Issue solved.

I have not noticed this issue yet after upgrading to 9.x.

I updated the post already and added a section at top: For the sake of completeness as it may happen to others: We finally identified an issue in the network configuration, that isolated the internal VM network from the public network. Disabling the isolation solved the issue at hand. We are now figuring out another way to isolate the VM itself. you can decide if you wanna decline/resolve it or just publish and directly close it

@girish thank you, Girish. I already ensured that my server is running security updates using those commands.

Marking as solved due to inactivity.

@derin can you open a separate topic with that request for nextcloud? can you also elaborate on your use case for this (does nextcloud the app support aliases?) ?

@luckow Maybe some sort of shared hosting? Should be able to support lots of wordpress instances, LAMP stacks and Surfer apps.

Perfect. Everything works as intended. Thank you, @girish, and have a great beginning of your week

This has gone back to normal for a few days in a row, indicating the upgrade didn't produce an issue, but probably the hardware infrastructure at Netcup.

Hello @maellerollet and welcome to the Cloudron forum It sounds like you are running into this issue: https://docs.cloudron.io/troubleshooting/#domain-issues-expiry Please check this documentation and see if this helps to resolve your issue.

Fixed in https://git.cloudron.io/platform/box/-/commit/3e6f3bd807a63e38711ace7e83eb5e2b722299b5 . Thanks for reporting!

Okay, with 9.0.10, backup was able to be completed.

So turns out that potentially the issue is disk space. we ran the process again without changing anything - same result we clean up and enable at least 40 GB of space and relaunched the update process = successful update suggestions: better pre-update space check and verbose messaging about needed space for update

I came here to learn about Hetzner having periodic issues. Thanks @girish ! I'm currently facing a similar issue on a Cloudron 9.x instance and was looking for old threads mentioning the exact same error. Here am I. Damn Hetzner then @girish is there a support ticket open with Hetnzer or anything that we can do?

Hello @jkammerer I understand that backward compatibility is desired. In this specific case it was actually a bug in the previous version that the field could have been left empty in the API call and it worked. People still use pop3 and we have to accommodate for this.

hai @guacadmin , are you using ubuntu in Alibabacloud?

This was reported in the other thread. Was fixed - https://forum.cloudron.io/topic/14359/cloudron-9.0-beta-bug-reports/128

I confirm. It work without 127.0.0.1

Thanks a lot, that was tho Problem. I changed the user rights from Administrator to Superadmin an it's working as expected.