Confirmed. I cleaned up my env and SCP is working fine now. Sorry for the false report; and thanks for the assistance!
- mj
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.
Topic review
- martin
Note that I am using a leveraged bash environment for the moment on the remote node and there are some irrevalent entries in the files for this system.
That's it. See
https://winscp.net/eng/docs/requirements#remote_environment
- mj
Hi, and thanks for your reply!
I have attached a log of me opening WinSCP, double-clicking on the last "directory" icon on the remote side (nothing happens); and then I close WinSCP. I have also attached a snapshot of WinSCP's remote view for your reference.
As to why I chose SCP over SFTP? Stupidity? I looked at the documentation on the WinSCP site, and the matric comparing the three different protocols and I thought SCP may be the way to go.
As it turns out, if I use SFTP, WinSCP displays my remote connection correctly and I don't have any problems.
Note that I am using a leveraged bash environment for the moment on the remote node and there are some irrevalent entries in the files for this system. If that affects WinSCP, feel free to disregard this ticket. I will clean up my environment and if I still see an issue I can re-post at that time.
Thanks again for the assistance.
I have attached a log of me opening WinSCP, double-clicking on the last "directory" icon on the remote side (nothing happens); and then I close WinSCP. I have also attached a snapshot of WinSCP's remote view for your reference.
As to why I chose SCP over SFTP? Stupidity? I looked at the documentation on the WinSCP site, and the matric comparing the three different protocols and I thought SCP may be the way to go.
As it turns out, if I use SFTP, WinSCP displays my remote connection correctly and I don't have any problems.
Note that I am using a leveraged bash environment for the moment on the remote node and there are some irrevalent entries in the files for this system. If that affects WinSCP, feel free to disregard this ticket. I will clean up my environment and if I still see an issue I can re-post at that time.
Thanks again for the assistance.
- martin
Re: Missing directory names on remote node
Please attach a full log file showing the problem (using the latest version of WinSCP).
Anyway, why are you using SCP? Did you consider/try SFTP?
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.
Anyway, why are you using SCP? Did you consider/try SFTP?
- mj
Missing directory names on remote node
I am using WinSCP v5.5.4 on Windows 8.1 (and Windows 7). I'm connecting to an Amazon Machine Image (AMI) via SCP, but the remote-side panel is not displaying the directories for the remote system correctly. The directory names are missing altogether (although there _is_ a generic icon), and I can't traverse them.
However, the phenomenon only occurs for a single user account on the AMI (which is running Ubuntu 14.04, and Bash). Any ideas regarding what the issue could be with the user account that is not working correctly?
However, the phenomenon only occurs for a single user account on the AMI (which is running Ubuntu 14.04, and Bash). Any ideas regarding what the issue could be with the user account that is not working correctly?