[bleze]

Hi

FTPS has been working fine prior to upgrade to Kodi 18. I first noticed issue on Shield which was auto updated. Then today I tried testing this on Windows and got the following errors in log. Connection works fine in FTP clients like FileZilla.

Code:


10:41:46.755 T:4100   ERROR: CCurlFile::FillBuffer - Failed: SSL connect error(35)
10:41:46.755 T:4100   ERROR: CCurlFile::Open failed with code 0 for ftps://USERNAME:[email protected]:21/:
10:41:46.755 T:4100   ERROR: XFILE::CDirectory::GetDirectory - Error getting ftps://USERNAME:[email protected]:21/|auth=TLS


Known issue or do I need to change something in my source?

ftps://<user>:<pass>@<ip>:<port>/<path>|auth=TLS

Thanks

[blunden]

It seems it doesn't like the |auth=tls part in Kodi 18. Unencrypted FTP seems to work still.

[bleze]

Thanks for checking this.

I went to trac but cannot find any tickets about this issue, nor do I have rights to add new tickets, so hopefully someone will see this thread and look it to it.

[Karellen]

I went to trac but cannot find any tickets

We don't use Trac anymore. We use github... https://github.com/xbmc/xbmc/issues

[bleze]

I see. I have created a ticket on github instead

https://github.com/xbmc/xbmc/issues/15513

[bleze]

After thought...

Actually the FTP support in Kodi would like some love. A few ideas;

1. Allow more than one connection to the same FTP server using a connection pool. Currently while scanning for new content, you cannot do anything else. NFS or SMB does not have this imitation.
2. The GUI for adding FTP sources could have properties for the secure stuff instead of having to edit behind the scenes xml files. This will give a better user experience and not be a error prone.

[blunden]

After thought...

Actually the FTP support in Kodi would like some love. A few ideas;

1. Allow more than one connection to the same FTP server using a connection pool. Currently while scanning for new content, you cannot do anything else. NFS or SMB does not have this imitation.
2. The GUI for adding FTP sources could have properties for the secure stuff instead of having to edit behind the scenes xml files. This will give a better user experience and not be a error prone.

Maybe you should clarify in your issue that it only affects encrypted FTPS, not regular FTP.