Kodi Community Forum

Full Version: Kodi Leia v18 SFTP and NFS addon auto-enable, when media source exist during upgrade
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
Still no solution, just deafening silence....
(2019-03-26, 17:29)DarthGecko Wrote: [ -> ]Still no solution, just deafening silence....

In case that can help someone: After also wasting a few hours of my life, I eventually managed to get sftp/ssh sources with key pair authentication working, both on Libreelec and OSMC.

What eventually did the trick was to wipe out the content of .ssh/known_hosts (take a backup just in case).
I didn't bother looking at the content difference, but the answer is probably there.

Along the way, I noticed that the sources.xml syntax for sftp has also changed a bit.

It went from:
<path>sftp://username:[email protected]/share/videos/</path>

To
<path>sftp|ssh://username:[email protected]//share/videos/</path>

Both still seem to work at the moment, but I guess it will be more future proof to update it.
(2019-05-02, 09:42)gimmeapill Wrote: [ -> ]
(2019-03-26, 17:29)DarthGecko Wrote: [ -> ]Still no solution, just deafening silence....

In case that can help someone: After also wasting a few hours of my life, I eventually managed to get sftp/ssh sources with key pair authentication working, both on Libreelec and OSMC.

What eventually did the trick was to wipe out the content of .ssh/known_hosts (take a backup just in case).
I didn't bother looking at the content difference, but the answer is probably there.

Along the way, I noticed that the sources.xml syntax for sftp has also changed a bit.

It went from:
<path>sftp://username:[email protected]/share/videos/</path>

To
<path>sftp|ssh://username:[email protected]//share/videos/</path>

Both still seem to work at the moment, but I guess it will be more future proof to update it. 

For people who can't install vfs.sftp from kodi repo on linux, I recompiled it from source and put it in zip file here: https://cloud.p2p.legal/s/yZMs8FL9ExLyPke
(2019-05-02, 09:42)gimmeapill Wrote: [ -> ]
(2019-03-26, 17:29)DarthGecko Wrote: [ -> ]Still no solution, just deafening silence....

In case that can help someone: After also wasting a few hours of my life, I eventually managed to get sftp/ssh sources with key pair authentication working, both on Libreelec and OSMC.

What eventually did the trick was to wipe out the content of .ssh/known_hosts (take a backup just in case).
I didn't bother looking at the content difference, but the answer is probably there.

Along the way, I noticed that the sources.xml syntax for sftp has also changed a bit.

It went from:
<path>sftp://username:[email protected]/share/videos/</path>

To
<path>sftp|ssh://username:[email protected]//share/videos/</path>

Both still seem to work at the moment, but I guess it will be more future proof to update it. 
Deleting .ssh worked for my LibreElec, but not for my Macbook.  Any ideas why Kodi 18 on Mac can't use sftp?  I'm running MacOS 10.13.6.

Here's my relevant kodi.log info (doesn't tell me a lot, hopefully it makes sense to someone else?)
Quote:2019-06-17 07:00:39.578 T:140735968236416   DEBUG: CGUIMediaWindow::GetDirectory (sftp|ssh://USERNAMETongue[email protected]:22//mnt/)
2019-06-17 07:00:39.578 T:140735968236416   DEBUG:   ParentPath = [sources://video/]
2019-06-17 07:00:39.580 T:123145475371008   DEBUG: Thread waiting start, auto delete: false
2019-06-17 07:00:39.582 T:123145475371008   ERROR: GetDirectory - Error getting sftp|ssh://USERNAMETongue[email protected]:22//mnt/
2019-06-17 07:00:39.582 T:123145475371008   DEBUG: Thread waiting 123145475371008 terminating
2019-06-17 07:00:39.586 T:140735968236416   ERROR: CGUIMediaWindow::GetDirectory(sftp|ssh://USERNAMETongue[email protected]:22//mnt/) failed
2019-06-17 07:00:39.587 T:140735968236416   DEBUG: CGUIMediaWindow::GetDirectory (sources://video/)
2019-06-17 07:00:39.587 T:140735968236416   DEBUG:   ParentPath = []
(2019-05-02, 09:42)gimmeapill Wrote: [ -> ]
(2019-03-26, 17:29)DarthGecko Wrote: [ -> ]Still no solution, just deafening silence....

In case that can help someone: After also wasting a few hours of my life, I eventually managed to get sftp/ssh sources with key pair authentication working, both on Libreelec and OSMC.

What eventually did the trick was to wipe out the content of .ssh/known_hosts (take a backup just in case).
I didn't bother looking at the content difference, but the answer is probably there.

Along the way, I noticed that the sources.xml syntax for sftp has also changed a bit.

It went from:
<path>sftp://username:[email protected]/share/videos/</path>

To
<path>sftp|ssh://username:[email protected]//share/videos/</path>

Both still seem to work at the moment, but I guess it will be more future proof to update it. 
Deleting .ssh worked for my LibreElec, but not for my Macbook.  Any ideas why Kodi 18 on Mac can't use sftp?  I'm running MacOS 10.13.6.

Here's my relevant kodi.log info: uyayosivoh.kodi (paste)
Sorry guys, I hadn't subscribed to email notifications and just saw your messages.

Please do not delete the whole .ssh folder - this is where your key pairs live;-)
just the file "known_hosts" should get wiped out: it will get recreated for each of your hosts with a better encryption algorithm on the next connection.
In my case "ecdsa-sha2-nistp256" was upgraded to "ssh-ed25519" - which is apparently the golden standard as of 2019.

I have unfortunately no idea what is going on with your Mac, but it could be that you're missing the Keychain configuration step described here ("Notes for macOS User"): https://medium.com/risan/upgrade-your-ss...e8d60d3c54

And even more unfortunately, it seems that even when it's working, accessing the library via ssh sucks big time when it comes to performance.
My Vero4k (OSMC) is overheating happily when rescaning the shares, or sometimes just playing music, and my old wetek/librelec box doesn't fare much better. In summary: So far the upgrade to Kodi18 was just a pain. Wrecking ssh/sftp support is just ruining the user experience (I have kids and they certainly didn't use such kind words).

All in all, it would have been cleaner from a user experience perspective to discontinue officially the feature rather than leaving it in a half broken state like it is right now (as a linux old timer, I can still not understand how can anyone NOT use ssh/sftp and key pair authentication to access files remotely but that's probably just me...).
Pages: 1 2 3