Sftp error listing directory

WinSCP is a free SFTP, SCP, Amazon S3, WebDAV, and FTP client for Windows.
ZAJDAN
Joined:
2017-06-06
Posts:
2
Location:
CzechRepublic

2017-06-06 13:50

Hello

I have windows scheduler script for winSCP: 

/log=c:UsersAdministratorwinscp.log /command "open sftp://sqlbackup:mypassword@192.168.6.116/" "synchronize remote C:database_backups  /mnt/databox/sapDatabase-backup/sqlbackup" "exit"

but in log I see this problem: 

2017-06-06 14:35:12.333 Error listing directory '/mnt/databox/sapDatabase-backup/sqlbackup'. ("No such file or directory.
. 2017-06-06 14:35:12.333 Error code: 2
. 2017-06-06 14:35:12.333 Error message from server: No such file")
< 2017-06-06 14:35:12.334 Script: Error listing directory '/mnt/databox/sapDatabase-backup/sqlbackup'.
< 2017-06-06 14:35:12.334 Script: No such file or directory.
< 2017-06-06 14:35:12.334 Error code: 2
< 2017-06-06 14:35:12.334 Error message from server: No such file
. 2017-06-06 14:35:12.334 Script: Failed
. 2017-06-06 14:35:12.334 Script: Exit code: 1
. 2017-06-06 14:35:12.335 Closing connection.
. 2017-06-06 14:35:12.335 Sending special code: 12
. 2017-06-06 14:35:12.335 Sent EOF message

when I connect to the directory via GUI, so I am successfully connected and can create/delete files/directory

on linux the user sqlbackup is chrooted and has shell /bin/false

on server in auth.log is: 

systemd-logind[712]: New session 37 of user sqlbackup.
systemd: pam_unix(systemd-user:session): session opened for user sqlbackup by (uid=0)
linux-zdenek sshd[16519]: pam_unix(sshd:session): session closed for user sqlbackup
linux-zdenek systemd-logind[712]: Removed session 37.
linux-zdenek systemd: pam_unix(systemd-user:session): session closed for user sqlbackup

Thank You for any hint

Regards ZAJDAN

Reply with quote

ZAJDAN
Joined:
2017-06-06
Posts:
2
Location:
CzechRepublic

2017-06-07 11:05

SOLVED…

because I use chroot via sshd_config I can not use the whole path but only what is inside the chroot…so in my case

/log=c:UsersAdministratorwinscp.log /command «open sftp://sqlbackup:mypassword@192.168.6.116/» «synchronize remote C:database_backups /sqlbackup» «exit»

thanx for Tuxik(CZ) :_)

Reply with quote

Источник

I suddenly get this error using SFTP:

Status: Connecting to 64.207.146.82...
Response:   fzSftp started
Command:    open "root@64.207.146.82" 22
Command:    Pass: *********
Status: Connected to 64.207.146.82
Status: Retrieving directory listing...
Command:    pwd
Response:   Current directory is: "/root"
Command:    ls
Status: Listing directory /root
Error:  Connection timed out
Error:  Failed to retrieve directory listing

I tried using FileZila, Cyberduck, Shell (Terminal), same result. However, it worked fine today (just a few seconds) in Passive mode.

This is the message in Cyberduck:

I/O Error: Unexpected end of sftp stream.

I have no firewall active on my computer, and after changing some things in my network I pass the test (both active and passive):

Connecting to probe.filezilla-project.org
Response: 220 FZ router and firewall tester ready
USER FileZilla
Response: 331 Give any password.
PASS 3.6.0.2
Response: 230 logged on.
Checking for correct external IP address
Retrieving external IP address from http://checkip.dyndns.org:8245/
Checking for correct external IP address
IP 186.15.222.5 big-bf-ccc-f
Response: 200 OK
PREP 50185
Response: 200 Using port 50185, data token 386379933
PORT 186,15,222,5,196,9
Response: 200 PORT command successful
LIST
Response: 150 opening data connection
Response: 200 Successful
QUIT
Response: 200 goodbye!
Connection closed

Now I’m working on Passive mode.

Because I’m working behind a router, I get my external IP from http://checkip.dyndns.org:8245/

