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: Log file as requested

Thanks for the log.

The initial workaround implemented in 5.7.1 was not conforming to SFTP specification. So it broke compatibility with some other servers.
I had to make the workaround apply for ProFTPD specifically only, since 5.7.2.

But your server does not identify itself as ProFTPD, but as "netfirms FTP Server Ready". So WinSCP does not apply the workaround.

You should contact your hosting provider to upgrade their ProFTPD server. Or at least re-configure it to correctly identify as ProFTPD.

Log file as requested

I've attached the log file.
I performed one directory creation using the Normal level of logging and one using Debug 1.

Re: Can't create directory - SSH_FXP_REALPATH with SFTP version 6 a problem in 5.7.6

Please attach a full log file showing the problem (using the latest version of WinSCP).

To generate 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.

Can't create directory - SSH_FXP_REALPATH with SFTP version 6 a problem in 5.7.6

I recently upgraded to 5.7.6 and found that I couldn't create directories using SFTP.

After some reading and investigation I found that this was a problem that was fixed in 5.7.1. (

Rolling back to 5.7.1 fixed the problem.

Another workaround was to change to version 5.

So...still a problem in latest release.