Solved Unable to stream media to local device
#1
I run Kodi on a headless Arch Linux installation, and updated Kodi to v18.1 a few weeks ago (used v17 before that). After the upgrade, I'm not able to stream any media from it anymore. All settings are correct (UPnP etc). I use Yatse on my Android devices, and with v17 I could stream everything to my device. But after the upgrade it just fails. I tried streaming from the web interface to my browser (Chorus), but it fails there to, just get The connection was canceled (the url is http://kodi:8080/vfs/%2fhome%2fkodi%2f.....). Can't really find anything useful in the logs that explains it.

I tried searching for the problem, but can't find anything about it (just get lots of irrelevant search results).

Any ideas?
Reply
#2
In Leia some of the support for virtual file systems was moved out to binary add-ons, which may be influencing what you're seeing here (based on your URL anyway).

Normally they're installed from the official repo under the virtual file systems section, but I'm not sure on Linux if you'll need to manually build them yourself or install them externally (I know you do for other binary add-ons like PVR ones, but I'm not sure in this case - I'm not a Linux expert).
| Banned add-ons (wiki) | Forum rules (wiki) | VPN policy (wiki) | First time user (wiki) | FAQs (wiki) | Troubleshooting (wiki) | Add-ons (wiki) | Free content (wiki) | Debug Log (wiki) | Free Movies/TV Shows |
Reply
#3
I did compile the kodi-addon-vfs-sftp package for Arch, but still no success. Not sure if it's the right package to handle it. This function should be a core function imo. The UPnP is pretty useless without it.

[]EDIT Can't really find any other related packages, the others are vfs.rar, vfs.sacd and vfs.libarchive.
Reply
#4
The majority of people probably don't use it (I don't), which is why it was taken from core into binary add-on to help streamline the code, so only people who need it have it.

Just to cover the basics, it may be worth double-checking the addon is enabled and if necessary configured (I don't know if it needs anything in that way or not).

If not maybe try libarchive, but it would depend a lot on your exact server-end configuration as to how things are stored and supplied.
| Banned add-ons (wiki) | Forum rules (wiki) | VPN policy (wiki) | First time user (wiki) | FAQs (wiki) | Troubleshooting (wiki) | Add-ons (wiki) | Free content (wiki) | Debug Log (wiki) | Free Movies/TV Shows |
Reply
#5
(2019-03-20, 15:22)DarrenHill Wrote: The majority of people probably don't use it (I don't), which is why it was taken from core into binary add-on to help streamline the code, so only people who need it have it.

Just to cover the basics, it may be worth double-checking the addon is enabled and if necessary configured (I don't know if it needs anything in that way or not).

If not maybe try libarchive, but it would depend a lot on your exact server-end configuration as to how things are stored and supplied.
Make sense, doesn't really matter how the functions are incorporated to the system as long as it works Smile The only thing that doesn't really make sense is that you can enable UPnP server in the settings, but not use it until appropriate addon is installed, shouldn't streaming media to other devices be a part of UPnP/DLNA framwork iself? Else the setting doesn't make sense, or am i missing something?

Yep, the addon itself is enabled (missed that at first). But can't stream anything from Kodi using UPnP still (same with both Yatse & Chorius), seems that the URL pointing to the media is invalid or can't be reached. I looked at the addon, but can't see anything related to settings (nor are there any files from the package itself to configure, just the addon xml and some library files).

Everything is stored on the local media computer itself for now (planing of setting up a server, but that's still in the future). It's stored on Linux ext4 filesystem.

Comparing to v17, how did the UPnP work there? Was it "vfs-sftp" that handled it internally or how does UPnP/DLNA handle the URI itself?
Reply
#6
Saw this answer from the developer of Yatse.
 
Quote:[630] HEAD http://192.168.1.3:8189/vfs/%2Fshare%2FP...(2018).mkv[630] HTTP FAILED: java.io.IOException: unexpected end of stream on Connection{192.168.1.3:8189, proxy=DIRECT hostAddress=/192.168.1.3:8189 cipherSuite=none protocol=http/1.1}

Your Kodi does not properly answer on a simple HEAD query, it’s internal to Kodi.
Reply
#7
After some heavy digging and trying to find out how VFS works, I found the solution to what made it fail.

I seems that you have to add the path that UPnP trying to access in the file manager. In my case the link was http://kodi:8080/vfs/home/kodi.. That means that you must add that path to Kodi VFS (in my case, the folder containing the home folder). In the file manager, I just added a new source pointing to my root file system (/ in linux, because the link starts with /home/kodi/).

After I added the source, the streaming worked.
Reply
#8
Glad to hear it's resolved for you, and thanks for the information on the solution.

In Krypton and earlier the archive handling was in the Kodi core. It's only been split out since Leia.
| Banned add-ons (wiki) | Forum rules (wiki) | VPN policy (wiki) | First time user (wiki) | FAQs (wiki) | Troubleshooting (wiki) | Add-ons (wiki) | Free content (wiki) | Debug Log (wiki) | Free Movies/TV Shows |
Reply
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
Unable to stream media to local device00