Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
Start simple, look at the firewall settings, look at the netstat -anp output, whether your ftp is there or not.
Is the path to the ftp folder in the config? And then the server can connect, but does not know which directory to display.
Switch filezilla to another mode (active / passive) - will it work?
on the server:
should show the ftpd process or whatever you have, and the addresses it listens on. should be 0.0.0.0:21 or your ip to which you connect with ftp client.
on the server, run the ftp client and connect with the address that exactly happens to be the ftp daemon. The easiest option is to put midnight commander to run it and enter the command in it (assume that the server listens to 0.0.0.0, and therefore 127.0.0.1):
if successful, you will see the ftp server directory.
should show the rules from which it follows that port 21 is accepted on the desired interface from the desired client IP. If a rule is written for port 21 (it is better to write it), you will see a packet counter. If you tried to connect from the client since the restart of iptables, the counter should be non-zero.
add the ip_nat_ftp module and restart IPTABLES,
see what's happening with AppArmor, it can also block access.
Ubuntu doesn't usually use SELinux by default, but it's worth checking.
If enabled, you can temporarily disable it and try to connect again.
Logs, favorite admin reading:
# cat /var/log/имя лога ftp сервера | grep -i 'ftp'
# cat /var/log/kern.log
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question