Only ‘PORT’ data connection ftp protocol will work on my server I’ve checked in the server settings and in the FTP server and says PASV use defualt any ideas?
Please elaborate “will not work”, what happens when you try passive mode? What errors does the client and ProFTPD log show?
Also, check out the FAQ entry here titled “FTP Service Isn’t working”, it contains a fix for some common problems:
Just tried running modprobe ip_conntrack_ftp
However I got…
FATAL: Error inserting nf_conntrack_ftp (/lib/modules/220.127.116.11-rscloud/kernel/net/netfilter/nf_conntrack_ftp.ko): Cannot allocate memory
My guess is that you’re on a VPS – and either low on memory, or your provider doesn’t allow you to load kernel modules.
Are you by chance using an OpenVZ-based VPS?
If so, what output do you get if you run “free -m”? And can you paste in the contents of /proc/user_beancounters?
Its a RackSpace Cloud Server
total used free shared buffers cached
Mem: 998 864 133 0 10 279
-/+ buffers/cache: 573 424
Swap: 2047 339 1708
-bash: /proc/user_beancounters: No such file or directory
I repeat my initial question: What exactly happens when you try to do a passive mode transfer? What does the client say, what do the logs show?
If you’d like us to try and help you, you need to provide the information we ask for as thoroughly as possible. “Doesn’t work” is not an error report.
I’ve upgraded the cloud servers memory to 2GBs and the modprobe ip_conntrack_ftp command has now run OK so was a memory issue stopping the command from running.
As I reported in my post above (Posted: Wed, 2012-05-02 22:07) I successfully ran the modprobe ip_conntrack_ftp command and pasv ftp had been working fine, I tried to connect to the server today and only PORT would work. I re-ran the modprobe ip_conntrack_ftp command and pasv ftp is working again, what would cause this to reset and how can I ensure it doesn’t happen again?
Was the server rebooted inbetween? As far as I know, modules should not get unloaded just like that.
As a quick-and-dirty workaround it might help to run the modprobe command once per day via cron. If the module is already loaded, modprobing it again doesn’t hurt.
Not sure if it had been rebooted, can I set it to always start on reboot/boot up if so how?
Modules can indeed be loaded at boot time.
What distro are you using?
For example, on Ubuntu/Debian, you can have a module load at boot time by adding it to the /etc/modules file.
There are instructions here for loading a module at boot time using CentOS:
Can I set this to be loaded at start-up/reboot via Webmin?