WebDav on Windows 10 cant upload Files (0x80070032) files are landing in Trash

I'm actually surprised that you managed to mount at all using the Windows' own quirky WebDAV support.

The official connection URL is:

net use X: \\demo.filerun.co@SSL\dav.php\@Home\

The one you use is dedicated to the Nextcloud apps, and there might be non standards-compliant behaviors in the future.

Uploading still doesn't work (technically it works, the file gets uploaded, then deleted, by Windows, as you can notice in the FileRun user activity log) but we'll look into it.

In the meantime, I suggest using a third-party tool, such as Netdrive or Webdrive for mounting FileRun as a Windows drive.

btw mcrypt is not installed (also showed up while setup). But what wonders me is: 

Thanks for pointing it out. It was probably forgotten in the installer, although FileRun doesn't need or use it.

For windows users a fair solution may be to enable webdav at server level. In my case enabling webdisk for the concerning users in cPanel was sufficient to provide them with read/write webdav access, it couldn't be simpler.

Ok thank you, I solved my problems with FileRun using NetDrive.

There I just connectet to "https://domain.tld/dav.php/@Home" and everything worked fine!

map filerun webdav to windows 10 (copyright: propi62) ;)

1. rightclick in free space in my computer

2. add webadress

3. 

https://www.your-url.com/files/dav.php/%40Home/
(%40 is the @ sign)

Thank you for the information, we've added this method to the documentation: http://docs.filerun.com/webdav

Unfortunately it still does not seem to work uploading files using Windows 10 explorer. The culprit seems to be a call to PROPPATCH that returns a 501 error from Apache. Windows then deletes the uploaded file directly after this failed request. From my Apache log:

nnn.nnn.nnn.nnn - user [07/Mar/2019:19:53:28 +0000] "PROPFIND /dav.php/%40Home HTTP/1.1" 207 2604
nnn.nnn.nnn.nnn - user [07/Mar/2019:19:53:28 +0000] "PROPFIND /dav.php/%40Home/file.txt HTTP/1.1" 404 410
nnn.nnn.nnn.nnn - user [07/Mar/2019:19:53:28 +0000] "PUT /dav.php/%40Home/file.txt HTTP/1.1" 201 406
nnn.nnn.nnn.nnn - user [07/Mar/2019:19:53:29 +0000] "LOCK /dav.php/%40Home/file.txt HTTP/1.1" 200 760
nnn.nnn.nnn.nnn - user [07/Mar/2019:19:53:29 +0000] "PROPPATCH /dav.php/%40Home/file.txt HTTP/1.1" 501 400
nnn.nnn.nnn.nnn - - [07/Mar/2019:19:53:29 +0000] "HEAD /dav.php/%40Home/file.txt HTTP/1.1" 401 573
nnn.nnn.nnn.nnn - user [07/Mar/2019:19:53:29 +0000] "HEAD /dav.php/%40Home/file.txt HTTP/1.1" 200 465
nnn.nnn.nnn.nnn - user [07/Mar/2019:19:53:29 +0000] "PUT /dav.php/%40Home/file.txt HTTP/1.1" 204 393
nnn.nnn.nnn.nnn - user [07/Mar/2019:19:53:30 +0000] "PROPPATCH /dav.php/%40Home/file.txt HTTP/1.1" 501 400
nnn.nnn.nnn.nnn - user [07/Mar/2019:19:53:30 +0000] "DELETE /dav.php/%40Home/file.txt HTTP/1.1" 204 546

Is there any way to debug what causes this error? Apache error log is empty, so is PHP error log. Filerun log just says the file failed to upload.

Hello. I know this thread is too old but maybe you could find this information useful. I'm writing a webdav server and spent lots of hours trying to make it work with Windows10 and had the same problem with WEBDAV: After Windows uploads a file, it deletes it and reports an error. Well, what I've found was an error in my XML response to the PROPPATCH method that not was closing all opened tags, after I fixed that, Windows started to work like if it were a local drive, I just uploaded a folder with more than 2000 files/folders and a 2.8GB iso file.
In other words: When you have a problem with WebDav in Windows, its very likely that the problem is an error in your xml response.Unfortunately, Windows is not helpful to report what exactly is happening.

what exactly did you change in the windows installation that is working ok now? is it easy to implement on all Filerun users' computers?

Dump of request and response (have the same problem):

Request:

PROPPATCH <a href="https://[REDACTED]/dav.php/%40Home/%D0%90%D0%B2%D0%B4%D0%BE%D0%BD%D0%B8%D0%BD%20%D0%A1.%D0%92..jpg" class="redactor-autoparser-object">https://[REDACTED]/dav.php/%40Home/%D0%90%D0%B2%D0%B4%D0%BE%D0%BD%D0%B8%D0%BD%20%D0%A1.%D0%92..jpg</a> HTTP/1.1
Cache-Control: no-cache
Connection: Keep-Alive
Pragma: no-cache
Content-Type: text/xml; charset="utf-8"
User-Agent: Microsoft-WebDAV-MiniRedir/10.0.18363
If: (<5f401544e6b94>)
translate: f
Content-Length: 443
Host: [REDACTED]
Authorization: Basic [REDACTED]

<?xml version="1.0" encoding="utf-8" ?><d:propertyupdate xmlns:d="DAV:" xmlns:z="urn:schemas-microsoft-com:"><d:set><d:prop><z:win32creationtime>Fri, 21 Aug 2020 18:41:08 GMT</z:win32creationtime><z:win32lastaccesstime>Fri, 21 Aug 2020 18:41:08 GMT</z:win32lastaccesstime><z:win32lastmodifiedtime>Fri, 21 Aug 2020 18:41:08 GMT</z:win32lastmodifiedtime><z:win32fileattributes>00002020</z:win32fileattributes></d:prop></d:set></d:propertyupdate>

Response:

HTTP/1.1 501 Not Implemented
Content-Length: 0
Content-Type: text/html; charset=UTF-8
Date: Fri, 21 Aug 2020 18:41:09 GMT
Server: Apache/2.4.25 (Debian)
X-Webdav-Status: 501 Method Not Implemented

May be FileRun does not understand this <Win32CreationTime> (and other win32-) tags?

FileRun doesn't use the PROPATCH method. We can try to make it so that the command looks successful.

Hi Vlad R, your last comment was 5 month ago. My installed Filerun (on Docker) is Software-Version 2020.11.21, but today my Win 10 WebDAV connection also have the same error like at the start here.

For so much things it would be realy nice, if a nativ WebDAV connection over Windows Explorer would go.

Hi Vlad,

Could you please let me know what webdav methods are implemented in FileRun free and enterprise editions exactly?

WebDAV (COPY, LOCK, MKCOL, MOVE, PROPFIND, PROPPATCH, UNLOCK)

KR/Zoltan

A FileRun update that fixes compatibility with Windows Explorer's WebDAV support is now ready to be applied from the control panel of your installation.

https://docs.filerun.com/updating