Chapter 10: Common error messages
This chapter lists a number of common error messages which PuTTY and its associated tools can produce, and explains what they mean in more detail.
We do not attempt to list all error messages here: there are many which should never occur, and some which should be self-explanatory. If you get an error message which is not listed in this chapter and which you don't understand, report it to us as a bug (see appendix B) and we will add documentation for it.
- 10.1 ‘The server's host key is not cached in the registry’
- 10.2 ‘WARNING - POTENTIAL SECURITY BREACH!’
- 10.3 ‘SSH protocol version 2 required by our configuration but server only provides (old, insecure) SSH-1’
- 10.4 ‘The first cipher supported by the server is ... below the configured warning threshold’
- 10.5 ‘Server sent disconnect message type 2 (protocol error): "Too many authentication failures for root"’
- 10.6 ‘Out of memory’
- 10.7 ‘Internal error’, ‘Internal fault’, ‘Assertion failed’
- 10.8 ‘Unable to use this private key file’, ‘Couldn't load private key’, ‘Key is of wrong type’
- 10.9 ‘Server refused our public key’ or ‘Key refused’
- 10.10 ‘Access denied’, ‘Authentication refused’
- 10.11 ‘No supported authentication methods available’
- 10.12 ‘Incorrect CRC received on packet’ or ‘Incorrect MAC received on packet’
- 10.13 ‘Incoming packet was garbled on decryption’
- 10.14 ‘PuTTY X11 proxy: various errors’
- 10.15 ‘Network error: Software caused connection abort’
- 10.16 ‘Network error: Connection reset by peer’
- 10.17 ‘Network error: Connection refused’
- 10.18 ‘Network error: Connection timed out’
- 10.19 ‘Network error: Cannot assign requested address’