LinuxQuestions.org - Timing out when using filezilla to connect to vsFTPd

- Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)

- - Timing out when using filezilla to connect to vsFTPd (https://www.linuxquestions.org/questions/linux-networking-3/timing-out-when-using-filezilla-to-connect-to-vsftpd-4175431724/)

Timing out when using filezilla to connect to vsFTPd

Hi Guys

I've installed vsFTPd on my Ubunut box 12.04 and all seems well but I can't connect over the home network via ftp.

I can ping the IP addy (192.168.1.113) and that works fine.

The ftp server seems to be running if I open a terminal and type ftp 127.0.0.1

Code:

user@user-VT8367-8235:~$ ftp 127.0.0.1

Connected to 127.0.0.1.

220 (vsFTPd 2.3.5)

Name (127.0.0.1:user): 

331 Please specify the password.

Password:

230 Login successful.

Remote system type is UNIX.

Using binary mode to transfer files.

ftp>

But I'm get a timedout message when I try to connect over the home network with filezilla.

Can anyone point me in the right direction to sort this out?

Here's the entire config file

Code:

# Example config file /etc/vsftpd.conf

#

# The default compiled in settings are fairly paranoid. This sample file

# loosens things up a bit, to make the ftp daemon more usable.

# Please see vsftpd.conf.5 for all compiled in defaults.

#

# READ THIS: This example file is NOT an exhaustive list of vsftpd options.

# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's

# capabilities.

#

#

# Run standalone?  vsftpd can run either from an inetd or as a standalone

# daemon started from an initscript.

listen=YES

#

# Run standalone with IPv6?

# Like the listen parameter, except vsftpd will listen on an IPv6 socket

# instead of an IPv4 one. This parameter and the listen parameter are mutually

# exclusive.

#listen_ipv6=YES

#

# Allow anonymous FTP? (Beware - allowed by default if you comment this out).

anonymous_enable=YES

#

# Uncomment this to allow local users to log in.

local_enable=YES

#

# Uncomment this to enable any form of FTP write command.

write_enable=YES

#

# Default umask for local users is 077. You may wish to change this to 022,

# if your users expect that (022 is used by most other ftpd's)

#local_umask=022

#

# Uncomment this to allow the anonymous FTP user to upload files. This only

# has an effect if the above global write enable is activated. Also, you will

# obviously need to create a directory writable by the FTP user.

#anon_upload_enable=YES

#

# Uncomment this if you want the anonymous FTP user to be able to create

# new directories.

#anon_mkdir_write_enable=YES

#

# Activate directory messages - messages given to remote users when they

# go into a certain directory.

dirmessage_enable=YES

#

# If enabled, vsftpd will display directory listings with the time

# in  your  local  time  zone.  The default is to display GMT. The

# times returned by the MDTM FTP command are also affected by this

# option.

use_localtime=YES

#

# Activate logging of uploads/downloads.

xferlog_enable=YES

#

# Make sure PORT transfer connections originate from port 20 (ftp-data).

connect_from_port_20=YES

#

# If you want, you can arrange for uploaded anonymous files to be owned by

# a different user. Note! Using "root" for uploaded files is not

# recommended!

#chown_uploads=YES

#chown_username=whoever

#

# You may override where the log file goes if you like. The default is shown

# below.

#xferlog_file=/var/log/vsftpd.log

#

# If you want, you can have your log file in standard ftpd xferlog format.

# Note that the default log file location is /var/log/xferlog in this case.

#xferlog_std_format=YES

#

# You may change the default value for timing out an idle session.

#idle_session_timeout=600

#

# You may change the default value for timing out a data connection.

#data_connection_timeout=120

#

# It is recommended that you define on your system a unique user which the

# ftp server can use as a totally isolated and unprivileged user.

#nopriv_user=ftpsecure

#

# Enable this and the server will recognise asynchronous ABOR requests. Not

# recommended for security (the code is non-trivial). Not enabling it,

# however, may confuse older FTP clients.

#async_abor_enable=YES

#

# By default the server will pretend to allow ASCII mode but in fact ignore

# the request. Turn on the below options to have the server actually do ASCII

# mangling on files when in ASCII mode.

# Beware that on some FTP servers, ASCII support allows a denial of service

# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd

# predicted this attack and has always been safe, reporting the size of the

# raw file.

# ASCII mangling is a horrible feature of the protocol.

#ascii_upload_enable=YES

#ascii_download_enable=YES

#

# You may fully customise the login banner string:

#ftpd_banner=Welcome to blah FTP service.

#

# You may specify a file of disallowed anonymous e-mail addresses. Apparently

# useful for combatting certain DoS attacks.

#deny_email_enable=YES

# (default follows)

#banned_email_file=/etc/vsftpd.banned_emails

#

# You may restrict local users to their home directories.  See the FAQ for

# the possible risks in this before using chroot_local_user or

# chroot_list_enable below.

#chroot_local_user=YES

#

# You may specify an explicit list of local users to chroot() to their home

# directory. If chroot_local_user is YES, then this list becomes a list of

# users to NOT chroot().

# (Warning! chroot'ing can be very dangerous. If using chroot, make sure that

# the user does not have write access to the top level directory within the

# chroot)

#chroot_local_user=YES

#chroot_list_enable=YES

# (default follows)

#chroot_list_file=/etc/vsftpd.chroot_list

#

# You may activate the "-R" option to the builtin ls. This is disabled by

# default to avoid remote users being able to cause excessive I/O on large

# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume

# the presence of the "-R" option, so there is a strong case for enabling it.

#ls_recurse_enable=YES

#

# Customization

#

# Some of vsftpd's settings don't fit the filesystem layout by

# default.

#

# This option should be the name of a directory which is empty.  Also, the

# directory should not be writable by the ftp user. This directory is used

# as a secure chroot() jail at times vsftpd does not require filesystem

# access.

secure_chroot_dir=/var/run/vsftpd/empty

#

# This string is the name of the PAM service vsftpd will use.

pam_service_name=vsftpd

#

# This option specifies the location of the RSA certificate to use for SSL

# encrypted connections.

rsa_cert_file=/etc/ssl/private/vsftpd.pem

Hi,

Check if ports 21/20 tcp are open on your firewall

Regards

Quote:

Originally Posted by bathory (Post 4803355)

Hi,

Check if ports 21/20 tcp are open on your firewall

Regards

Which firewall? I can use the ftp program to connect to my NAS and web servers but not my linux box.

Quote:

Which firewall? I can use the ftp program to connect to my NAS and web servers but not my linux box.

That means there is a firewall (iptables) running on your box, blocking access to it.
Have a look here for details about iptables and how to open ports.

Regards

Quote:

Originally Posted by bathory (Post 4803381)

That means there is a firewall (iptables) running on your box, blocking access to it.
Have a look here for details about iptables and how to open posts.

Regards

Thanks for this help, I'll take a look tomorrow and see if I can open the ports.

P

Quote:

Originally Posted by bathory (Post 4803381)

That means there is a firewall (iptables) running on your box, blocking access to it.
Have a look here for details about iptables and how to open ports.

Regards

well I'm not too sure what I'm looking at but...

Code:

user@user-VT8367-8235:~$ sudo iptables -L

[sudo] password for user: 

Chain INPUT (policy DROP)

target    prot opt source              destination        

ACCEPT    tcp  --  localhost.localdomain  anywhere            tcpflags:! FIN,SYN,RST,ACK/SYN

ACCEPT    udp  --  localhost.localdomain  anywhere            

ACCEPT    all  --  anywhere            anywhere            

ACCEPT    icmp --  anywhere            anywhere            limit: avg 10/sec burst 5

I'm not running ubuntu, so I cannot tell how the firewall is configured. Anyway try:

Code:

sudo iptables -A INPUT -p tcp --dport ftp -j ACCEPT

You can also stop the firewall, or flush iptables temporarily

Code:

iptables -F

iptables -P INPUT ACCEPT

iptables -P FORWARD ACCEPT

iptables -P OUTPUT ACCEPT

to see if you can connect remotely

Regards

Quote:

Originally Posted by bathory (Post 4803667)

I'm not running ubuntu, so I cannot tell how the firewall is configured. Anyway try:

Code:

sudo iptables -A INPUT -p tcp --dport ftp -j ACCEPT

You can also stop the firewall, or flush iptables temporarily

Code:

iptables -F

iptables -P INPUT ACCEPT

iptables -P FORWARD ACCEPT

iptables -P OUTPUT ACCEPT

to see if you can connect remotely

Regards

Thanks, the above has enabled me to connect.

Sadly as soon as I reboot I cant connect.

I'm getting the message 'connection established, waiting for welcome message' before timing out

Quote:

Originally Posted by pbryd (Post 4804102)

Thanks, the above has enabled me to connect.

Which one? The rule to open ftp port, or flushing iptables. Note that the latter is not recommended for obvious reasons.

Quote:

Sadly as soon as I reboot I cant connect.

Take a look here, about saving iptables rules and configure it to start on boot.

The four lines of code that flushed the tables.

I'll take a look at the link tomorrow.

I can't believe it's causing me so much trouble to set up a ftp server.

P

Quote:

Originally Posted by bathory (Post 4804247)

Which one? The rule to open ftp port, or flushing iptables. Note that the latter is not recommended for obvious reasons.

Take a look here, about saving iptables rules and configure it to start on boot.

I can connect without problems if I use

Code:

iptables -F

This is starting too complicated for me to get my head around.

I've also tried sharing across the network with SAMBA and that doesn't work for me either.

I'm thinking there's a deeper problem somewhere.

P

Better use a firewall for security reasons, so don't flush iptables, but look for a way to open ftp ports on your firewall.
Have a look here to better understand how the ubuntu firewall works.

HTH

i have the ufw firewall running and the status command gives me this

Code:

To                        Action      From

--                        ------      ----

21/tcp                    ALLOW      Anywhere

21                        ALLOW      Anywhere

20                        ALLOW      Anywhere

20/tcp                    ALLOW      Anywhere

21/tcp                    ALLOW      Anywhere (v6)

21                        ALLOW      Anywhere (v6)

20                        ALLOW      Anywhere (v6)

20/tcp                    ALLOW      Anywhere (v6)

I've restarted vsftpd service but I cant connect.

P

I'm getting

connection established, waiting for welcome message...

before timing out.

Disabling ufw doesn't make a difference either.