SeafDav not allowing writing

I have connected my Windows 10 computer to my SeaFile Server via WebDav (SeafDav). I cannot make any changes to the drive. It results in write errors. Any help here would be greatly apprecaited.

Thanks,
Jeff Savage ~ BetaLeaf

New File:
https://i.gyazo.com/3882a1b3a5663054e0c18288aff95807.png
Modify File:
https://i.gyazo.com/df6aa00072a1dbae9e2f80979fbac86b.png

Can you check the server logs? Which seafile version do you use?

I am not writing to the root. I am attempting to write to the My Libraries folder.

Using Server 6.0.4 Pro. Here are the logs and configuration files.
https://github.com/BetaLeaf/FileStorage/releases/download/17/Logs.zip

Here’s an excerpt from my nginx\seafdav.access.log that caught my eye.

192.168.0.2 - BetaLeaf@gmail.com [16/Dec/2016:06:21:50 -0500] "PUT /seafdav/My%20Library/test.txt HTTP/1.1" 403 423 "-" "Microsoft-WebDAV-MiniRedir/10.0.14393"

Error 403 means Forbidden (The request was a valid request, but the server is refusing to respond
to it. The user might be logged in but does not have the necessary permissions for the resource.)
Error 423 means locked (The resource that is being accessed is locked)

I’m not sure what this means for me honestly. My guess is the file is being locked as soon as it is created or I don’t have permission to write to the folder. I can create files fine using the seafile client or the web interface.

I’m using CentOS 7 Minimal and I installed Server 6.0.4 Pro using the install script found at https://github.com/haiwen/seafile-server-installer. Any help given would be greatly appreciated.

cd /root
wget --no-check-certificate https://raw.githubusercontent.com/haiwen/seafile-server-installer/master/seafile_centos
bash seafile_centos 6.0.4

What happens if you try to create a empty folder? Does this work?

No, it produces the same error. I will get a log for that for you. Hang Tight.

192.168.0.2 - BetaLeaf@gmail.com [19/Dec/2016:03:43:39 -0500] "MKCOL /seafdav/My%20Library/New%20folder HTTP/1.1" 403 423 "-" "Microsoft-WebDAV-MiniRedir/10.0.14393"

Did you try to do this on another library?

It produces the same error, no matter what library I use.

Just for confirmation: If you try to upload via web interface or client to the same library it works?

Yup. No problems there.

Please look at this doc: https://manual.seafile.com/extension/webdav.html

It seems not all your configs are the same as recommended.

I do not understand. My configuration is the same as the recommended. Please explain.

A new discovery. It appears there is something wrong with the client I’m using. (Windows 10 File Explorer)
CyberDuck works fine when using WebDAV. I need the Windows 10 File Explorer to work, CyberDuck does not allow me to mount the drive in File Explorer.

I’m trying to use portable programs I have located on the SeaFile Server, which is why I need the Windows 10 File Explorer to be able to write to WebDAV. I realize I could use the client but it uses a lot of storage space on the device to sync the program to my device. I have very limited storage space on my SSD. This is why I need to use WebDAV.

So I was inspecting the traffic with Fiddler. Not sure if this helps anyone pinpoint an issue but I thought I would post anyways.

CyberDuck:

MKCOL /seafdav/My%20Library/New%20folder/ HTTP/1.1
Content-Length: 0
Host: 192.168.0.3
Connection: Keep-Alive
User-Agent: Cyberduck/5.2.3.21496 (Windows 10/10.0) (x86)
Accept-Encoding: gzip,deflate
Authorization: Basic --redacted-- 

Responses:

HTTP/1.1 201 Created
Server: nginx
Content-Type: text/html
Content-Length: 376
Connection: keep-alive
Date: Mon, 19 Dec 2016 11:10:42 GMT
HTTP/1.1 207 Multistatus
Server: nginx
Content-Type: application/xml
Content-Length: 7274
Connection: keep-alive
Date: Mon, 19 Dec 2016 11:10:42 GMT

Windows 10 File Explorer (MiniRedirector 10):

MKCOL /seafdav/My%20Library/New%20folder HTTP/1.1
Connection: Keep-Alive
User-Agent: Microsoft-WebDAV-MiniRedir/10.0.14393
translate: f
Content-Length: 0
Host: 192.168.0.3
Authorization: Basic --redacted-- 

Responses:

HTTP/1.1 404 Not Found
Server: nginx
Content-Type: text/html
Content-Length: 420
Connection: keep-alive
Date: Mon, 19 Dec 2016 11:09:28 GMT
HTTP/1.1 207 Multistatus
Server: nginx
Content-Type: application/xml
Content-Length: 719
Connection: keep-alive
Date: Mon, 19 Dec 2016 11:09:28 GMT
HTTP/1.1 403 Forbidden
Server: nginx
Content-Type: text/html
Content-Length: 423
Connection: keep-alive
Date: Mon, 19 Dec 2016 11:09:28 GMT
HTTP/1.1 403 Forbidden
Server: nginx
Content-Type: text/html
Content-Length: 423
Connection: keep-alive
Date: Mon, 19 Dec 2016 11:09:28 GMT
HTTP/1.1 403 Forbidden
Server: nginx
Content-Type: text/html
Content-Length: 423
Connection: keep-alive
Date: Mon, 19 Dec 2016 11:09:28 GMT
HTTP/1.1 403 Forbidden
Server: nginx
Content-Type: text/html
Content-Length: 423
Connection: keep-alive
Date: Mon, 19 Dec 2016 11:09:28 GMT

Your nginx config looked a little bit diffrent. I recommend you to use the new Drive client: https://www.seafile.com/en/download/

WebDAV has really poor performance as fas as i can say, since we’ve tested it very in detail for a customer.

I am already using the client but I don’t have enough space to everything. This is why I need webdav to work.

This may be due to change of behavior in Win 10 explorer. I remember I tested webdav on Win 10 some time ago. So I’m not sure whether it’s your server’s setting problem or our Dav server. We’ll test again when we have time.

But anyway, I don’t think you can what you want with either WebDav or SeaDrive. Explorer in Win 10 will cache the entire file to local disk first before you can open it. You should get some free space out of your SSD.

I am aware of the caching. I have several hundreds of gigabytes of portable programs. I only need to run a few at any time. Clearing cache when needed is no problem. Please let me know what your test turn up and if there is anything I can do to assist you.

Ok, at htis point i can’ help you anymore. Since you say that other clients work, i think it’s Windows related.