• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Issue FTP System not working

jimmy57000

jimmy57000

New Pleskian
Hello,
I have had a problem for 2 days with my FTP server, it is no longer possible to connect.

Error:
Status: Resolution of the address of ftp.mydomain.com
Status: Connection to myip:21...
Status: Connection established, waiting for the welcome message...
Error: Connection interrupted by the server
Error: Unable to establish a connection to the server

I tried the Plesk update and several reboots, nothing to do..

PLesk Version: 18.0.40
Linux Version: CentOS Linux 7.9.2009 (Core)

Thank you in advance for your future help!
 
Thomas Wilhelmi said:
Did you enable the Firewall and the passive Ports are blocked?

Otherwise a bit more of Log-File would be necessary
Click to expand...
The ports are open, I haven't touched anything for 1 year!
The ports are wide open, I also tried to solve all the same problem!

Log:
Jan 07 23:58:16 web01.cserv.fr xinetd[843]: xinetd Version 2.3.15 started with libwrap loadavg labeled-networking options compiled in.
Jan 07 23:58:16 web01.cserv.fr xinetd[843]: Started working: 2 available services
Jan 07 23:58:21 web01.cserv.fr xinetd[843]: START: ftp pid=1970 from=::ffff:82.65.149.68
Jan 07 23:58:21 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=1970 duration=0(sec)
Jan 07 23:58:26 web01.cserv.fr xinetd[843]: START: ftp pid=1991 from=::ffff:82.65.149.68
Jan 07 23:58:26 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=1991 duration=0(sec)
Jan 07 23:58:49 web01.cserv.fr xinetd[843]: START: ftp pid=2010 from=::ffff:65.108.169.14
Jan 07 23:58:49 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=2010 duration=0(sec)
Jan 07 23:59:49 web01.cserv.fr xinetd[843]: START: ftp pid=2068 from=::ffff:65.108.169.14
Jan 07 23:59:49 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=2068 duration=0(sec)
Jan 08 00:00:49 web01.cserv.fr xinetd[843]: START: ftp pid=2544 from=::ffff:65.108.169.14
Jan 08 00:00:49 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=2544 duration=0(sec)
Jan 08 00:01:49 web01.cserv.fr xinetd[843]: START: ftp pid=2557 from=::ffff:65.108.169.14
Jan 08 00:01:49 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=2557 duration=0(sec)
Jan 08 00:02:49 web01.cserv.fr xinetd[843]: START: ftp pid=2573 from=::ffff:65.108.169.14
Jan 08 00:02:49 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=2573 duration=0(sec)

Status:

[root@web01 ~]# service xinetd status
Redirecting to /bin/systemctl status xinetd.service
● xinetd.service - Xinetd A Powerful Replacement For Inetd
Loaded: loaded (/usr/lib/systemd/system/xinetd.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/xinetd.service.d
└─respawn.conf
Active: active (running) since Sun 2022-01-09 00:59:48 CET; 16s ago
Process: 7571 ExecStart=/usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid $EXTRAOPTIONS (code=exited, status=0/SUCCESS)
Main PID: 7572 (xinetd)
Tasks: 1
Memory: 552.0K
CGroup: /system.slice/xinetd.service
└─7572 /usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid

Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing daytime
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing discard
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing discard
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing echo
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing echo
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing tcpmux
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing time
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing time
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: xinetd Version 2.3.15 started with libwrap loadavg labeled-networking options compiled in.
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: Started working: 2 available services
 
jimmy57000 said:
The ports are open, I haven't touched anything for 1 year!
The ports are wide open, I also tried to solve all the same problem!

Log:
Jan 07 23:58:16 web01.cserv.fr xinetd[843]: xinetd Version 2.3.15 started with libwrap loadavg labeled-networking options compiled in.
Jan 07 23:58:16 web01.cserv.fr xinetd[843]: Started working: 2 available services
Jan 07 23:58:21 web01.cserv.fr xinetd[843]: START: ftp pid=1970 from=::ffff:82.65.149.68
Jan 07 23:58:21 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=1970 duration=0(sec)
Jan 07 23:58:26 web01.cserv.fr xinetd[843]: START: ftp pid=1991 from=::ffff:82.65.149.68
Jan 07 23:58:26 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=1991 duration=0(sec)
Jan 07 23:58:49 web01.cserv.fr xinetd[843]: START: ftp pid=2010 from=::ffff:65.108.169.14
Jan 07 23:58:49 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=2010 duration=0(sec)
Jan 07 23:59:49 web01.cserv.fr xinetd[843]: START: ftp pid=2068 from=::ffff:65.108.169.14
Jan 07 23:59:49 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=2068 duration=0(sec)
Jan 08 00:00:49 web01.cserv.fr xinetd[843]: START: ftp pid=2544 from=::ffff:65.108.169.14
Jan 08 00:00:49 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=2544 duration=0(sec)
Jan 08 00:01:49 web01.cserv.fr xinetd[843]: START: ftp pid=2557 from=::ffff:65.108.169.14
Jan 08 00:01:49 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=2557 duration=0(sec)
Jan 08 00:02:49 web01.cserv.fr xinetd[843]: START: ftp pid=2573 from=::ffff:65.108.169.14
Jan 08 00:02:49 web01.cserv.fr xinetd[843]: EXIT: ftp status=1 pid=2573 duration=0(sec)

Status:

[root@web01 ~]# service xinetd status
Redirecting to /bin/systemctl status xinetd.service
● xinetd.service - Xinetd A Powerful Replacement For Inetd
Loaded: loaded (/usr/lib/systemd/system/xinetd.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/xinetd.service.d
└─respawn.conf
Active: active (running) since Sun 2022-01-09 00:59:48 CET; 16s ago
Process: 7571 ExecStart=/usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid $EXTRAOPTIONS (code=exited, status=0/SUCCESS)
Main PID: 7572 (xinetd)
Tasks: 1
Memory: 552.0K
CGroup: /system.slice/xinetd.service
└─7572 /usr/sbin/xinetd -stayalive -pidfile /var/run/xinetd.pid

Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing daytime
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing discard
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing discard
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing echo
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing echo
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing tcpmux
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing time
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: removing time
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: xinetd Version 2.3.15 started with libwrap loadavg labeled-networking options compiled in.
Jan 09 00:59:48 web01.cserv.fr xinetd[7572]: Started working: 2 available services
Click to expand...


I have the same problem, can you tell me how to solve this problem?


Thanks
 
I moved into AWS 10 years ago and haven't been able to ftp ever; can sftp using my root and key but Its too much trouble for the average user who wants/needs to ftp some files.
I rather have them use the file admin in the domain's control panel. Maybe not so fast as ftp but pretty straightforward for them
 
You must log in or register to reply here.

Similar threads

P
Resolved FTP Connection Closed By Server
Replies
7
Views
3K
PeterK900
P
S
Issue php fpm service Failed
2
Replies
20
Views
2K
Peter Debik
P
P
Issue Error when doing backup on remote FTP
Replies
7
Views
254
PaoloM
P
M
Resolved Failed to retrieve directory listing
Replies
2
Views
2K
MMM
M
F
Issue Server is permanently down and unavailable
2 3 4
Replies
73
Views
7K
fab5freddie
F
Back
Top