I am trying to use rclone to list the contents of my IceDrive using webDAV. I get an authentication error message saying username or password is incorrect but they are the username and password that work to log into the web site. I am new to rclone. What am I missing?
Run the command 'rclone version' and share the full output of the command.
rclone v1.62.2
os/version: ubuntu 22.04 (64 bit)
os/kernel: 5.19.0-46-generic (x86_64)
os/type: linux
os/arch: amd64
go/version: go1.20.2
go/linking: static
go/tags: none
Which cloud storage system are you using? (eg Google Drive)
webDAV (for IceDrive connection)
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone -vv ls IceDrive:
The rclone config contents with secrets removed.
[IceDrive]
type = webdav
url = https://webdav.icedrive.io
vendor = other
user = myemailaddress@gmail.com
pass = REMOVED
A log from the command with the -vv flag
2023/06/29 16:45:51 DEBUG : rclone: Version "v1.62.2" starting with parameters ["rclone" "-vv" "ls" "IceDrive:"]
2023/06/29 16:45:51 DEBUG : Creating backend with remote "IceDrive:"
2023/06/29 16:45:51 DEBUG : Using config file from "/home/steve/.config/rclone/rclone.conf"
2023/06/29 16:45:51 DEBUG : found headers:
2023/06/29 16:45:52 ERROR : : error listing: couldn't list files: Username or password was incorrect: Sabre\DAV\Exception\NotAuthenticated: 401 Unauthorized
2023/06/29 16:45:52 DEBUG : 4 go routines active
2023/06/29 16:45:52 Failed to ls with 2 errors: last error was: couldn't list files: Username or password was incorrect: Sabre\DAV\Exception\NotAuthenticated: 401 Unauthorized
2023/06/29 18:00:53 NOTICE: --dump-headers is obsolete - please use --dump headers instead
2023/06/29 18:00:53 NOTICE: --dump-bodies is obsolete - please use --dump bodies instead
2023/06/29 18:00:53 DEBUG : rclone: Version "v1.62.2" starting with parameters ["rclone" "-vv" "ls" "IceDrive:" "--dump-headers" "--dump-bodies"]
2023/06/29 18:00:53 DEBUG : Creating backend with remote "IceDrive:"
2023/06/29 18:00:53 DEBUG : Using config file from "/home/steve/.config/rclone/rclone.conf"
2023/06/29 18:00:53 DEBUG : found headers:
2023/06/29 18:00:53 DEBUG : You have specified to dump information. Please be noted that the Accept-Encoding as shown may not be correct in the request and the response may not show Content-Encoding if the go standard libraries auto gzip encoding was in effect. In this case the body of the request will be gunzipped before showing it.
2023/06/29 18:00:53 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2023/06/29 18:00:53 DEBUG : HTTP REQUEST (req 0xc00091a600)
2023/06/29 18:00:53 DEBUG : PROPFIND / HTTP/1.1
Host: webdav.icedrive.io
User-Agent: rclone/v1.62.2
Authorization: XXXX
Depth: 1
Referer: https://webdav.icedrive.io/
Accept-Encoding: gzip
<d:error xmlns:d="DAV:" xmlns:s="sabre/dav">
<s:sabredav-version>4.4.0</s:sabredav-version>
<s:exception>Sabre\DAV\Exception\NotAuthenticated</s:exception>
<s:message>Username or password was incorrect</s:message>
</d:error>
0
2023/06/29 18:00:54 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2023/06/29 18:00:54 ERROR : : error listing: couldn't list files: Username or password was incorrect: Sabre\DAV\Exception\NotAuthenticated: 401 Unauthorized
2023/06/29 18:00:54 DEBUG : 4 go routines active
2023/06/29 18:00:54 Failed to ls with 2 errors: last error was: couldn't list files: Username or password was incorrect: Sabre\DAV\Exception\NotAuthenticated: 401 Unauthorized
If your distro has different file manager then install any other webdav client to test e.g. GhostCloud.
I do not know IceDrive but are you sure that you have webdav credentials? Maybe credentials you are using are for logging to IceDrive website. Webdav ones do not have to be the same... Testing with other webdav client will confirm it.
Something wrong with credentials but I can't see where so I got a refund from IceDrive. Got rclone working with GoogleDrive instead. Thanks for your help.
After this post, I received a notice from IceDrive that they have updated their webDAV implementation. I had moved to another cloud storage provider and have not used it since. The behavior may be different now. BTW, I did eventually get a refund from them.
