FTP Issues: Can't upload files via ftp and new ftp user having the same problem.

Virtualmin
21

I don’t think it’s related to the firewall/portforwarding, since I have my server in the DMZ temporarily while testing and I’ve disabled the CentOS firewall. Actually, all my firewall/router settings are the same ones that resulted in the successful ftp sessions I had yesterday (it was working perfectly, I was able to upload files, edit files… I had multiple sessions going, it was working flawlessly). I can also confirm that port 21 is open.

I’m connecting from the host computer on the LAN to the VM/CentOS Server.

The exact problem is that when I go to Dreamweaver or filezilla, I can’t connect. I get the standard connection refused for both programs. I’m using the same dreamweaver/filezilla settings that were working before this whole eth0 to eth1 fiasco.

So, same firewall settings, same ftp settings and no luck. As soon as I changed back from eth1 to eth0, the first thing I did was retest the ftp and got the connection refused error, so something changed when I went from eth0 to eth1 and then back to eth0… some file must have gotten modified somewhere.

I’ve also created an ftp user, but he can’t connect either.

This is a strange phenomenon indeed. On the bright side, the dns is still working great, I’m able to visit my domain externally, just need to solve the ftp issue.

I’m willing to try anything at this point, since I had it working yesterday. If you come up with some new tests, I will try them.

Thank Locutus, appreciate all your help.

22

Here’s a recent output of /var/log/messages:

Feb 23 11:34:18 examplehost rsyslogd: [origin software="rsyslogd" swVersion="5.8.10" x-pid="1488" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Feb 23 11:34:49 examplehost proftpd[6485]: 127.0.0.1 (::ffff:198.199.98.246[::ffff:198.199.98.246]) - FTP session opened.
Feb 23 11:34:49 examplehost proftpd[6485]: 127.0.0.1 (::ffff:198.199.98.246[::ffff:198.199.98.246]) - FTP session closed.
Feb 23 11:41:01 examplehost proftpd[6764]: 127.0.0.1 (::ffff:198.199.98.246[::ffff:198.199.98.246]) - FTP session opened.
Feb 23 11:41:01 examplehost proftpd[6764]: 127.0.0.1 (::ffff:198.199.98.246[::ffff:198.199.98.246]) - FTP session closed.
Feb 23 11:41:13 examplehost clamd[1861]: SelfCheck: Database modification detected. Forcing reload.
Feb 23 11:41:13 examplehost clamd[1861]: Reading databases from /var/lib/clamav
Feb 23 11:41:20 examplehost clamd[1861]: Database correctly reloaded (3131257 signatures)
Feb 23 11:41:51 examplehost proftpd[6859]: 127.0.0.1 (::ffff:198.199.98.246[::ffff:198.199.98.246]) - FTP session opened.
Feb 23 11:41:51 examplehost proftpd[6859]: 127.0.0.1 (::ffff:198.199.98.246[::ffff:198.199.98.246]) - FTP session closed.
Feb 23 11:55:47 examplehost proftpd[7287]: 127.0.0.1 (::ffff:198.199.98.246[::ffff:198.199.98.246]) - FTP session opened.
Feb 23 11:55:47 examplehost proftpd[7287]: 127.0.0.1 (::ffff:198.199.98.246[::ffff:198.199.98.246]) - FTP session closed.
Feb 23 11:56:04 examplehost clamd[1861]: SelfCheck: Database status OK.
23

Okay, sorry I’m out of ideas what to test, remotely via the forum. The problem can have a number of reasons, and I’d need to see your system for myself, anything else is too much guesswork.

I could offer you a screen sharing / instant messenger session tomorrow. I can only do this for free if it doesn’t take longer than about 30 minutes though, since I do this in my somewhat limited spare time. :slight_smile: If you’re not looking for paid support, the user “tpnsolutions” might be able and willing to do screen sharing for free.

24

sure, I can do a screenshare. Give me a time, let me know what software you use and how to contact you and I will be there.

thanks locutus.

25

Okies, we can use Teamviewer, I’m in timezone UTC+1. You can contact me on Skype, user “Loc2262”. Can’t say exactly yet when I’m free tomorrow, but we’ll find a time. :slight_smile:

26

Issue (for now) solved via screen sharing. As a reference for others:

The problem was that the user tried to connect to his server, which is in his LAN and reachable from the outside via a NAT router, from the LAN via the external IP.

His router does not perform port forwarding from the LAN (or we could not find the setting to turn that on – I know that e.g. pfSense can do that, it’s called “NAT reflection”), so that didn’t work. By simply using the LAN IP of the server, the issue vanished. :slight_smile:

27

I can’t thank you guys enough! We used the LAN IP of the server and it worked fine.

Locutus, you did an outstanding job in not only solving the problem but helping me in general… I learned so much.

Thanks so much!

KInd Regards.