[Bug]: Can't delete folders on external storage (S3)

[marcoklobas]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

After updating to Nextcloud Hub 25 Autumn (32.0.0) I can't delete any folder on AWS S3 external storage.

Files are deleted flawlessly. Local stored folders are deleted without issues as well.

I get a Delete folder: failed notification. I attach the specific error log below which mentions "400 Bad Request" and "Malformed XML".

Interestingly, if I replace the api-2.json.php file available in the 3rdparty/aws/aws-sdk-php/src/data/s3/2006-03-01 folder with the one coming from the previous version (31.0.9), then I can delete the folders successfully. I guessed this file is involved in the issue due to the ?delete string mentioned in the log.

Hope someone will check the differences between the old and new api-2.json.php files and figure out what is wrong and find a fix.

Any idea whether is it safe to keep the older working file for the time being?

Steps to reproduce

1. Update to Nextcloud 32 version
2. Attempt to delete a folder
3. Observe the error message

Expected behavior

Folders should be removed on external storage after a delete command is invoked.

Nextcloud Server version

32

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.3

Web server

Apache (supported)

Database engine version

MySQL

Is this bug present after an update or on a fresh install?

Upgraded to a MAJOR version (ex. 31 to 32)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Error executing "DeleteObjects" on "https://***REMOVED SENSITIVE VALUE***/?delete"; AWS HTTP error: Client error: `POST https://***REMOVED SENSITIVE VALUE***/?delete` resulted in a `400 Bad Request` response: <Error><Code>MalformedXML</Code><Message>The XML you provided was not well-formed or did not validate against our publis (truncated...) MalformedXML (client): The XML you provided was not well-formed or did not validate against our published schema - <Error><Code>MalformedXML</Code><Message>The XML you provided was not well-formed or did not validate against our published schema</Message><RequestId>***REMOVED SENSITIVE VALUE***</RequestId><HostId>***REMOVED SENSITIVE VALUE***</HostId></Error>

Additional info

No response

[joshtrichards]

Can you share the entire Nextcloud log entry?

What S3 platform/provider is this?

[marcoklobas]

I use AWS S3. No other changes have been made. The same configuration worked in the previous version.

The only error log I get is this:

Error executing "DeleteObjects" on "URL/?delete"; AWS HTTP error: Client error: POST URL/?deleteresulted in a400 Bad Request response: <Error><Code>MalformedXML</Code><Message>The XML you provided was not well-formed or did not validate against our publis (truncated...) MalformedXML (client): The XML you provided was not well-formed or did not validate against our published schema - <Error><Code>MalformedXML</Code><Message>The XML you provided was not well-formed or did not validate against our published schema</Message><RequestId>ID</RequestId><HostId>ID</HostId></Error>

I replaced "sensitive" values with URL and ID.

Thanks for chiming in.

[walec51]

Getting the same thing right after update to the latest version for OVH S3

Error executing "DeleteObjects" on "https://marketing-do-obrobki.s3.waw.io.cloud.ovh.net/?delete"; AWS HTTP error: Client error: `POST https://marketing-do-obrobki.s3.waw.io.cloud.ovh.net/?delete` resulted in a `400 Bad Request` response: <?xml version='1.0' encoding='UTF-8'?> <Error><Code>MalformedXML</Code><Message>The XML you provided was not well-formed (truncated...) MalformedXML (client): The XML you provided was not well-formed or did not validate against our published schema - <?xml version='1.0' encoding='UTF-8'?> <Error><Code>MalformedXML</Code><Message>The XML you provided was not well-formed or did not validate against our published schema</Message><RequestId>tx11091945100842a893788-0068e23ad9</RequestId></Error>

[walec51]

Interestingly, if I replace the api-2.json.php file available in the 3rdparty/aws/aws-sdk-php/src/data/s3/2006-03-01 folder with the one coming from the previous version (31.0.9), then I can delete the folders successfully. I guessed this file is involved in the issue due to the ?delete string mentioned in the log.

I can confirm this worked

replaced

api-2.json-new.php

with

api-2.json.php

and this started working

[Kiter1988]

I am also unable to delete folders, but I get a slightly different error code.
I also tried replacing the API file, but that did not work.

[files_external] Fehler: Error executing "DeleteObjects" on "https://s3.hidrive.strato.com/bucketname?delete"; AWS HTTP error: Client error: `POST https://s3.hidrive.strato.com/bucketname?delete` resulted in a `400 Bad Request` response:
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>MissingContentMD5</Code><Message>Missing required header for this re (truncated...)
 MissingContentMD5 (client): Missing required header for this request: Content-Md5. - <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>MissingContentMD5</Code><Message>Missing required header for this request: Content-Md5.</Message><Key>/bucketname</Key><RequestId>only an id</RequestId></Error>
	DELETE /remote.php/dav/files/admin/randompath
	

[manuelaznar]

The same thing happens to me after updating from 31.0.5 to 32.0.1 :

Error executing "DeleteObjects" on "URL/?delete"; AWS HTTP error: Client error: POST URL/?deleteresulted in a400 Bad Request response: MalformedXMLThe XML you provided was not well-formed or did not validate against our publis (truncated...) MalformedXML (client): The XML you provided was not well-formed or did not validate against our published schema - MalformedXMLThe XML you provided was not well-formed or did not validate against our published schemaIDID

[manuelaznar]

Interestingly, if I replace the api-2.json.php file available in the 3rdparty/aws/aws-sdk-php/src/data/s3/2006-03-01 folder with the one coming from the previous version (31.0.9), then I can delete the folders successfully. I guessed this file is involved in the issue due to the ?delete string mentioned in the log.

I can confirm this worked

replaced

api-2.json-new.php

with

api-2.json.php

and this started working

It works, but the UI still shows the error message, and you need to refresh to see that the folder has actually been deleted.

[marcoklobas]

Interesting.

In my case, using the "trick" of the old api-2.json.php version, I don't get any error alerts and the deleted folder disappears without the need to refresh the page.