Addon FTP accounts failing to connect
AnsweredHi folks,
I have an addon FTP account which is refusing to connect. The FTP client transcript would indicate that there's not a firewall issue and it doesn't seem to matter what I set the remote path to. I'm certain that the hostname, username, and password are all correct as I've created and deleted the account several times trying to get this working.
The account in question has a path of /home/[main account username]/public_html, which the transcript is saying doesn't exist when I set it as the remove path.
The FTP server in use is Pure-FTPd and 'Broken Clients Compatibility' is enabled.
I've tried setting up a second addon FTP account and the issue persists.
Please see the transcript below.
**********
Date/Time: 2024-10-27 21:15:18 +0000
1: Transmit 5.10.4 (arm64) Session Transcript [Version 14.7 (Build 23H124)] (27/10/2024, 21:15)
1: LibNcFTP 3.2.3 (July 23, 2009) compiled for UNIX
1: 220: --------- Welcome to Pure-FTPd [privsep] [TLS] ----------
1: You are user number 1 of 50 allowed.
1: Local time is now 21:15. Server port: 21.
1: This is a private system - No anonymous login
1: IPv6 connections are also welcome on this server.
1: You will be disconnected after 15 minutes of inactivity.
1: Connected to [main account domain].
1: Cmd: USER [ftp username]@[main account domain]
1: 331: User [ftp username]@[main account domain] OK. Password required
1: Cmd: PASS xxxxxxxx
1: 230: OK. Current restricted directory is /
1: Cmd: TYPE A
1: 200: TYPE is now ASCII
1: Logged in to [main account domain] as [ftp username]@[main account domain].
1: Cmd: SYST
1: 215: UNIX Type: L8
1: Cmd: FEAT
1: 211: Extensions supported:
1: UTF8
1: EPRT
1: IDLE
1: MDTM
1: SIZE
1: MFMT
1: REST STREAM
1: MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
1: MLSD
1: PRET
1: AUTH TLS
1: PBSZ
1: PROT
1: TVFS
1: ESTA
1: PASV
1: EPSV
1: ESTP
1: End.
1: Cmd: OPTS UTF8 ON
1: 504: Unknown command
1: Cmd: OPTS UTF-8 ON
1: 504: Unknown command
1: Cmd: PWD
1: 257: "/" is your current location
1: Cmd: CWD /home/[main account username]/public_html
1: 550: Can't change directory to /home/[main account username]/public_html: No such file or directory
1: Cmd: CWD /home/[main account username]
1: 550: Can't change directory to /home/[main account username]: No such file or directory
1: Cmd: EPSV
1: 500: Unknown command
1: Cmd: PASV
1: connect failed: Operation timed out.
1: Retrying PASV mode (2 tries left).
1: Cmd: EPSV
1: 500: Unknown command
1: Cmd: PASV
1: connect failed: Operation timed out.
1: Retrying PASV mode (1 try left).
1: Cmd: EPSV
1: 500: Unknown command
1: Cmd: PASV
1: connect failed: Operation timed out.
1: Falling back to PORT instead of PASV mode.
1: Connection falling back to port (PORT) mode.
1: Cmd: LIST -a
Any ideas? Thanks in advance :)
Cheers,
RS
-
Hey there! Have you ensured the passive port range is opened in the server's firewall? Details on adjusting that in various firewall tools can be found here:
https://docs.cpanel.net/knowledge-base/ftp/how-to-enable-ftp-passive-mode/#configure-the-firewall
Can you try that and see if that changes the behavior?
0 -
Hi cPRex,
Port 21 (the port the FTP client is trying to connect on) is definitely open.
Cheers,
RS0 -
Thanks for confirming port 21 is open. While that is the standard port for FTP connections, I was actually interested in the passive FTP port range documented in that link I sent, which uses a different range of ports in the firewall on the server. That is what the error log is referring to with those "PASV" entries.
Can you check that port range as well?
0 -
Hi cPRex,
My apologies, it's been one of those days!
I've added 49152:65534 to TCP_IN in my CSF configuration and the account is now connecting as expected.
Thanks for your assistance :)
Cheers,
RS0 -
I'm glad to hear that's all it took!
0
Please sign in to leave a comment.
Comments
5 comments