FTP - The remote host actively refused the attempt to connect to it

can no longer FTP to server?

this is my FTP local error log ' [7/29/2014 7:08:57 PM] Connecting to FTP server... (ip = ERROR:> [7/29/2014 7:08:58 PM] The remote host actively refused the attempt to connect to it. 1) Verify that the destination server name or IP address is correct 2) Verify that the connection port number is correct (under Site Settings | Type tab). 3) The remote server may be temporarily or permanently inaccessible (try again later). 4) Verify that you have chosen the right protocol (SSH2, SSL, FTP, etc.) and have setup all required options for that protocol. 5) Verify that the destination IP address and port numbers are correct. 6) The remote server may be refusing multiple connections from the same client. Try using only one connection thread when connecting to this particular server (Site Settings | Options). 7) Try pinging the address. 8) If you are using a router, verify the router is up and running (check by pinging it and then ping an address outside of the router). 9) Do a traceroute to the destination to verify all routers along the connection path are operational. 10) Verify that your subnet mask is setup properly. 11) Verify that your local software or hardware firewall is not blocking outbound connections originating from CuteFTP. 12) Verify that your anti-virus software is not at fault (try disabling it).'



i poked around the site/settings but have no clue where to start..... i can SSH but not FTP SFTP

Howdy -- is ProFTPd running on your server?

You can verify that it's running with the following command:

ps auxw | grep -i proftp

Also, what is the output of this command:

rpm -qa | grep -i proftp

this 'root 30696 0.0 0.0 103244 880 pts/0 S+ 23:25 0:00 grep -i proftp '

and proftpd-1.3.3g-4.el6.x86_64


ok i found the proftp modual config, clicked 'start server' and poof...

so the question now is.. how and why did it stop how can i make sue it stays running?

Looks like you did indeed fix it! Yeah for some reason it wasn't running.

It's difficult to say why that might be; Linux services are pretty stable, and don't typically crash.

However, if the server is low on RAM, the Linux kernel would kill services in order to free up RAM.

Is your server perhaps low on RAM? You can determine that by running this command:

free -m

Also, you may want to review the output of dmesg | tail -50 to see if there are any reports of processes being killed off.

server has Real memory 16.59 GB total, 1.70 GB used of RAM.... so dont think that is an issue ;)

Yeah it does appear that you have plenty of memory :-)

You may want to run "dmesg | tail -50" anyhow, just in case it shows any relevant messages.

You also may want to review /var/log/messages and /var/log/proftpd/proftpd.log to see if there are any clues in the logs, near the time when you noticed the service being down.