So I finely got Stalker working in Kodi after the whole serial number fiasco. It was working just fine for a couple of days now all of a sudden I cannot get Stalker to work as I am getting an error "IncompleteRead(7346 bytes read, 513 more expected)". I can get all the way to the point of selecting "All" or "VoD", "Entertainment", "Science", etc. but when I select an option such as "All" that's when the "working" box pops up and spins for about 30 seconds and then pops up this error. What's all that about and how do I fix yet another issue with Stalker/Kodi?
IncompleteRead error in Kodi
- Thread starter PayPerView
- Start date
This indicates an issue with your internet connection or network. Your loosing data. What it is telling you that it is reading data from the server and it is expecting 7346 but the connection dropped/timed out and it had another 513 to go to complete the read. This is being reported by python and has nothing to do with the Stalker Client.
Try resetting your modem/router. Make sure you don't have torrent running or anything else that might be eating your bandwidth.
Try resetting your modem/router. Make sure you don't have torrent running or anything else that might be eating your bandwidth.
Then I am at a loss on how to correct this issue. I have rebooted the modem and the router and I still get the same error. I have no issues at all with any other service within Kodi or any other web service; just Stalker. I pull up Kodi on my Android phone and am able to use Stalker under the same exact settings as my computer through the same router/modem connection.
I have searched around Kodi looking for Python but am unable to find it. Perhaps there is a setting within it that I can change to allow for more time before it times out?
I have searched around Kodi looking for Python but am unable to find it. Perhaps there is a setting within it that I can change to allow for more time before it times out?
That is possible I had just updated the antivirus. It almost seemed like a firewall issue, so the antivirus very likely could have been the issue. It seems to be working now although I made no adjustments to anything.