v17 CURL http time out too short
#1
With Kodi 17 beta 6 I have problems accessing my https server.
The server isn't the fastest (Raspi with 2 USB HDDs) so the response time is not that great but the actual file delivery works well for videos. So I'm getting random timeouts accessing my library.
Accessing it via "files" and playing files from there works so a connection is possible. So is there a possibility to increase the wait for a HTTPS response? I know it's a timeout because of this in the log:
Code:
11:09:04.564 T:10188   ERROR: CCurlFile::FillBuffer - Failed: Timeout was reached(28)
11:09:04.565 T:10188   ERROR: CCurlFile::Open failed with code 0 for https://USERNAME:[email protected]:443/serien/
11:09:04.565 T:10188   ERROR: XFILE::CHTTPDirectory::GetDirectory - Unable to get http directory (https://USERNAME:[email protected]:443/serien/)
11:09:04.573 T:10580   ERROR: XFILE::CDirectory::GetDirectory - Error getting https://USERNAME:[email protected]:443/serien/
11:09:04.577 T:10580   ERROR: CGUIMediaWindow::GetDirectory(https://USERNAME:[email protected]:443/serien/) failed


1. Version of Kodi: Kodi 17 beta 6
2. Windows 10 1607
3. CPU/Architecture: Intel Xeon 1230 v3 / Haswell
4. RAM amount: 32GB
5. see above
6. Webserver: Raspi3 + nginx 1.10

The debug log addon doesn't seem to work for me but I can upload a full log if desired.
Reply
#2
you could try if increasing the curlclienttimeout helps:
http://kodi.wiki/view/Advancedsettings.xml#network
Do not PM or e-mail Team-Kodi members directly asking for support.
Always read the Forum rules, Kodi online-manual, FAQ, Help and Search the forum before posting.
Reply
#3
Thanks, increasing the timeout in the Advancedsettings really did help and scanning now worked without a problem.

I guess that the more files there are on my server the longer the response takes so that it worked earlier and now just sometimes got past the timeout.
Reply
#4
Are the disks set to spin down?
That would be a common cause for some accesses to timeout but not others.
Reply
#5
Yes, the USB disks do spin down but even when they are running I get random timeouts.
I don't know if the DNS resolve time accounts to the timeout time, too. But the DNS resolution can take some time, too, as it goes from a "normal" address to a (not so fast) dyndns address.
And the server is https only so the handshake alone takes some time, i guess. Perhaps HTTP2 or a later libcurl could help? On Windows libcurl version 1.48 is used.
Reply

Logout Mark Read Team Forum Stats Members Help
CURL http time out too short0