New FTP users cannot connect

5 posts / 0 new
Last post
#1 Tue, 10/06/2015 - 09:41
A Good Tech

New FTP users cannot connect

I just want to say that I love Virtualmin and have been using it for some years now, but I still consider myself somewhat of a noob. I have search the forum and Google for sometime trying to resolve my issue and have not found anything. So here we go, I have 10 plus servers all running CentOS, about 8 of them are running CentOS 6.7 and the rest I installed CentOS 7. On the CentOS 7 servers I did not install any repos, I kept it completely vanilla, I find this a lot easier to maintain. So here is the problem, anytime I ad a new user to a VS in "Add a website FTP access user" I get no errors, but when I try to login via FTP I get this:

Status: Resolving address of host002.agoodlab.com Status: Connecting to 50.249.118.28:21... Status: Connection established, waiting for welcome message... Status: Insecure server, it does not support FTP over TLS. Status: Connected Status: Retrieving directory listing... Command: PWD Response: 257 "/" is the current directory Command: TYPE I Response: 200 Type set to I Command: PASV Response: 227 Entering Passive Mode (50,249,118,28,191,121). Command: MLSD Error: Connection timed out after 20 seconds of inactivity Error: Failed to retrieve directory listing

Now I assume that it is something that I am doing, because all the servers do the same thing, I thought at first it might be do to the extra repos in the old servers causing the Proftp to update to an incompatible version. That is why I did a fresh install with CentOS 7 and a fresh install of Virtualmin, but I still get the same errors. Here are some log entries from var/log/secure :

Oct 6 09:59:01 host002 proftpd: pam_unix(proftpd:session): session opened for user brook@host002.agoodlab.com by (uid=0) Oct 6 09:59:01 host002 proftpd[6180]: 50.249.118.28 (75.73.73.12[75.73.73.12]) - USER brook@host002.agoodlab.com: Login successful. Oct 6 09:59:22 host002 proftpd: pam_unix(proftpd:session): session opened for user brook@host002.agoodlab.com by (uid=0) Oct 6 09:59:22 host002 proftpd[6184]: 50.249.118.28 (75.73.73.12[75.73.73.12]) - USER brook@host002.agoodlab.com: Login successful. Oct 6 09:59:42 host002 saslauthd[699]: pam_unix(smtp:auth): check pass; user unknown Oct 6 09:59:42 host002 saslauthd[699]: pam_unix(smtp:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Oct 6 09:59:44 host002 saslauthd[701]: pam_unix(smtp:auth): check pass; user unknown Oct 6 09:59:44 host002 saslauthd[701]: pam_unix(smtp:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Oct 6 09:59:49 host002 saslauthd[700]: pam_unix(smtp:auth): check pass; user unknown Oct 6 09:59:49 host002 saslauthd[700]: pam_unix(smtp:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= Oct 6 10:00:01 host002 su: pam_unix(su:session): session opened for user postgres by (uid=0) Oct 6 10:00:01 host002 su: pam_unix(su:session): session closed for user postgres

Sorry so long, any help would be great!!

Tue, 10/06/2015 - 10:12
andreychek

Aha, I think you may be seeing this issue -- try the fix mentioned here and see if this helps:

http://virtualmin.com/documentation/web/faq#FTP_Service_isn-t_working

Tue, 10/06/2015 - 11:50 (Reply to #2)
A Good Tech

That is what it is!! So far I have tried this on 2 of the servers and it is working, thank you so much. My one question would be is this something I am doing wrong during the install or is this something common on CentOS and other builds. I don't mind having to run this, but wanted to make sure that it isn't something that is preventable. Thanks again!! :o)

Tue, 10/06/2015 - 14:11
andreychek

Howdy,

It's great to hear that works!

It's likely a router or firewall issue... are these particular servers behind a NAT router, by chance?

However, it's very unlikely to be anything you're doing incorrectly, it's generally a networking related issue.

-Eric

Tue, 10/06/2015 - 17:49 (Reply to #4)
A Good Tech

I have the servers directly connected to the router, so I would assume that it was the firewall built into CentOS. Thanks again for such a quick response!!

Topic locked