I tested different range of ports.

SSH is working perfect, but SFTP gets stuck in the listing directory part.

sftp root@64.207.146.82
root@64.207.146.82's password: 
Connected to 64.207.146.82.
sftp>ls

Doing some debugging from ssh:

ssh -vv root@domain.com
OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to domain.com [64.207.146.82] port 22.
debug1: Connection established.
debug1: identity file /Users/Admin/.ssh/id_rsa type -1
debug1: identity file /Users/Admin/.ssh/id_rsa-cert type -1
debug1: identity file /Users/Admin/.ssh/id_dsa type -1
debug1: identity file /Users/Admin/.ssh/id_dsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH_4*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.6
debug2: fd 3 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: mac_setup: found hmac-md5
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 128/256
debug2: bits set: 543/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'domain.com' is known and matches the RSA host key.
debug1: Found key in /Users/Admin/.ssh/known_hosts:2
debug2: bits set: 508/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /Users/Admin/.ssh/id_rsa (0x0)
debug2: key: /Users/Admin/.ssh/id_dsa (0x0)
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/Admin/.ssh/id_rsa
debug1: Trying private key: /Users/Admin/.ssh/id_dsa
debug2: we did not send a packet, disable method
debug1: Next authentication method: password
root@domain.com's password: 
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
Authenticated to domain.com ([64.207.146.82]:22).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug2: channel 0: request env confirm 0
debug2: channel 0: request shell confirm 1
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
Last login: Fri Dec 21 19:55:45 2012 from ip5-222-15-186.ct.co.cr
############################################################
                     (mt) shortcuts
############################################################

To see your Plesk password, type: p

To rebuild your Apache/Web Server configuration, type: web

To rebuild your Qmail/Mail Server configuration, type: mchk

To see your Qmail/Mail Server queue, type: q

To completely restart your Qmail/Mail server, type: r

To connect to your MySQL server as admin, type: my

To apply the latest Plesk microupdates, type: up

To get rid of these messages/aliases, edit your /root/.bash_profile

[root@domain ~]#

SOLUTION:

Once you login/connect with the server using SSH:

p link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue 
    link/void 
[root@domian ~]# ip link set eth0 mtu 1400
SIOCSIFMTU: No such device
[root@domian ~]# ip link set venet0 mtu 1400
[root@domian ~]# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1400 qdisc noqueue 
    link/void 
[root@domian ~]#

Источник

Moderator: Project members

CS-JS

500 Command not understood
Posts: 5
Joined: 2017-05-31 09:37
First name: Johannes
Last name: Schön

SFTP Connection stops at «Listing directory»

#1

Post

by CS-JS » 2017-05-31 09:46

Hi all,

I have a SFTP-Server up and running fine, except for one client that tries to connect to the server via FileZilla.

Code: Select all

2017-05-31 10:18:48 7468 5 Status: Connecting to server.example.com:222...
2017-05-31 10:18:48 7468 5 Response: fzSftp started, protocol_version=8
2017-05-31 10:18:48 7468 5 Command: keyfile "C:pathtokeyfileprivate_key.txt"
2017-05-31 10:18:48 7468 5 Command: open "user@server.example.com" 222
2017-05-31 10:18:50 7468 5 Command: Trust new Hostkey: Once
2017-05-31 10:18:50 7468 5 Status: Connected to server.example.com
2017-05-31 10:18:50 7468 5 Status: Retrieving directory listing...
2017-05-31 10:18:50 7468 5 Command: pwd
2017-05-31 10:18:50 7468 5 Response: Current directory is: "/"
2017-05-31 10:18:50 7468 5 Command: ls
2017-05-31 10:18:50 7468 5 Status: Listing directory /

After that nothing happens in the FileZilla Client. On the server-side i get similar entries (sftp.log), those entries are corresponding with the client log above:

Code: Select all

May 31 10:18:50 server internal-sftp[26878]: session opened for local user USER from [***.***.***.***]
May 31 10:18:50 server internal-sftp[26878]: received client version 3
May 31 10:18:50 server internal-sftp[26878]: realpath "."
May 31 10:18:50 server internal-sftp[26878]: realpath "/."
May 31 10:18:50 server internal-sftp[26878]: opendir "/"

