Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Re: WinSCP SSH error "Cannot get real path"

It's probably a server-side bug. If you want us to investigate further, please attach a full session log file showing the problem (using the latest version of WinSCP). Use Debug 2 log level.

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

WinSCP SSH error "Cannot get real path"

We are having an issue with clients connecting to our FTP server using WinSCP with SFTP. Users can connect but get an error when browsing to an empty directory or trying to go back a folder.

Error when going into an empty folder is "Server returned an Empty Listing",

Error when going back to root is: "cannot get real path for /folder/"

Any ideas? SFTP works in other clients like Filezilla and FTPS works in Winscp

Thank you!