Kodi Community Forum
Solved WebDav - not working on Kodi 19 (Android) - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228)
+---- Thread: Solved WebDav - not working on Kodi 19 (Android) (/showthread.php?tid=367308)



WebDav - not working on Kodi 19 (Android) - daniel.delillo - 2022-03-04

I'm at 2300 movies on a W10 1511 PC with IIS for WebDav / FTP services.  On the main PC Kodi scans without problems, but on my android devices it's failing to update the library nicely.

Changing IIS authentication from basic to NTLM authentication seems to fix the issue for android 19 builds.  Solved... thanks!


RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - Klojum - 2022-03-04

(2022-03-04, 19:10)daniel.delillo Wrote: Also is there any way to speed up the process, it takes about 1.5hr to scan the library from a Fire Stick

I don't have one, but AFAIK the Firestick does not have the fastest of CPUs and storage, and it's using wifi I think? So saving thumbnails locally alone can take extra time.
Perhaps you can provide a debug log (wiki) of a scrape session. Perhaps we can spot something.

Why WebDAV/FTP? Is your Kodi client located half around the world? And Windows 10 build 1511 is from around October 2017 if I'm correct...


RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - daniel.delillo - 2022-03-05

I'm using W10 1511 because of its compatibility for cable cards on Windows Media Center.  That said, I have net framework 4.8 installed, so it handles all current applications.

I'm using FTP & WebDav for outside library viewing on my phone and other devices.

Yes, the fire stick is not fast, but it works.  I just need to be able to update my library without having to redo Kodi's source from scratch.

Here's the log file kodi.log

Thanks for the help Smile

Looking further, it looks like WebDav may not be supported in Kodi 19, DAVS is not supported?


RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - wsnipex - 2022-03-06

davs is supported. Enable debug logging and provide a new log, preferably on paste.kodi.tv


RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - daniel.delillo - 2022-03-06

WebDav may work right on the PC, but on android it's been broken for a long while for me.  I normally just let movies build up in a non-index source, because I don't want to deal with rebuilding 10x android based Kodi devices from scratch.

Just like the guy said in this thread Davs not supported? it will do the initial scrape and then never updates afterwards.  I find this true on fire sticks and android phones using both 32 & 64bit versions.

Here's the log on paste.kodi.tv kodi.log 

If I perform the update from movie's option section, it does nothing.  I have to do it from the video file section to even get it going and then after a min or so at 0% it just finishes and finds nothing new.

There looks to be something pretty wrong with Kodi 19, because I don't remember this in past versions of Kodi.  I'll try Kodi 18 later today as I have 2 new items to scan to the library.


RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - wsnipex - 2022-03-06

2022-03-05 07:03:03.963 T:16097 ERROR <general>: CCurlFile::Exists - Failed: Unsupported protocol(1) for dav://USERNAMETongue[email protected]:80/hdd/Movies/
2022-03-05 07:03:03.963 T:16097 WARNING <general>: Process directory 'dav://USERNAMETongue[email protected]:80/hdd/Movies/' does not exist - skipping scan.

did you try with davs://?


RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - daniel.delillo - 2022-03-06

No, because I would need to create a self signed certificate and it's just one more thing to manage on multiple devices. Is there a reason it would with 443 and not port 80?


RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - wsnipex - 2022-03-06

depends on the server. does it support plain dav? Sadly we still don't see the actual cause in the log, so try enabling curl component logging in addition to normal debug


RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - daniel.delillo - 2022-03-06

(Update) - So I just tried 18.9 on my android phone and my DAV library updates just fine with no changes to my IIS server.  It grabbed the new movies without any problems.  There's definitely something wrong with Kodi 19, because as soon as I updated to any version of 19 it fails to update.  Can you please see why 19 is broken for android?  Thanks.

(Earlier Post)
On 19 - here's the updated log file you wanted.
The log is too big for past.kodi.tv, so here's a onedrive link.
kodi.log

It's just a plain IIS DAV setup in windows.  The simple problem is it work fine on my Windows PCs and not on android devices.

It will scrape the library correctly on the 1st pass with android devices and then fails to do a 2nd pass.  I just don't understand why this is broken for so many builds updates.


RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - wsnipex - 2022-03-06