When I connect to the SFTP server from my machine it works perfectly fine (same user, same server, same port etc.). Other clients dont experience this problem (we have about 40 FTP/SFTP-Accounts running and never had such an issue). I’d like to suggest a WireShark-Trace for that particular client, but I want to make sure this is not a common or known issue, that could be solved otherwise first.

Thanks for any hints in advance!

CS-JS

500 Command not understood
Posts: 5
Joined: 2017-05-31 09:37
First name: Johannes
Last name: Schön

Re: SFTP Connection stops at «Listing directory»

#2

Post

by CS-JS » 2017-05-31 12:27

New Info, after some time the Client gets an timeout.

Code: Select all

Error:	Connection timed out after 20 seconds of inactivity
Error:	Failed to retrieve directory listing
Status:	Disconnected from server

So we have at least an error to work on :-) Tips and hints are nevertheless welcome :-)

User avatar

botg

Site Admin
Posts: 34745
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: SFTP Connection stops at «Listing directory»

#3

Post

by botg » 2017-05-31 12:51

Which SFTP server software (product and version) are you using?

CS-JS

500 Command not understood
Posts: 5
Joined: 2017-05-31 09:37
First name: Johannes
Last name: Schön

Re: SFTP Connection stops at «Listing directory»

#4

Post

by CS-JS » 2017-05-31 13:29

botg wrote:Which SFTP server software (product and version) are you using?

Code: Select all

dpkg -l | grep sftp
ii  openssh-sftp-server               1:6.7p1-5+deb8u3                   amd64        secure shell (SSH) sftp server module, for SFTP access from remote machines

Debians internal-sftp as described here for example:
https://www.linode.com/docs/tools-refer … and-ubuntu

The server itself is a Debian Jessie, SSH / SFTP only allow Public/Private Authentication.

User avatar

botg

Site Admin
Posts: 34745
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: SFTP Connection stops at «Listing directory»

#5

Post

by botg » 2017-05-31 14:02

Are there any files with non-ASCII characters in their names in the directory that is being listed?

CS-JS

500 Command not understood
Posts: 5
Joined: 2017-05-31 09:37
First name: Johannes
Last name: Schön

Re: SFTP Connection stops at «Listing directory»

#6

Post

by CS-JS » 2017-06-01 08:37

Not any that I’m aware of:

Code: Select all

root@server /home/sftpUsers/USER # ls -alh
insgesamt 20K
drwxr-xr-x 5 root  root  4,0K Apr 19 13:10 .
drwxr-xr-x 4 root  root  4,0K Mär 28 15:02 ..
drwxr-sr-x 2 USER  USER  4,0K Mai 14 17:29 dev
drwxr-xr-x 5 USER  USER  4,0K Mai 17 00:29 html
drwxr-xr-x 2 USER  USER  4,0K Apr 19 13:10 staging-html

That is an actual listing of the / directory that the client tries to open. «dev» contains the server-side sftp-log that I quoted earlier, «html» and «staging-html» are two versions of a website, «html» beeing the productive one and «html-staging» being the testing environment.

User avatar

botg

Site Admin
Posts: 34745
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: SFTP Connection stops at «Listing directory»

#7

Post

by botg » 2017-06-01 17:23

The SFTP components in FileZilla are based on PuTTY. If you use the latest version of PuTTY’s psftp.exe, can you list the directory?

CS-JS

500 Command not understood
Posts: 5
Joined: 2017-05-31 09:37
First name: Johannes
Last name: Schön

Re: SFTP Connection stops at «Listing directory»

#8

Post

by CS-JS » 2017-06-02 06:56

Thanks for the hint, worked for me, like FileZilla does — I will get my client to test it and report back :-)

Источник

I set up SFTP, but I have a problem regarding iptables. Here are my rules:

A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 21 -j ACCEPT
A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 20 -j ACCEPT
A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 21 -j ACCEPT

By the way, I’m using the vsftpd service for FTP. So, it’s not connecting to FTP, before stopping iptables service. When I attempt to connect to FTP, that’s gives me «Listing remote folder failed» error.

What should I do?

John's user avatar

John

2151 gold badge3 silver badges10 bronze badges

