-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Can't copy files from a folder to another when using S3 object storage as a Primary Storage #9679
Comments
Hi, please update to 24.0.9 or better 25.0.3 and report back if it fixes the issue. Thank you! My goal is to add a label like e.g. 25-feedback to this ticket of an up-to-date major Nextcloud version where the bug could be reproduced. However this is not going to work without your help. So thanks for all your effort! If you don't manage to reproduce the issue in time and the issue gets closed but you can reproduce the issue afterwards, feel free to create a new bug report with up-to-date information by following this link: https://github.com/nextcloud/server/issues/new?assignees=&labels=bug%2C0.+Needs+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+ |
@szaimen I upgraded my nextcloud installation to 25.0.3 and the issue persist. Also as a side effect document versioning is not working, in fact, from the previous version it didn't work but I thought the problem was something with the installation but in this version it doesn't work either. In block storage everything works perfectly. |
@szaimen Problem Solved, But hey, the above apparently is not a problem of the Linode object storage but of the way in which Nextcloud manages those configurations. So this issue can be marked as solved |
So is this a docker variable problem? |
@szaimen |
All right, so I think this should potentially be documented here? https://docs.nextcloud.com |
Your issue was two-fold:
The docs technically covered this before, but were a bit confusing. That's been remedied some recently, but I can see already see there's room for further improvement. Namely to make sure it is clear that the https://www.linode.com/docs/products/storage/object-storage/guides/urls/#cluster-url-s3-endpoint As for
Often both styles will work with some providers. The main issue is that the Documenting all of this clearly is also challenging because a few other configuration combinations will technically sometimes work, but they won't get the results you might expect or may be fragile (i.e. break in the future). It gets confusing very quickly! I tried to narrow down the choices recently in the latest docs to the two reliable combinations that always (to my knowledge) work and always place your data where you're expecting (regardless of provider/object store platform) From the looks of it, Linode would work either as:
With the above resulting in your data being stored in https://us-southeast-1.linodeobjects.com/mybucket/ or:
With the above resulting in your data being stored in https://mybucket.us-southeast-1.linodeobjects.com/ I'll see about:
|
…cket URL Fixes nextcloud#9679 Signed-off-by: Josh Richards <[email protected]>
Bug description
After installation I uploaded a file and I can't copy it to another folder.
But I can do the following operations without errors:
I'm using the S3 object storage provided by linode. I have the correct values of key and secret and the correct permision in the object storage.
Steps to reproduce
Expected behavior
Being able to copy files from one folder to another without problems.
Installation method
Official Docker image
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.0
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: