Hello rclone community,
I’ve been trying the latest beta ( 1.38-236 as of writing ), and I’m very interested in webdav ( Nextcloud ) support.
I have 3 Nextcloud servers available to me, and none of them show files with the lsd, ls, or mount commands. I’m able to upload fine, which is great, however, I can’t seem to view/download ( When I mount, nothing shows up until I upload something, then only items uploaded during this current mount show up. ) I haven’t tried other commands, as something is clearly not right, and I don’t want to cause problems to the servers.
With dav2fs, I’m able to mount, view, edit and browse everything fine, so my first guess was that it’s an rclone bug. However, I didn’t want to post a bug report, because it could be a configuration problem ( weird that it’s on all 3 servers with different setups though ).
What I did notice, is that if I run “rclone --max-depth=1 ls -vv xxxx:”. I get the files listed with messages like this:
2017/12/17 20:46:27 DEBUG : test.img: Ignoring item with bad status "HTTP/1.1 404 Not Found"
When I use other webdav clients, I see no such error however. Is this a configuration issue in Nextcloud ( In which case any help fixing it would be greatly appreciated, I can provide more details as needed. ), or is this a possible issue with rclone?
Thanks for the help, and for rclone!
P.S. The first Nextcloud server was set up as an OwnCloud server a few years ago by someone else, who then upgraded it to Nextcloud. It is running on an x86 virtual machine. Servers 2 and 3 are on ARM SBCs, one ARMv7 (Debian Jessie, Apache2, php5) one ARMv8 ( Ubuntu 16.04, nginx, php-fpm7.1 ). So I’ve tried a few different setups, which makes me think it could be an rclone bug ( combined with the fact that dav2fs shows everything fine ). All of them are using SSL ( HTTPS ). Thinking about it, is it possible rclone connects initially with https, then tries to read files over http? It’s possible port 80 is blocked, or http not allowed by the web server… Thanks again.