Hello,
I am trying to connect RaiDrive to a FileBrowser Quantum WebDAV endpoint, but I cannot get it to authenticate successfully.
My WebDAV server is FileBrowser Quantum running behind Tailscale. The endpoint is available over plain HTTP, not HTTPS:
http://100.x.x.x:8080/dav/pny250/
Connection settings in RaiDrive:
Storage: WebDAV
Protocol: HTTP
Address: 100.x.x.x
Port: 8080
Path: /dav/pny250/
Account: admin
Password: API token generated in FileBrowser Quantum
FileBrowser Quantum uses an API token instead of the regular account password for WebDAV access. The token is relatively long, approximately 100–120 characters.
RaiDrive returns:
401 Unauthorized
I tested the same endpoint, username, and API token with curl using a WebDAV PROPFIND request:
curl.exe -v -X PROPFIND -u “admin:API_TOKEN” -H “Depth: 1” “http://100.x.x.x:8080/dav/pny250/”
The server returns a valid WebDAV multistatus response and lists the files:
HTTP/1.1 207 Multi-Status
Example response contains:
<D:multistatus xmlns:D=“DAV:”>
<D:href>/dav/pny250/</D:href>
<D:href>/dav/pny250/WebSender_v12a-1.macro</D:href>
<D:status>HTTP/1.1 200 OK</D:status>
</D:multistatus>
So the WebDAV endpoint, path, username, and API token are valid.
Questions:
Does RaiDrive support FileBrowser Quantum WebDAV with API-token authentication?
Could RaiDrive have a limitation with long passwords/API tokens of around 100–120 characters?
Does RaiDrive send WebDAV authentication differently from curl?
Is there any specific option required for this type of WebDAV server?
Thank you.