Quote:2022-03-06 13:47:24.040 T:20013   DEBUG <general>: Curl:Big Grinebug - HEADER_OUT: PROPFIND /hdd/Movies/101%20Dalmatians%20(1996)/ HTTP/1.1
2022-03-06 13:47:24.041 T:20013   DEBUG <general>: Curl:Big Grinebug - HEADER_OUT: Host: some.server
2022-03-06 13:47:24.041 T:20013   DEBUG <general>: Curl:Big Grinebug - HEADER_OUT: Authorization: Basic ***************
2022-03-06 13:47:24.041 T:20013   DEBUG <general>: Curl:Big Grinebug - HEADER_OUT: User-Agent: Kodi/19.3 (Linux; Android 7.1.2; AFTMM Build/NS6281) Android/7.1.2 Sys_CPU/armv7l App_Bitness/32 Version/19.3-(19.3.0)-Git:20211024-49a04cd6a7
2022-03-06 13:47:24.041 T:20013   DEBUG <general>: Curl:Big Grinebug - HEADER_OUT: Accept: */*
2022-03-06 13:47:24.041 T:20013   DEBUG <general>: Curl:Big Grinebug - HEADER_OUT: Accept-Encoding: deflate, gzip
2022-03-06 13:47:24.041 T:20013   DEBUG <general>: Curl:Big Grinebug - HEADER_OUT: Accept-Charset: UTF-8,*;q=0.8
2022-03-06 13:47:24.041 T:20013   DEBUG <general>: Curl:Big Grinebug - HEADER_OUT: depth: 0
2022-03-06 13:47:24.041 T:20013   DEBUG <general>: Curl:Big Grinebug - TEXT: Received HTTP/0.9 when not allowed
2022-03-06 13:47:24.042 T:20013   DEBUG <general>: Curl:Big Grinebug - TEXT: Closing connection 5
2022-03-06 13:47:24.042 T:20013   ERROR <general>: CCurlFile::Exists - Failed: Unsupported protocol(1) for dav://USERNAMETongue[email protected]:80/hdd/Movies/101%20Dalmatians%20(1996)/
check the server logs. It claims kodi sends http 0.9 while http 1.1 was used.


RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - daniel.delillo - 2022-03-06

That's why I'm coming to you guys.  updated post below


RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - daniel.delillo - 2022-03-07

Here's what it looks like on Windows 19.4 Build, which works fine.  There's clearly something wrong with the android build of 19 and IIS 10 DAV Support, because it works fine on the 18.9 build for android too.
Quote:2022-03-06 17:13:48.232 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: HEAD /hdd/Movies/101%20Dalmatians%20(1996)/.nomedia HTTP/1.1
2022-03-06 17:13:48.232 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: Host: danspcpitstop.com
2022-03-06 17:13:48.232 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: User-Agent: Kodi/19.2 (Windows NT 10.0.22000.434; Win64; x64) App_Bitness/64 Version/19.2-(19.2.0)-Git:20211006-52c19a0728
2022-03-06 17:13:48.232 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: Accept: */*
2022-03-06 17:13:48.232 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: Accept-Encoding: deflate, gzip, br
2022-03-06 17:13:48.232 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: Accept-Charset: UTF-8,*;q=0.8
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Mark bundle as not supporting multiuse
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - HEADER_IN: HTTP/1.1 401 Unauthorized
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - HEADER_IN: Content-Length: 1293
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - HEADER_IN: Content-Type: text/html
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - HEADER_IN: Server: Microsoft-IIS/10.0
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - HEADER_IN: WWW-Authenticate: Basic realm="danspcpitstop.com"
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - HEADER_IN: Date: Sun, 06 Mar 2022 22:13:47 GMT
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Connection #34 to host danspcpitstop.com left intact
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Issue another request to this URL: 'http://danspcpitstop.com:80/hdd/Movies/101%20Dalmatians%20(1996)/.nomedia'
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Found bundle for host danspcpitstop.com: 0x2613db56b30 [serially]
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Can not multiplex, even if we wanted to!
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Re-using existing connection! (#34) with host danspcpitstop.com
2022-03-06 17:13:48.234 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Connected to danspcpitstop.com (96.225.99.65) port 80 (#34)
2022-03-06 17:13:48.235 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Server auth using Basic with user 'wmc-u2'
2022-03-06 17:13:48.235 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: HEAD /hdd/Movies/101%20Dalmatians%20(1996)/.nomedia HTTP/1.1
2022-03-06 17:13:48.235 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: Host: danspcpitstop.com
2022-03-06 17:13:48.235 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: Authorization: Basic *******
2022-03-06 17:13:48.235 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: User-Agent: Kodi/19.2 (Windows NT 10.0.22000.434; Win64; x64) App_Bitness/64 Version/19.2-(19.2.0)-Git:20211006-52c19a0728
2022-03-06 17:13:48.235 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: Accept: */*
2022-03-06 17:13:48.235 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: Accept-Encoding: deflate, gzip, br
2022-03-06 17:13:48.235 T:11512   DEBUG <general>: Curl:: Debug - HEADER_OUT: Accept-Charset: UTF-8,*;q=0.8
2022-03-06 17:13:48.237 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Mark bundle as not supporting multiuse
2022-03-06 17:13:48.237 T:11512   DEBUG <general>: Curl:: Debug - TEXT: The requested URL returned error: 404 Not Found
2022-03-06 17:13:48.237 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Closing connection 34
2022-03-06 17:13:48.241 T:11512   DEBUG <general>: Curl:: Debug - TEXT: RESOLVE danspcpitstop.com:80 is - old addresses discarded!
2022-03-06 17:13:48.241 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Added danspcpitstop.com:80:96.225.99.65 to DNS cache
2022-03-06 17:13:48.241 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Hostname danspcpitstop.com was found in DNS cache
2022-03-06 17:13:48.241 T:11512   DEBUG <general>: Curl:: Debug - TEXT:   Trying 96.225.99.65:80...
2022-03-06 17:13:48.241 T:11512   DEBUG <general>: Curl:: Debug - TEXT: TCP_NODELAY set
2022-03-06 17:13:48.243 T:11512   DEBUG <general>: Curl:: Debug - TEXT: Connected to danspcpitstop.com (96.225.99.65) port 80 (#35)



RE: WebDav - Scanning movies using Local Information only - (Slow / Not working) - daniel.delillo - 2022-03-07

Changing IIS authentication from basic to NTLM authentication seems to fix the issue for android 19 builds.  Solved... thanks!


WebDav - not working on Kodi 19 (Android) - Klojum - 2022-03-07

Thread marked solved.


RE: WebDav - not working on Kodi 19 (Android) - marantz - 2022-11-29

this seems to happenening with libreelec 11 and nginx now, no option to switch to NTLM.

https://forum.kodi.tv/showthread.php?tid=370584&pid=3119875#pid3119875

edit: I think its becouse on windows it sends header depth 1 and on libreelec 11 its sends header 0, when doing this manually you need depth 1