Report ID: 1085672104. Problem connecting to WebDAV server for attachment syncing

qbit271 · November 28, 2023

I'm using Zotero 6.0.30 on Mac OS 13.4.1. I try to set up syncing with WebDAV using the following:
1. Open Zotero -> Settings
2. Go to Sync tab
3. Under "Sync attachments in my library" select WebDAV
4. Fill in username and password for the WebDAV server. The address is "https"
5. Press "Verify server"

I get the error message:
"Component returned failure code: 0x804b000a (NS_ERROR_MALFORMED_URI) [nsIIOService.newURI]"

dstillman · November 28, 2023

Are there non-alphanumeric characters in your WebDAV URL, username, or password?

Are you adding // characters (or any other characters) at the beginning of the WebDAV address?

qbit271 · November 29, 2023

The URL is:
cloud.orion-manifold.freeddns.org
It's a Nextcloud instance. The username does not contain non-alphanumeric symbols, an example password is:
jTxeo-Rrr4w-STAFa-NGFRn-jdGnz

So both URL and password contain only alphanumerics and dashes

dstillman · November 30, 2023

Actually, it looks like this also happens if you include a leading or trailing space in the URL field. We'll fix that, but that'd be my guess here.

qbit271 · November 30, 2023

Unfortunately there are no spaces in the URL.
I forgot to say that I run a WebDAV server behind a reverse proxy with SSL, and there are complains in Netcloud bug tracker about apps passwords in such configuration.
Is there a way to get more logs in Zotero?
I can even try to debug/submit a patch if you give me some clue on what is the function to test. Although I'm not very proficient with JS

dstillman · December 1, 2023

If you're actually getting the NS_ERROR_MALFORMED_URI error, that wouldn't have anything to do with the connection. That error is shown before it even tries to connect to anything. That has something to do with what you've entered into the fields, and probably just the URL field.

If you're referring to a SEC_ERROR_UNKNOWN_ISSUER error, which you will likely get once you've entered the URL correctly, that's because your server has a missing intermediate certificate (as you can see with the SSL Labs test linked from that page)