Differences
This shows you the differences between the selected revisions of the page.
| 2012-03-28 | 2012-03-28 | ||
| removed (203.223.189.78) (hidden) | Restored revision 1332745230. Undoing revision 1332919032. (martin) (hidden) | ||
| Line 1: | Line 1: | ||
| + | ====== Common Error Messages ====== | ||
| + | |||
| + | |||
| + | |||
| + | ~~SPLIT~~ | ||
| + | |||
| + | ===== [[host_key]] The server's host key was not found in the cache ===== | ||
| + | This error message occurs when WinSCP connects to a new [[SSH]] server. Every server identifies itself by means of a host key; once WinSCP knows the host key for a server, it will be able to detect if a malicious attacker redirects your connection to another machine. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | If you see this message, it means that WinSCP has not seen this host key before, and has no way of knowing whether it is correct or not. You should attempt to verify the host key by other means, such as asking the machine's administrator. | ||
| + | |||
| + | If you see this message and you know that your installation of WinSCP has connected to the same server before, it may have been recently upgraded to SSH protocol version 2. SSH protocols 1 and 2 use separate host keys, so when you first use SSH-2 with a server you have only used SSH-1 with before, you will see this message again. You should verify the correctness of the key as before. ((&puttydoccite)) | ||
| + | |||
| + | Read more about [[ssh#verifying_the_host_key|verifying host keys]]. | ||
| + | |||
| + | Learn also how to [[scripting#hostkey|accept host key automatically in script]]. | ||
| + | |||
| + | ===== [[security_breach]] Warning - Potential security breach! ===== | ||
| + | This message, followed by "The server's host key does not match the one WinSCP has is cache", means that WinSCP has connected to the SSH server before, knows what its host key should be, but has found a different one. | ||
| + | |||
| + | This may mean that a malicious attacker has replaced your server with a different one, or has redirected your network connection to their own machine. On the other hand, it may simply mean that the administrator of your server has accidentally changed the key while upgrading the SSH software; this shouldn't happen but it is unfortunately possible. | ||
| + | |||
| + | You should contact your server's administrator and see whether they expect the host key to have changed. If so, verify the new host key in the same way as you would if it was new. ((&puttydoccite)) | ||
| + | |||
| + | Read more about [[ssh#verifying_the_host_key|verifying host keys]]. | ||
| + | |||
| + | ===== [[connection_refused]] Network error: Connection refused ===== | ||
| + | You may get this message when connecting to a server for following reasons: | ||
| + | * You are trying to use WinSCP for a purpose for which it is not designed. [[requirements|WinSCP needs]] a SSH or FTP server to be installed at the other end (on the machine you want to connect to). In particular, you cannot easily use it to connect to another Windows workstation, since Windows does not have an SSH or FTP server included by default. Please refer to [[guide_exchange|FAQ]]. | ||
| + | * You are trying to use [[protocol]] that the server does not support. Particularly you are trying SFTP/SCP (over SSH), but the server supports FTP; or vice versa. Check selected protocol on [[ui_login_session#protocol_group|login dialog]]. Note that WinSCP defaults to SFTP protocol, while most other similar applications default to FTP. | ||
| + | * The server is running on non-standard port. Please make sure you enter actual port number on [[ui_login_session|login dialog]]. | ||
| + | * You may need to connect through proxy server, but you have not specified one on [[ui_login_proxy|login dialog]]. | ||
| + | * Connection was blocked by firewall. Please refer to [[faq_connection_refused|FAQ]]. | ||
| + | |||
| + | |||
| + | If you are trying to use WinSCP to connect to your iPhone, iPod Touch or iPad, please refer to [[faq_iphone|FAQ]]. | ||
| + | |||
| + | ==== In Other Languages ==== | ||
| + | * //Deutsch - // Netzwerkfehler: Verbindung abgelehnt | ||
| + | * //Español - // Error de Red: Conexión Rechazada | ||
| + | * //Français - // Erreur réseau : connexion refusée | ||
| + | * //Italiano - // Errore di rete: connessione rifiutata | ||
| + | |||
| + | ===== [[connection_refused_ftp]] No connection could be made because the target machine actively refused it ===== | ||
| + | The same as [[message_connection_refused|"Network error: Connection refused"]]. | ||
| + | |||
| + | ===== [[connection_timed_out]] Network error: Connection timed out ===== | ||
| + | All reasons and hints for [[message_connection_refused|"Network error: Connection refused"]] apply to this error too. | ||
| + | |||
| + | ===== [[no_route_to_host]] Network error: No route to host ===== | ||
| + | All reasons and hints for [[message_connection_refused|"Network error: Connection refused"]] apply to this error too. | ||
| + | It may also be worth trying again later as this error can be due to temporary network issue. | ||
| + | |||
| + | ===== [[timeout_detected]] Timeout detected ===== | ||
| + | If you are getting this error, first try to set longer [[ui_login_connection|timeout interval]]. | ||
| + | |||
| + | If this does not help and 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 [[ftp|FTP protocol]] you can also try to use [[ui_login_connection#connection|passive mode]]. | ||
| + | |||
| + | ===== [[software_caused_connection_abort]] Network error: Software caused connection abort ===== | ||
| + | ==== While Connecting ==== | ||
| + | You may get this message when connecting to a server for following reasons: | ||
| + | * Connection was blocked by firewall. Please refer to [[faq_connection_refused|FAQ]]. | ||
| + | * All reasons and hints for [[message_unexpected_close|"Server unexpectedly closed network connection"]] apply to this error too. | ||
| + | |||
| + | ==== In a Middle of Session ==== | ||
| + | If you are getting the error in the middle of session, it means that Windows network code killed an established connection for some reason. For example, it might happen if you pull the network cable out of the back of an Ethernet-connected computer, a DHCP IP address renewal fails or changes the computer's IP address, or if Windows has any other similar reason to believe the entire network has become unreachable. | ||
| + | |||
| + | Windows also generates this error if it has given up on the machine at the other end of the connection ever responding to it. If the network between your client and server goes down and your client then tries to send some data, Windows will make several attempts to send the data and will then give up and kill the connection. In particular, this can occur even if you didn't do anything, if you are using SSH-2 and WinSCP attempts a [[ui_login_kex#reexchange|key re-exchange]]. | ||
| + | |||
| + | The problem can be caused also by the firewall. Try to disable it temporarily to see if the problem persists. Refer to [[faq_connection_refused|FAQ]]. | ||
| + | |||
| + | It can also occur if you are using [[ui_login_connection#keepalives|keepalives]] in your connection. Other people have reported that keepalives fix this error for them. ((&puttydoccite)) | ||
| + | |||
| + | If you find DHCPNACK errors in the Event Viewer, your DHCP server may be briefly denying your IP address, causing your existing connections to fail. Where possible, this can be addressed by reserving a specific IP address on the DHCP server (e.g. cable modem/router), setting that as the static IP address, and disabling the DHCP client service. | ||
| + | |||
| + | ===== [[host_does_not_exist]] Host does not exist ===== | ||
| + | You may get this message when connecting to a server for following reasons: | ||
| + | * You may have typed a wrong hostname on Login dialog. | ||
| + | * Your domain name is new and is not fully distributed to DNS servers yet. | ||
| + | * Connection was blocked by firewall. Please refer to [[faq_connection_refused|FAQ]]. | ||
| + | * Problem with DNS server. | ||
| + | * Common mistake is to enter full URL (e.g. ''%%ftp://ftp.example.com%%'') as hostname on Login dialog instead of actual hostname (e.g. ''%%ftp.example.com%%''). | ||
| + | |||
| + | ===== [[no_data_of_requested_type_found]] The requested name is valid, but no data of the requested type was found ===== | ||
| + | All reasons and hints for [[message_host_does_not_exist|"Host does not exist"]] apply to this error too. | ||
| + | |||
| + | ===== [[error_code_4]] General failure; Error code: 4 ===== | ||
| + | You probably see error message like: | ||
| + | |||
| + | //General failure (server should provide error description).\\ | ||
| + | Error code: 4\\ | ||
| + | Error message from server: Failure\\ | ||
| + | Request code: ?// | ||
| + | |||
| + | What does particular error code mean is explained on the line above, i.e. "General failure" here. Particularly for "General failure", the SFTP server should provide you more details, that you will see next to "Error message from server". Unfortunately, SFTP server shipped with OpenSSH (or Sun SSH) does not. That is, why you see there just "Failure" (very useful). | ||
| + | |||
| + | Some situations when OpenSSH (Sun SSH) server issues this useless error message: | ||
| + | * Renaming file to name of already existing file. | ||
| + | * Creating directory that already exists. | ||
| + | * Moving remote file to different filesystem (HDD). | ||
| + | * Uploading file to full filesystem (HDD). | ||
| + | * Exceeding user disk quota. | ||
| + | |||
| + | If none of the above helps, check your permissions or contact server administrator. | ||
| + | |||
| + | ===== [[unexpected_close]] Server unexpectedly closed network connection ===== | ||
| + | ==== While Connecting ==== | ||
| + | If you get this error message while connecting to your server, it is most usually caused by the server not being able to run some process necessary to support your session. Always try to connect with another SSH (SFTP) client to find, if it is server or client related problem. | ||
| + | |||
| + | Possibilities are: | ||
| + | * Shell. | ||
| + | * 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. | ||
| + | * 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 group writeable permissions to chroot directory). | ||
| + | * Some environments require specific permissions (e.g. 755) to files like ''.profile'' or ''.bashrc''. | ||
| + | * 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. | ||
| + | * SSH server: | ||
| + | * Your SSH server, particularly OpenSSH, may not be able to access the server key files, due to an incorrect permissions. | ||
| + | |||
| + | ==== In a Middle of Session ==== | ||
| + | If you get this error message in a middle of the session, it is usually caused by some fatal error on server. The server error may possibly be initiated by error on client (WinSCP) side. | ||
| + | |||
| + | In both cases check log file of your server to see an actual reason, it closed connection for. | ||
| + | |||
| + | If the problem repeats, try turning off //[[ui_login_connection|Optimize connection buffer size]]//. | ||
| + | |||
| + | ===== Incoming packet was garbled on decryption ===== | ||
| + | This error occurs when WinSCP decrypts an SSH packet and the decrypted data makes no sense. This probably means something has gone wrong in the encryption or decryption process. It's difficult to tell from this error message whether the problem is in the client or in the server. | ||
| + | |||
| + | You can try enabling //[[ui_login_bugs#sshbug_maxpkt2|Ignores SSH-2 maximum packet size]]// session option. | ||
| + | |||
| + | ===== [[exit_status_1]] Connection has been unexpectedly closed. Server sent command exit status 1 (or 255 or 0) ===== | ||
| + | All reasons and hints for [[message_unexpected_close|"Server unexpectedly closed network connection"]] apply to this error too. | ||
| + | |||
| + | ===== [[reset_by_peer]] Network error: Connection reset by peer ===== | ||
| + | All reasons and hints for [[message_unexpected_close|"Server unexpectedly closed network connection"]] apply to this error too. | ||
| + | |||
| + | ===== [[host_is_not_communicating]] Host is not communicating for more than 15 seconds. Still waiting... Warning: Aborting this operation will close connection! ===== | ||
| + | You get this message when WinSCP is waiting for response from the server for more than [[ui_login_connection#server_response_timeout|configured time]]. Note that this is not an error message, WinSCP still keeps waiting. If the server responds finally, the message goes away automatically. The message box is shown only to give you a chance to break the connection and reconnect, if you do not want to wait anymore. | ||
| + | |||
| + | If the server never replies, it may be because of some fatal error on the server side. Also something may be interfering with the connection, preventing the server response from arriving or possibly even the original request to arrive at the server. | ||
| + | |||
| + | If the problem repeats, try turning off //[[ui_login_connection|Optimize connection buffer size]]//. | ||
| + | |||
| + | ==== In Other Languages ==== | ||
| + | * //Deutsch - // Der entfernte Rechner kommuniziert seit mehr als 15 Sekunden nicht mehr. Warte... Warnung: Der Abbruch dieser Operation beendet die Verbindung! | ||
| + | * //Español - // El servidor no se ha comunicado por mas de 15 segundos. Sigo esperando... Aviso: si abortas la operación la sesión se cerrará! | ||
| + | * //Français - // L'hôte n'a pas répondu pendant plus de 15 secondes. Toujours en attente... Attention : Annuler cette opération va fermer la connexion ! | ||
| + | * //Italiano - // L'host non sta comunicando per più di 15 secondi. In attesa... Avviso: Interrompendo questa operazione chiuderai la connessione! | ||
| + | |||
| + | ===== [[access_denied]] Access denied ===== | ||
| + | You will get the error while authenticating when: | ||
| + | * You have entered incorrect password, used non-authorized key, etc. | ||
| + | * The account you are trying to use cannot be logged in. This can be case even when you get "Access denied" only after entering password, as for security reasons, many servers do not reveal information about the accounts. Reasons for not being allowed to login include: | ||
| + | * The account (username) you have entered on Login dialog does not exist at all. | ||
| + | * The account is disabled. | ||
| + | * The password has expired. | ||
| + | * Number of parallel sessions allowed for the account has been exceeded. | ||
| + | * You are trying to connect with super-user account (''root''), without having allowed that. Please read [[faq_su|FAQ]]. | ||
| + | It may help to check log file of your server to see an actual reason, it denied you an access. | ||
| + | |||
| + | If you are not controlling the server, seek help with your server administrator (e.g. your webhosting provider). | ||
| + | |||
| + | ===== [[permission_denied]] Permission denied ===== | ||
| + | You do not have a sufficient permissions (access rights) to a resource, such as a file or directory, to perform the operation. | ||
| + | |||
| + | You should contact the server administrator to resolve the problem. | ||
| + | |||
| + | Access rights systems differ with operating system and the file server. With the most common combination of Unix-based system and OpenSSH: | ||
| + | * To see a directory contents you need to have read permissions to the directory; | ||
| + | * To read a file you need to have read permissions to the file; | ||
| + | * To write a file you need to have a write permissions to the file; | ||
| + | * To create or delete file you need have a write permissions to the directory; | ||
| + | * To change file or directory permissions you need to be its owner; | ||
| + | * To change file modification time you need to be its owner (note that by default WinSCP [[ui_transfer#common_options|updates file modification time]] when uploading). | ||
| + | |||
| + | ===== [[too_many_authentication_failures]] Server sent disconnect message type 2 (protocol error): "Too many authentication failures for root" ===== | ||
| + | This message is produced by an OpenSSH (or Sun SSH) server if it receives more failed authentication attempts than it is willing to tolerate. | ||
| + | |||
| + | This can easily happen if you are using [[ui_pageant|Pageant]] and have a large number of keys loaded into it, since these servers count each offer of a public key as an authentication attempt. This can be worked around by specifying the key that's required for the authentication in the [[ui_login_session|session configuration]]; WinSCP will ignore any other keys Pageant may have, but will ask Pageant to do the authentication, so that you don't have to type your passphrase. ((&puttydoccite)) | ||
| + | |||
| + | ===== [[key_is_of_wrong_type]] Unable to use this private key file, Couldn't load private key, Key is of wrong type ===== | ||
| + | If you see one of these messages, it often indicates that you've tried to load a key of an inappropriate type into WinSCP. | ||
| + | |||
| + | You may have specified a key that's inappropriate for the connection you're making. The SSH-1 and SSH-2 protocols require different private key formats, and a SSH-1 key can't be used for a SSH-2 connection (or vice versa). | ||
| + | |||
| + | Alternatively, you may have tried to load an SSH-2 key in a "foreign" format (OpenSSH or ssh.com), in which case you need to [[public_key#private|import it into PuTTY's native format]]. ((&puttydoccite)) | ||
| + | |||
| + | ===== [[unexpected_directory_listing]] Unexpected directory listing line '...' ===== | ||
| + | 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>] | ||
| + | |||
| + | Some common examples: | ||
| + | |||
| + | drw-r--r-- 3 martinp users 4596 2007-06-06 11:18:33.000000000 +0200 private | ||
| + | |||
| + | lrwxrwxrwx 1 martinp users 4 Mar 24 2005 wiki -> dokuwiki | ||
| + | |||
| + | drwxr-xr-x+ 2 martinp users 96 Oct 26 14:58 httpdocs | ||
| + | |||
| + | If your listing does not correspond to some of the above: | ||
| + | * 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. | ||
| + | * Alter output of ''ls'' command to match any of the supported formatting. WinSCP has few session options that may be used for that, including: | ||
| + | * //[[ui_login_scp#directory_listing|Listing command]]// (e.g. use ''sed'' to modify output of ''ls'' command to match the WinSCP requirements); | ||
| + | * //[[ui_login_scp#other_options|Clear aliases]]// (may help if the ''ls'' command is aliased to display non standard output) and | ||
| + | * //[[ui_login_scp#other_options|Clear national variables]]// (may help if your listing does not use English month names). | ||
| + | * Make sure you are using ''bash'' shell. If you do not want to set it as your default shell, [[ui_login_scp#shell|force it]] for WinSCP sessions. | ||
| + | |||
| + | ===== [[large_packet]] Received too large (... B) SFTP packet. Max supported packet size is 102400 B ===== | ||
| + | If ... (from the subject) is a very large number then the problem is typically caused by a message printed from some profile/logon script. It violates the SFTP protocol. Some of these scripts are executed even for [[requirements#configuring_winscp_sessions|non-interactive (no TTY) sessions]], so they cannot print anything (nor ask user to type something). | ||
| + | |||
| + | The number ... represents the first four bytes read from the server. If your login scripts are printing words, this will be the first four characters cast into a number, and not an SFTP message at all. | ||
| + | |||
| + | To fix the problem find out what command in your login script prints text. Once you find it move the command to the proper interactive script, or remove it entirely. The scripts are usually hidden (their name starts with dot) and are located in your home directory on the server. Typically you will need to move the commands from ''.bashrc'' script to ''.bash_profile''. | ||
| + | |||
| + | There are other possible sources of the message in addition to the profile script - some SSH servers print messages if they are unable to start the SFTP server, or encounter a fatal error. You should contact your server administrator. | ||
| + | |||
| + | Another possibility is that the server is configured to only allow the SCP protocol and not the SFTP protocol, in such a way that SCP fallback mechanism of WinSCP does not work. The solution is to choose SCP protocol on the [[ui_login_session|login dialog]]. | ||
| + | |||
| + | ===== [[return_code_127]] Command failed with return code 127 (or 255) ===== | ||
| + | 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 [[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. | ||
| + | |||
| + | You can also try to run the respective command from terminal (with the same account that you use with WinSCP), to verify that you can execute it. You may not have sufficient permissions, or the command dependencies may not be installed. | ||
| + | |||
| + | Common situations, in which you may get the error: | ||
| + | * Transferring files fails, because path to ''scp'' command is not in ''PATH''; | ||
| + | * Error appears while logging in, because your *nix distribution lacks ''groups'' command. You can instruct WinSCP not to use the command in [[ui_login_scp#other_options|session settings]]. | ||
| + | |||
| + | ===== [[not_able_to_determine_application_started]] WinSCP was not able to determine application that was started to open the file. WinSCP cannot watch for changes in the file and thus it will not upload the changed file back ===== | ||
| + | |||
| + | See [[task_edit#mdi|documentation]]. | ||
| + | |||
| + | ===== [[startup_message]] Error skipping startup message. Your shell is probably incompatible with the application (BASH is recommended) ===== | ||
| + | This error is typically associated with another error. If there is no other error in the message, try searching a [[logging|session log file]]. | ||
| + | |||
| + | ===== [[empty_listing_for_directory]] Server returned empty listing for directory ===== | ||
| + | Check that you have read and execute permissions to the directory. | ||
| + | |||
| + | ===== [[timeout_external_console]] Timeout waiting for external console to complete the command ===== | ||
| + | This error indicates that ''[[executables|winscp.exe]]'' did not receive an answer from ''[[executables|winscp.com]]'' in time. | ||
| + | |||
| + | Most commonly this happens when ''winscp.com'' has redirected output to a stream with limited buffer. If the stream is not being read from, the buffer gets eventually filled and ''winscp.com'' hangs, when trying to write into it. | ||
| + | |||
| + | In turn the above most commonly happens when ''winscp.com'' is run from another program (such as .NET code), which redirect its output into stream. If the program then e.g. waits for ''winscp.com'' to finish without reading from the stream, the ''winscp.com'' eventually hangs, never finishing. | ||
| + | |||
| + | See example of [[guide_dotnet|.NET]] or [[guide_automation_advanced#inout|WSH]] code dealing with the problem. | ||
| + | |||
| + | ===== [[error_listing_directory]] Error listing directory ===== | ||
| + | This is high-level error, and it is typically associated with another error, such as: | ||
| + | * [[message_timeout_detected|Timeout detected]]; | ||
| + | * [[message_unexpected_directory_listing|Unexpected directory listing line '...']]. | ||
| + | |||
| + | ===== [[cannot_initialize_sftp_protocol]] Cannot initialize SFTP protocol. Is the host running a SFTP server? ===== | ||
| + | The error is frequently associated (and caused by) with following errors: | ||
| + | * [[message_unexpected_close|"Server unexpectedly closed network connection"]]; | ||
| + | * [[message_exit_status_1|"Connection has been unexpectedly closed. Server sent command exit status 1 (or 255 or 0)"]]; | ||
| + | * [[message_large_packet|"Error Received too large (... B) SFTP packet. Max supported packet size is 102400 B"]]. | ||
| + | |||
| + | ===== [[cannon_open_active_connection]] The server cannot open connection in active mode. If you are behind a NAT router, you may need to specify an external IP address. Alternatively, consider switching to passive mode. ===== | ||
| + | The error happens when the server does not open connection to WinSCP to perform file or directory listing transfer. | ||
| + | |||
| + | To resolve the problem try: | ||
| + | * Specifying your [[ui_pref_network|external IP address]]; | ||
| + | * Switching to [[ui_login_connection|passive mode]]. | ||
| + | |||
| + | ===== [[name_no_data]] The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for ===== | ||
| + | The usual example for this is a host name-to-address translation attempt which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable. | ||
| + | |||
| + | This can possibly happen for newly registered domain names that are no fully setup yet. | ||
| + | |||
| + | ===== [[invalid_access_to_memory]] Invalid access to memory ===== | ||
| + | This error message is not useful for you as an end-user. It generally means that there is a bug in the software. Please [[reporting|report the bug]]. | ||
| + | |||
| + | <nosplit> | ||
| + | ===== Other References ===== | ||
| + | SSH code of WinSCP is based on PuTTY. So if you are getting some error message while using [[protocol|SFTP or SCP protocols]] (particularly while connecting), you may check also the [[&url(puttydoc)/Chapter10.html|common error messages]] in PuTTY documentation. | ||
| + | </nosplit> | ||