[RPi4] FTPS not working on LE13 Nightly

    Hello there,

    yesterday I updated my Rpi4b LibreELEC installation to a nightly LE13 build from LE12 and connecting through sftp isnt possible any more. I try to access it through Solid Explorer on my Android Phone and it suddenly stopped working now.

    Is this a known issue / a wanted behaviour?

    Known issue. We have something similar on RPi3 and x86-64:

    Post

    RE: [RPi] FTPS Broken in LE12

    There is a comparison table that indicates which versions of curl, along with their libraries, are used in the different LibreELEC versions. It is evident that under LibreELEC 12.0.1, 12.0.2, and the current nightly-20250415-e25b5e0 (v12.x), ftps does not function.

    LibreELEC Generic.x86_64 and RPi2.arm curl comparison table:
    183

    With the current LibreELEC nightly-20250424-067110d (v13.x), ftps is operational again; however, various elements (folders/files) are constantly being omitted. This renders…
    sittich
    April 25, 2025 at 7:35 PM
    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. Generate a log URL (do not post/upload logs to the forum)

    use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

    Arokhaerr I'm not aware of any noteworthy changes to the SSH server between LE12 and LE13 but perhaps delete any stored profile or connection in the app and recreate in case there are cipher changes. Using a normal computer, check SSH in to prove the SSH service is enabled/running and that password auth is allowed. If yes, perhaps clear any stored connection/profile in the app and recreate. We don't change certs after initial boot but the accepted ciphers can/do change over time (albeit not often).

    Quote from chewitt

    Arokhaerr I'm not aware of any noteworthy changes to the SSH server between LE12 and LE13 but perhaps delete any stored profile or connection in the app and recreate in case there are cipher changes. Using a normal computer, check SSH in to prove the SSH service is enabled/running and that password auth is allowed. If yes, perhaps clear any stored connection/profile in the app and recreate. We don't change certs after initial boot but the accepted ciphers can/do change over time (albeit not often).

    SSH is definately working, maybe its an issue on android. Ill test some things and reply later.