-
Notifications
You must be signed in to change notification settings - Fork 187
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
Error 500 when using rclone with ocis #2767
Comments
|
Hi @wkloucek yes Does this help? Do you need more information? |
I created a PR to document the Rclone usage with oCIS #2785. And what you describe is indeed a bug that I could reproduce. Test folder I tried to sync with Rclone:
Rclone WebDAV remote set up with OIDC according to #2785, then I run this Rclone command:
It doesn't yield any output, but oCIS does: oCIS log:
|
@nikslor this fix will land on oCIS latest in the next few days (and maybe also in the oCIS 1.15.0 release) |
Awesome work @wkloucek - thanks so much for looking into this and being that responsive! Great work, thanks a lot! |
Fix is on latest master of oCIS and will therefore be part of the 1.15.0 release. Docs are merged, too. So if you want to look into Rclone with OpenID Connect Authentication ;-) -> https://owncloud.dev/clients/rclone/ |
Just confirming, that 1.15.0 works flawlessly with rclone; thanks a lot @wkloucek! |
Describe the bug
I run into an issue when trying to sync my home dir to ocis (1.14) using rclone (1.57). On the server side I see messages like the following:
On the client side:
Steps to reproduce
It seems, that the problem occurs due to the fact that I have folders only containing one other folder, it should therefore be easy to reproduce my issue with the following commands:
Create the following folder structure on your client:
1.1
$ mkdir -p rclone_test/dir1/dir2/dir3
1.2
$ touch rclone_test/dir1/dir2/dir3/testfile.txt
use rclone to sync this folder structure to ocis:
2.1
$ rclone -vvv --no-check-certificate --low-level-retries 2 sync /tmp/oc/rclone_test storage:
Expected behavior
ocis should not throw a HTTP 500 error in such a case
Actual behavior
IT seems, that ocis throws a HTTP 500 error in such a case
Setup
I did
setcap 'cap_net_bind_service=+ep' ocis
and run ocis like this:The text was updated successfully, but these errors were encountered: