phibuntu
May 23rd, 2011, 03:42 PM
[SOLVED]
Hi everybody
I wanted to connect to my FTP Server (vsftp version 2.0.7) yesterday and could suddenly not connect:
>ftp gress.ly
Connected to gress.ly.
220 ProFTPD 1.3.1 Server (Debian) [::ffff:109.230.211.248]
Name (gress.ly:phi): phi
331 Password required for phi
Password:
530 Login incorrect.
Login failed.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp>
Actually I run a debian Server, but the forum of my provider does not know the word "vsftp" (thats why I ask here).
My vsftp.conf look like this:
listen=YES
anonymous_enable=NO
local_enable=YES
write_enable=YES
local_umask=022
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
chown_uploads=YES
chown_username=phi
chroot_local_user=YES
secure_chroot_dir=/var/run/vsftpd
pam_service_name=vsftpd
rsa_cert_file=/etc/ssl/certs/vsftpd.pem
restarting the server...
>/etc/init.d/vsftpd restart
... I get:
Restarting FTP server: vsftpdNo /usr/sbin/vsftpd found running; none killed.
.
Even if a /var/run/vsftp/vsftp.pid is generated, there is no process started (ps -A | grep "vsftp" produces an empty output). I think the process kills itself. I have found nothing in the log files.
What happened? I have done nothing with the vsftp, it worked properly some weeks ago. But: Because the provider moved my virtual host to another PC and because I upgraded all debian-packages, I think, it has something to do with a firewall, restricted ports or simply with a new IPv6 address???
Any Ideas where to look further?
Every help is welcome.
ɸ
Hi everybody
I wanted to connect to my FTP Server (vsftp version 2.0.7) yesterday and could suddenly not connect:
>ftp gress.ly
Connected to gress.ly.
220 ProFTPD 1.3.1 Server (Debian) [::ffff:109.230.211.248]
Name (gress.ly:phi): phi
331 Password required for phi
Password:
530 Login incorrect.
Login failed.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp>
Actually I run a debian Server, but the forum of my provider does not know the word "vsftp" (thats why I ask here).
My vsftp.conf look like this:
listen=YES
anonymous_enable=NO
local_enable=YES
write_enable=YES
local_umask=022
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
chown_uploads=YES
chown_username=phi
chroot_local_user=YES
secure_chroot_dir=/var/run/vsftpd
pam_service_name=vsftpd
rsa_cert_file=/etc/ssl/certs/vsftpd.pem
restarting the server...
>/etc/init.d/vsftpd restart
... I get:
Restarting FTP server: vsftpdNo /usr/sbin/vsftpd found running; none killed.
.
Even if a /var/run/vsftp/vsftp.pid is generated, there is no process started (ps -A | grep "vsftp" produces an empty output). I think the process kills itself. I have found nothing in the log files.
What happened? I have done nothing with the vsftp, it worked properly some weeks ago. But: Because the provider moved my virtual host to another PC and because I upgraded all debian-packages, I think, it has something to do with a firewall, restricted ports or simply with a new IPv6 address???
Any Ideas where to look further?
Every help is welcome.
ɸ