Closed lewisgardner closed 1 month ago
Invalid region: region was not a valid DNS name.
Sounds like something you wanna check.
"region": "**region**",
Is this what your region
is actually set to?
Since you're not using AWS, you should be able to leave region
entirely blank in your case since we already handle the scenario mentioned in DO's docs. Otherwise this must be set to - as strange as it sounds but like DO's own docs say - a valid AWS region. But like I said, blank is easier/best since we already handle this.
But this isn't new behavior.
Thank you for the responses. I removed the 'region' parameter entirely and it works now. Please note that this is changed behaviour: The region parameter has been set to '**region**
' ever since I created the server as the DigitalOcean documentation states that the region is ignored when using their S3 compatible storage. The only change I did was upgrade server from Ubuntu 22.04 to 24.04 and only after that I had to remove the 'region' parameter.
Then I would considered tjis a bug fixed, not a bug introduced, becasue it should never work as is.
Please note that this is changed behaviour: The region parameter has been set to 'region' ever since I created the server as the DigitalOcean documentation states that the region is ignored when using their S3 compatible storage
It's a little confusing, but the DO docs state it must be set to a valid AWS region. They're own example says us-east-1
:
"Due to an AWS-specific behavior in all versions of the SDK except Python 3, to successfully create a new bucket, you must specify an AWS region, such as us-east-1, in your configuration. This is because, when creating a bucket, the SDK sends an entirely different payload if a custom region is specified, which results in an error."
We haven't changed our handling of the region
parameter in many years. I'm not sure how your config ever worked.
Perhaps an earlier version of the AWS SDK ignored your value of **region**
silently (since it's also happens to contain characters that aren't valid within DNS entries or something). That wouldn't have been reasonable behavior either by the SDK, so still a bug fixed. :) Also just a wild guess. I did a quick look and I don't see any obviously related changes in the SDK.
What version of Nextcloud did you upgrade from? (I'm presuming you upgraded Nextcloud too recently since 30.0.1 just came out).
According to DO docs, the region only has to be valid AWS region when creating a bucket (which was not required in this case as I had created the bucket manually beforehand).
I was running version NC 29 when I upgraded the server from Ubuntu 22.04 to 24.04, after which the S3 connectivity was broken. I then updated to NC 30.0 (using update/updater.phar which still worked fine) and then 30.0.1 a few days later when it was released in case that would fix the issue. My best guess is that parameter handling has somehow changed between PHP 8.1 and 8.3 (they did introduce sensitive parameters in 8.2) but I'm just happy it all works now.
⚠️ This issue respects the following points: ⚠️
Bug description
After upgrading Ubuntu from 22.04 to 24.04 (which also upgrades PHP from 8.1 to 8.3) the AWS S3 ObjectStore is unable to connect to S3 compatible backend (DigitalOcean Spaces). The S3 ObjectStore is configured as the primary storage. The server worked perfectly with this setup before the OS (and PHP) upgrade, no other changes were performed.
I have downloaded latest AWS PHP SDK into test folder and performed connection tests from same Apache/PHP server and connection works correctly.
Steps to reproduce
1 .Run a nextcloud server with primary storage attached to S3 compatible backend
Expected behavior
The nextcloud server should continue to be able to access the backend.
Nextcloud Server version
30
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?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
No login possible
Nextcloud Logs
Additional info
No response