TeamAmaze / TeamAmaze/AmazeFileManager

Unable to connect with Filezilla using ftps

Open
#3,073 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-FTP Issue-Bug
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

I'm not sure whether it is an actual issue or if I'm doing something wrong, so please advise.

The problem is, I'm unable to connect with Filezilla using secure connection.

I set up a new site in Filezilla Site Manager using details Amaze shows me. The IP address of the device is correct, as it's the same that is assigned to it by the router. Encryption in FZ is set to "Use explicit FTP over TLS if available". Connection mode is set to default. When connection starts, the FZ log show me the following:

Status: Connection established, waiting for welcome message...
Error: Connection timed out after 20 seconds of inactivity
Error: Could not connect to server
Status: Waiting to retry...

It makes another attempt with same messages, and then disconnects.

If in FZ site settings I select "Require explicit FTP over TLS", I get the same result (or, rather, no result). If I select "Require implicit FTP over TLS", I get a warning that this server does not support renewing TLS session for data transfer and insecure connection is established (it connects via ftp, not ftps, if I understand it correctly).

If I uncheck the "Secure connection" setting in Amaze, everything works fine using ftp and default Filezilla settings.

This happens on two tablets: Huawei Matepad T8 (no Google services) and Lenovo Tab M10. Both run Android 10. Amaze was installed from IzzyOnDroid repo, version 3.6.7.

Thank you in advance.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are mentioned. Reproduce the FTPS connection failure with FileZilla using the reported Amaze 3.6.7 settings, then trace the Android app's secure FTP connection handling and compare it with the working plain FTP path; done means explicit FTPS connects successfully without falling back to insecure FTP.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.