asked Jun 22, 2011 at 7:51

Cell-o's user avatar

SFTP and FTP are not the same thing.

If you really mean SFTP, that’s an SSH-based transmission that takes place only over port 22 (unless you configure your SSH daemon to listen on another port).

FTP is an ancient file-transfer protocol that operates on ports and 21 (and possibly others). Firewalls need to do connection state-tracking to properly support it. Make sure you have the netfilter ftp connection tracking module (nf_conntrack_ftp) loaded.

You can configure the min/max ports for «passive mode» FTP in vsftp via the pasv_min_port and pasv_max_port options in vsftpd.conf: Could you narrow the range down to a small number of ports (perhaps one port) and open them in the firewall?

Are you sure the firewall is at fault? If you disable it temporarily, do things work?

answered Jun 22, 2011 at 8:38

jmtd's user avatar

jmtdjmtd

9,1252 gold badges25 silver badges26 bronze badges

1

Источник

Using SFTP I suddenly get this result:

Status: Connecting to 64.207.146.82...
Response:   fzSftp started
Command:    open "root@64.207.146.82" 22
Command:    Pass: *********
Status: Connected to 64.207.146.82
Status: Retrieving directory listing...
Command:    pwd
Response:   Current directory is: "/root"
Command:    ls
Status: Listing directory /root
Error:  Connection timed out
Error:  Failed to retrieve directory listing

I tested in Cyberduck, FileZila and Terminal, same result. I can login but once I get to the point when: Directory Listing it freezes (no answer).

I can access using FTP (port 21) with a different user, the problem is that I cannot update any of the files (I have been working as root).

Tested in 3 computers, same result in my office. However, I tested at home and it works (so I guess is not a problem with the Hosting provider).

Doing some debugging from ssh:

ssh -vv root@domain.com
OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to domain.com [64.207.146.82] port 22.
debug1: Connection established.
debug1: identity file /Users/Admin/.ssh/id_rsa type -1
debug1: identity file /Users/Admin/.ssh/id_rsa-cert type -1
debug1: identity file /Users/Admin/.ssh/id_dsa type -1
debug1: identity file /Users/Admin/.ssh/id_dsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH_4*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.6
debug2: fd 3 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: mac_setup: found hmac-md5
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: found hmac-md5
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 128/256
debug2: bits set: 543/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'domain.com' is known and matches the RSA host key.
debug1: Found key in /Users/Admin/.ssh/known_hosts:2
debug2: bits set: 508/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /Users/Admin/.ssh/id_rsa (0x0)
debug2: key: /Users/Admin/.ssh/id_dsa (0x0)
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/Admin/.ssh/id_rsa
debug1: Trying private key: /Users/Admin/.ssh/id_dsa
debug2: we did not send a packet, disable method
debug1: Next authentication method: password
root@domain.com's password: 
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
Authenticated to domain.com ([64.207.146.82]:22).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug2: channel 0: request env confirm 0
debug2: channel 0: request shell confirm 1
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
Last login: Fri Dec 21 19:55:45 2012 from ip5-222-15-186.ct.co.cr
############################################################
                     (mt) shortcuts
############################################################

To see your Plesk password, type: p

To rebuild your Apache/Web Server configuration, type: web

To rebuild your Qmail/Mail Server configuration, type: mchk

To see your Qmail/Mail Server queue, type: q

To completely restart your Qmail/Mail server, type: r

To connect to your MySQL server as admin, type: my

To apply the latest Plesk microupdates, type: up

To get rid of these messages/aliases, edit your /root/.bash_profile

[root@domain ~]#

SOLUTION:

Once you login/connect with the server using SSH:

p link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue 
    link/void 
[root@domian ~]# ip link set eth0 mtu 1400
SIOCSIFMTU: No such device
[root@domian ~]# ip link set venet0 mtu 1400
[root@domian ~]# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1400 qdisc noqueue 
    link/void 
[root@domian ~]#

Источник

FileZilla – это специализированное FTP-приложение, которое используется для обмена файлами по сети. Работает по принципу «клиент-сервер». Но иногда при попытке подключится к серверу FileZilla, пользователи сталкиваются с ошибкой «не удалось получить список каталогов».

Содержание

  • 1 Чем вызвана ошибка?
  • 2 Создание правила в брандмауэре
  • 3 Изменение настроек шифрования
  • 4 Изменение конфигурации FTP
  • 5 Изменение имени хоста

Чем вызвана ошибка?

Ошибка получения списка каталогов при подключении к серверу FileZilla может возникнуть по ряду причин:

  1. Соединение заблокировано брандмауэром Windows. Даже если установлено исключение для определенного порта в этом инструменте контроля за трафиком, FileZilla использует «Пассивный режим» для получения или отправки файлов. То есть для передачи могут быть открыты любые порты TCP, при блокировке которых приложение выбрасывает эту ошибку.
  2. Используется зашифрованное соединение, при котором могут возникнуть проблемы с подключением к серверу.

Создание правила в брандмауэре

Сообщение о неполадке при получении списков каталогов часто возникает из-за блокировки брандмауэром подключения FileZilla. В этом решении сначала ограничим порты клиента, затем добавим их в список исключений межсетевого экрана.

Запустите FileZilla Server, щелкните на «Edit» и выберите «Settings».

На левой панели щелкните на опцию «Passive Mode Settings» и отметьте флажком «Use Custom Port Range».

В первом и во втором поле введите «2100» и сохраните настройки.

В меню Пуск кликните на значок шестеренки для входа в параметры Windows. Перейдите в раздел «Обновления и безопасность».

На вкладке Безопасность Windows откройте Брандмауэр и защита сети.

Перейдите в «Дополнительные параметры».

Затем кликните на «Правила для входящих подключений», на правой панели Действие выберите «Создать правило».

В открывшемся окне укажите тип правила «Для порта» и продолжите.

Отметьте флажком опции «протокол TCP», «Определенные локальные порты» и наберите в поле «21, 2100» и продолжите.

Примечание: вместо 21 впишите порт, который был указан при установке сервера.

В окне Действие установите флажок «Разрешить подключение».

В следующем окне отметьте все три профиля: доменный, частный, публичный и продолжите.

Присвойте имя новому правилу и нажмите на «Готово».

Повторите эти действия для создания исходящего правила.

После добавления правил проверьте, сохраняется ли проблема.

Изменение настроек шифрования

Проблема также связана с настройками шифрования. Чтобы исправить ошибку получения списков каталогов при подключении к серверу FileZilla попробуйте отключить шифрование. Выполните следующие шаги.

Откройте клиента FileZilla на клиентском компьютере. В верхнем меню приложения перейдите в Файл – Менеджер сайтов.

Если еще нет созданных подключений, кликните на кнопку «Новый сайт». Добавьте хост, логин и пароль для доступа к FTP.

В пункте «Тип входа» кликните на выпадающий список и установите значение «Нормальный». В пункте «Шифрование» разверните выпадающее меню и выберите «Использовать обычный FTP».

После попробуйте установить соединение.

Изменение конфигурации FTP

Если по-прежнему не удается подключиться к серверу FileZilla из-за проблем с получением списка каталога, попробуйте изменить параметры FTP соединения.

В меню клиента перейдите на вкладку Редактирование, затем щелкните на Настройки.

Разверните раздел Соединение — FTP. Отметьте опцию «Разрешить возврат к другому режиму при сбое».

Затем на вкладке «Активный режим» установите флажок на «Получить сведения о внешнем IP-адресе в настройках системы».

На вкладке «Пассивный режим» выберите опцию «Вернуться в активный режим».

Сохраните изменения и проверьте, возникает ли ошибка.

Изменение имени хоста

Иногда удается устранить проблему путем изменения имени хоста для инициализации определенного протокола.

Откройте клиента FileZilla и в основном окне приложения щелкните в поле хоста. Перед фактическим именем хоста наберите «sftp://».

Введите остальные данные и проверьте, удалось ли исправить ошибку получения списка каталогов.

Источник

Понравилась статья? Поделить с друзьями:
  • Sftp connection failed kex error
  • Sfml graphics d 2 dll ошибка
  • Sfm как изменить размер модели
  • Shippingpc bmgame exe ошибка batman как исправить
  • Shindaiwa real dual 500 ошибка e06