Differences
This shows you the differences between the selected revisions of the page.
| 2011-05-29 | 2011-07-30 | ||
| no summary (Petr) | sftp (martin) | ||
| Line 56: | Line 56: | ||
| If you are getting the error while logging in or while initiating file transfer, all reasons and hints for [[message_connection_refused|"Network error: Connection refused"]] apply to this error too. | If you are getting the error while logging in or while initiating file transfer, all reasons and hints for [[message_connection_refused|"Network error: Connection refused"]] apply to this error too. | ||
| - | With [[protocols#ftp|FTP protocol]] you can also try to use [[ui_login_connection#passive_mode|passive mode]]. | + | With [[ftp|FTP protocol]] you can also try to use [[ui_login_connection#passive_mode|passive mode]]. |
| ===== [[software_caused_connection_abort]] Network error: Software caused connection abort ===== | ===== [[software_caused_connection_abort]] Network error: Software caused connection abort ===== | ||
| Line 111: | Line 111: | ||
| * Your account may not be allowed to start a shell at all. With some servers (like OpenSSH or Sun SSH), you may need to be allowed to start a shell, even if using SFTP protocol. | * Your account may not be allowed to start a shell at all. With some servers (like OpenSSH or Sun SSH), you may need to be allowed to start a shell, even if using SFTP protocol. | ||
| * Also some servers refuse to start a shell if your password has expired or your account was terminated. | * Also some servers refuse to start a shell if your password has expired or your account was terminated. | ||
| - | * Some shells do not work with non-interactive sessions. The same it true for some configurations (or profiles used) for otherwise working shells. This commonly exhibits with [[protocols#scp|SCP protocol]] with associated error message [[message_startup_message|"Error skipping startup message. Your shell is probably incompatible with the application (BASH is recommended)."]] Try to force ''bash'' shell explicitly on [[ui_login_scp|SCP/Shell tab]] of Login dialog. Using [[protocols#sftp|SFTP protocol]] instead of SCP is another option. | + | * Some shells do not work with non-interactive sessions. The same it true for some configurations (or profiles used) for otherwise working shells. This commonly exhibits with [[scp|SCP protocol]] with associated error message [[message_startup_message|"Error skipping startup message. Your shell is probably incompatible with the application (BASH is recommended)."]] Try to force ''bash'' shell explicitly on [[ui_login_scp|SCP/Shell tab]] of Login dialog. Using [[sftp|SFTP protocol]] instead of SCP is another option. |
| * OpenSSH server may fail to start shell when chroot is configured, but not possible (e.g. due to permissions). | * OpenSSH server may fail to start shell when chroot is configured, but not possible (e.g. due to permissions). | ||
| * SFTP server. Your account may not be able to start SFTP server binary (e.g. ''/bin/sftp-server'') or the binary is not present on your server. Your SSH server may also lack the SFTP subsystem. | * SFTP server. Your account may not be able to start SFTP server binary (e.g. ''/bin/sftp-server'') or the binary is not present on your server. Your SSH server may also lack the SFTP subsystem. | ||
| Line 174: | Line 174: | ||
| ===== [[unexpected_directory_listing]] Unexpected directory listing line '...' ===== | ===== [[unexpected_directory_listing]] Unexpected directory listing line '...' ===== | ||
| - | You will get the error with [[protocols#scp|SCP protocol]], if output of ''ls'' command cannot be parsed by WinSCP. WinSCP expects listing in format: | + | You will get the error with [[scp|SCP protocol]], if output of ''ls'' command cannot be parsed by WinSCP. WinSCP expects listing in format: |
| <type><permissions> <inode> <owner> <group> <size> <timestamp> <filename>[ -> <target>] | <type><permissions> <inode> <owner> <group> <size> <timestamp> <filename>[ -> <target>] | ||
| Line 186: | Line 186: | ||
| If your listing does not correspond to some of the above: | If your listing does not correspond to some of the above: | ||
| - | * Try using [[protocols#sftp|SFTP protocol]] instead of SCP. | + | * Try using [[sftp|SFTP protocol]] instead of SCP. |
| * Always make sure you are using the latest version of WinSCP, as support for different listing format is being added continuously. | * Always make sure you are using the latest version of WinSCP, as support for different listing format is being added continuously. | ||
| * Alter output of ''ls'' command to match any of the supported formatting. WinSCP has few session options that may be used for that, including: | * Alter output of ''ls'' command to match any of the supported formatting. WinSCP has few session options that may be used for that, including: | ||
| Line 206: | Line 206: | ||
| ===== [[return_code_127]] Command failed with return code 127 (or 255) ===== | ===== [[return_code_127]] Command failed with return code 127 (or 255) ===== | ||
| - | You will get the error with [[protocols#scp|SCP protocol]], if command necessary for facilitate operation you were trying to do does not exist on remote server or the shell cannot find it. | + | You will get the error with [[scp|SCP protocol]], if command necessary for facilitate operation you were trying to do does not exist on remote server or the shell cannot find it. |
| - | If you are not an experienced Unix user, you should first try using [[protocols#sftp|SFTP protocol]] instead. | + | If you are not an experienced Unix user, you should first try using [[sftp|SFTP protocol]] instead. |
| If you are sure that the command exists on the remote server, make sure that WinSCP (or rather the shell) can find it. You may need to add path to the command to ''PATH'' environment variable. Also make sure that the startup script that sets ''PATH'' is actually executed for non-interactive sessions. | If you are sure that the command exists on the remote server, make sure that WinSCP (or rather the shell) can find it. You may need to add path to the command to ''PATH'' environment variable. Also make sure that the startup script that sets ''PATH'' is actually executed for non-interactive sessions. | ||