Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker Seafile 11 Seafdav (Webdav) upload issue: 0 Byte Files #2809

Open
nobe80 opened this issue Aug 12, 2024 · 7 comments
Open

Docker Seafile 11 Seafdav (Webdav) upload issue: 0 Byte Files #2809

nobe80 opened this issue Aug 12, 2024 · 7 comments

Comments

@nobe80
Copy link

nobe80 commented Aug 12, 2024

Hi,

i have faced an issue with Seafile webdav (Seafdav) when i use Seafile Version 11 after upgrade to 11.0.11.
The issue is the follow:

In Windows file explorer i have successful a Webdav drive over https to the Seafile server. So seafdav is enabled, we can see all folders. When i upload some files like pdf or simple text files i get an error “…
file is to big…” and i have 0 Bytes files in the folder.

When i downgrade to Seafile Version 10 again no problems at all. Everything works fine then.
We use Seafile docker community.

Does anyone have a hint what could be the reason?

seafdav2
seafdav1

@imwhatiam
Copy link
Member

Hello, Seafile’s seafdav is based on the wsgidav project(GitHub - mar10/wsgidav: A generic and extendable WebDAV server based on WSGI 1). Seafile version 10 uses wsgidav 4.1, while version 11 uses wsgidav 4.3.

It seems that wsgidav added some checks in version 4.3, which caused your issue.

We have also conducted tests, and it seems that this issue only occurs when connecting to seafdav using Windows File Explorer. Other WebDAV clients do not encounter this problem.

We will debug it to see if they can resolve this problem.

@nobe80
Copy link
Author

nobe80 commented Sep 2, 2024

Hi @imwhatiam

so that means that with wsgidav as standalone the bug would also be there?

So the functionality without any apps is the most important thing for using Seafile with Windows.
It is a must have that it works further, like before.

Thanks and please keep me updated

@imwhatiam
Copy link
Member

@nobe80 We will try to solve this problem, but we need to gain a deep understanding of the WsgiDAV project, which may take quite a long time.

@nobe80
Copy link
Author

nobe80 commented Sep 9, 2024

@imwhatiam Thanks for that info. Do you know how long Seafile 10 will work further?
Because in that case we have to use Seafile 10 until the bug is fixed.

regards

@gianogli
Copy link

@imwhatiam Any news regarding this issue?
We upgrade our seafile installation to 11 some weeks ago and now all our users have 0 byte files only!!! If they try to upload/restore the correct file, the server change it again with a file of 0 byte after 3/4 seconds. Unusable!!!
Can you tell us how the correct way to rollback to 10? (on-premise pro installation without docker).
Thanks...

@nobe80
Copy link
Author

nobe80 commented Nov 21, 2024

Hi @imwhatiam ,

do you have any news on this? The issue is still pending since summer this year! We need that feature because the native webdav is the most important function and the reason why we are using Seafile!
So please tell me when this mistake will be fixed? What happend in the meantime ate the dev team?

thanky & regards

@harenber
Copy link

harenber commented Dec 1, 2024

We have also conducted tests, and it seems that this issue only occurs when connecting to seafdav using Windows File Explorer. Other WebDAV clients do not encounter this problem.

Are you sure about this? I see the same misbehaviour using davfs2 on Debian (crostini on a Chromebook):

harenber@penguin:~/seafile/private/ansible/plus$ df .
Filesystem                           1K-blocks  Used Available Use% Mounted on
https://XXX/seafdav/      7184  7184         0 100% /home/harenber/seafile
harenber@penguin:~/seafile/private/ansible/plus$ echo "Testfile" > aaa
bash: aaa: Input/output error
harenber@penguin:~/seafile/private/ansible/plus$ cat aaa
harenber@penguin:~/seafile/private/ansible/plus$ ls -l aaa
-rw-r--r-- 1 harenber davfs2 0 Dec  1 17:55 aaa
harenber@penguin:~/seafile/private/ansible/plus$ 

This bug is really a bummer. My strategy to re-install my vserver farm after a catastropic failure in the VMs is based on the possibility to mount via WebDAV. And I learned the hard way that this fails now as I upgraded my Seafile server.

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants