Anonymous wrote:

Ok, this is on a FreeBSD server w/cPanel. Currently each user does not have Shell access. Could this be the problem?

May be.

If this is the problem, is there any way to allow them to SFTP without giving them shell access?

I have not experiences with this, sorry :-(

Ok, this is on a FreeBSD server w/cPanel. Currently each user does not have Shell access. Could this be the problem? If this is the problem, is there any way to allow them to SFTP without giving them shell access?

Also, each user does not have a private profile and the global profile should not have any problems as you mentioned because the main account is able to use this app without it erroring out.

Any other suggestions?

Anonymous wrote:

Thanks for the quick response. Unfortunately, this is all chinese (or lating) to me. Can you please explain in more detail? What does "Shel" mean? How can I trace this? What would I need to do to correct this?

Have you read the F.A.Q?
There may several profile scripts (like .profile, .bash_rc, etc.)on the server (either global or your private). Some of these files print a message (first four letters of the message are "Shel", this is what I've decoded that the number 1399350636). This is a violation of the SFTP protocol. You must edit (or ask your administrator to do it) the file to remove the message.

If you need the message to be shown when you login in using SSH terminal, then you must move the command that generates it to other script, which get executed only for TTY sessions. Or to make check in the script for TTY.

If you do not understand, what I'm writting here, than forward it to your server administrator :-)

Thanks for the quick response. Unfortunately, this is all chinese (or lating) to me. Can you please explain in more detail? What does "Shel" mean? How can I trace this? What would I need to do to correct this?

Thank you,
Alex

martin wrote:

I have just added this problem to the [url=<invalid hyperlink removed by admin>#3169]F.A.Q.[/url] Please read it there.

Just addition (will make sense after you read F.A.Q. :-)): 1399350636 represents "Shel". It may help to trace it.

I have just added this problem to the F.A.Q. Please read it there.

Just addition (will make sense after you read F.A.Q. :-)): 1399350636 represents "Shel". It may help to trace it.

Newbie here,

WinSCP is working like a charm for my main website, but when I try to use it on another account, It logs in correctly and the password accepts but then It just closes. See log file for info:

Looking up host "xxx.xxx.xxx.xxx"
. Connecting to xxx.xxx.xxx.xxx port 22
. Server version: SSH-1.99-OpenSSH_3.6.1p1 FreeBSD-20030423
. We claim version: SSH-2.0-WinSCP-release-3.5
. Using SSH protocol version 2
. Doing Diffie-Hellman group exchange
. Doing Diffie-Hellman key exchange
. Host key fingerprint is:
. ssh-dss 1024 e2:05:0b:25:7b:19:d4:b7:27:1a:20:df:9e:2d:05:ff
. Initialised AES-256 client->server encryption
. Initialised AES-256 server->client encryption
! Using username "xxxxx".
. Server prompt (Password:)
. Access granted
. Opened channel for session
. Started a shell/command
. --------------------------------------------------------------------------
. Using SFTP protocol.
. Doing startup conversation with host.
> Type: SSH_FXP_INIT, Size: 5, Number: -1
. Server sent command exit status 0
. All channels closed. Disconnecting
* (ESshFatal) Cannot initialize SFTP protocol. Is the host running a SFTP server?
* Received too large (1399350636 B) SFTP packet. Max supported packet size is 102400 B.

What is wrong?

Thank you,
Alex