Member Avatar for Teddy112

Hi,
I am accessing a FTP over SSL server with port no 990 in Implicit mode on Linux through File Zilla client on windows.It is connected successfully but it is not listing the directory there and giving an error in logs "226 Transfer done (but failed to open directory).".
Can anyone help me that which command can help me to access the FTP over SSL directory location.

Thanks in Advance

Edited by Teddy112
  • 2 Contributors
  • 2 Replies
  • 331 Views
  • 20 Hours Discussion Span
  • Latest Post Latest Post by Teddy112

Dani AI

Generated

Brief diagnosis referencing the thread: has a working FTPS login but FileZilla fails to list the remote directory; ’s credential check shows authentication is not the blocker. When login works but listings/transfers fail the root cause is almost always the FTP data channel (passive vs active + firewall/NAT), a TLS/data-channel interoperability setting, or server-side permissions.

Quick checklist (most likely causes)

  • Client is using active mode or the server is returning a private IP/closed ports for PASV; forcing passive mode in the client often fixes it. (support.plesk.com)
  • Server passive port range or advertised passive address is not configured or allowed through the firewall/NAT; the server must hand out a reachable external IP and a limited port range that is opened on the host firewall/router. (docs.redhat.com)
  • TLS session-resumption mismatch: some FTPS servers require the TLS session to be reused for the data connection; if the client does not resume the session the server will drop the data channel (look for “TLS session … has not resumed” in logs). That setting exists in common servers (vsftpd, FileZilla Server) and may need adjusting. (access.redhat.com)

Practical next steps (in order)

  • In FileZilla Site Manager → Transfer Settings set Transfer mode to Passive and test the listing. (support.plesk.com)
  • If still failing, configure a passive port range and external PASV address on the server (example for vsftpd): 
pasv_enable=YES
pasv_min_port=30000
pasv_max_port=30100
pasv_address=203.0.113.45

Open those ports plus the FTPS control port in the server firewall/NAT. (docs.redhat.com)

  • Check for TLS session errors in the server log (messages like “450 TLS session … has not resumed”); either enable TLS session reuse on the client side or, if absolutely necessary and understood, disable the server’s “require session resumption” option as a temporary compatibility step (this reduces a security guard and should be avoided if possible). (access.redhat.com)

Diagnostics to gather

  • Client transcript showing PASV/227 response (check whether the server IP in 227 is private), server FTP logs, and an openssl s_client test of control TLS (implicit vs explicit) to confirm TLS handshake behavior. RFC 4217 explains FTPS control/data handling if deeper protocol detail is needed. (rfc-editor.org)

Follow that sequence: passive-mode check → passive-port + NAT/firewall → TLS session-resumption check → filesystem/permission checks. Each step rules out a major class of causes and usually finds the failure quickly.

Recommended Answers

All 2 Replies

Member Avatar for rubberman

Did you log into the ftp server with valid user credentials?

Member Avatar for Teddy112

yes when i give give valid credentials then i become logged in but not able to access the location.Perhaps a permission issue....not sure

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.