You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After configuring a volume /User with permissions 'rmda' for account @user, trying to configure the Zotero webdav sync to work with it fails with confusing (to me) log message.
To Reproduce
Copyparty config:
[global]
# i: unix:770:caddy:/tmp/cparty.sock
i: 127.0.0.1
p: 3309
e2dsa # enable file indexing and filesystem scanning
e2ts # and enable multimedia indexing
ansi # and colors in log messages
ah-alg: argon2 # enable password hashing
chpw
http-only
gsel
q, lo: $LOGS_DIRECTORY/%Y-%m%d.log
df: 2
no-robots, force-js # make it harder for search engines to read your server
# create users:
[accounts]
user: ...
[/]
/var/lib/copyparty/mnt/
accs:
r: *
[/User]
/var/lib/copyparty/mnt/User
accs:
rwmd: user
flags:
daw
davauth
safededup
pk
With server running as above, configure Zotero to connect to the webdav server with the url "https://[webdav.domain]/User/", any username and the appropriate password.
Expected behavior
Zotero should be able to access the subdirectory /User/zotero (created manually) and begin using it for syncing.
Instead it fails with an error about the server's response. The following lines in the server log correspond to this.
it looks like copyparty is failing to see how much free space you have on the drive, and assumes it is full. Could you try to remove the df option and see if that makes it work?
of course, that is not a fix -- I'd like to figure out why checking the disk space usage is not working on your machine, so I'll post a script we can use to figure this out later tonight.
I forgot to mention earlier that this error was only happening with the zotero built-in webdav client. Mounting the webdav with Nautilus and creating the sub-directory seemed to work okay (though I didn't try creating any files that way).
turns out this was a general issue with how df applied to PUT uploads, which is what webdav does... So thanks for catching this :>
was also a good opportunity to clean up how df only cared about files with a known filesize -- now it will also reject uploads of unknown size, if the disk space is already below the limit.
Describe the bug
After configuring a volume
/User
with permissions 'rmda' for account @user, trying to configure the Zotero webdav sync to work with it fails with confusing (to me) log message.To Reproduce
Copyparty config:
With server running as above, configure Zotero to connect to the webdav server with the url "https://[webdav.domain]/User/", any username and the appropriate password.
Expected behavior
Zotero should be able to access the subdirectory /User/zotero (created manually) and begin using it for syncing.
Instead it fails with an error about the server's response. The following lines in the server log correspond to this.
Server log
Server details
if the issue is possibly on the server-side, then mention some of the following:
lsblk -f
on linux):Client details
if the issue is possibly on the client-side, then mention some of the following:
Additional context
Zotero version 7.0.7 installed from https://flathub.org/apps/org.zotero.Zotero
The text was updated successfully, but these errors were encountered: