Core FTP

WinSCP (vucstor user) says:
Cannot get real path for '.'.
No such file or directory.
Error code: 2
Error message from server: No such file

Server says:
[20181108 13:01:24] [197.232.66.102] connecting
[20181108 13:01:24] [197.232.66.102] connected
[20181108 13:01:25] [197.232.66.102] user 'vucstor' sent
[20181108 13:01:25] [197.232.66.102] USER-PASS (vucstor) success
[20181108 13:01:25] [197.232.66.102] user (vucstor) granted access
[20181108 13:01:37] [197.232.66.102] disconnected (vucstor)

FileZilla (transfer user) says:
Status: Connected to sftp.innomate.com
Error: Warning: failed to resolve home directory: no such file or directory
Status: Retrieving directory listing...
Command: pwd
Response: Current directory is: "."
Error: Failed to parse returned path.
Error: Failed to retrieve directory listing

Server says:
[20181108 13:05:27] [197.232.66.102] connecting
[20181108 13:05:27] [197.232.66.102] connected
[20181108 13:05:28] [197.232.66.102] user (transfer) granted access
[20181108 13:06:15] [197.232.66.102] disconnected (transfer)

FlashFxp works just fine.

What build is this - it may been fixed a while ago.

You can test ftp.coreftp.com anonymous to see if the issue occurs there.

I'm using Server v2 build 668, so if you have a fixed build, please release it?

I'm not seeing the issue on your ftp/sftp.

Was the home directory a unc path? If so it may be fixed in build 669

I seem to still be having this issue in 2019.
The first time I connect to the server through SSH/SFTP it works, but after that it's "No such file" until the next restart of CoreFTP server. I'm actually not sure how to find the version information (I'm having a dumb moment and can't find the about screen, if there is one)

Log:

Status: Connecting to LN1QAAPP06...
Status: Connected to LN1QAAPP06
Status: Retrieving directory listing...
Status: Directory listing of "/" successful
Status: Disconnected from server
Status: Connecting to LN1QAAPP06...
Status: Connected to LN1QAAPP06
Error: Warning: failed to resolve home directory: no such file or directory
Status: Retrieving directory listing...
Command: pwd
Response: Current directory is: "."
Error: Failed to parse returned path.
Error: Failed to retrieve directory listing

Correction fully restarting CoreFTP server fixes the problem for some longer period (but no more than a day,) whereas restarting just the service (not sure what the difference is here, but that's how it works out) fixes the problem for one connection (as previously described.)

was the user's home directory off the root drive (ie: f:\user)?

There was an issue related to shares and virtual paths with this, it may be the same issue.

I have a similar issue, i can't set my users homedirs outside the SFTP root folder.
Even with permissions set correctly, homedir can't be set or navigated to.
Tried mapping virtual folders, they show up on sftp but are empty.
So technically, if my root dir is on D:\ i can never access files on C:\ or E:\ ..

ForumAdmin wrote:
> was the user's home directory off the root drive (ie: f:\user)?
>
> There was an issue related to shares and virtual paths with this, it may be
> the same issue.

Are you saying we can only configure access to other folders on the same drive?