Troubleshooting Of Typical Errors; Address Already In Use; Could Not Open Xxx File; Decode Error - HP NonStop SSL Reference Manual

Invalid IPMODE specified, run mode EXPANDS does not support IPMODE DUAL
This error occurs when IPMODE DUAL was specified in run mode EXPANDS, however this is not supported in
runmode EXPANDS by design. Please set up one EXPANDS process for both IPMODE IPv4 and IPMODE IPv6 to
resolve the error condition.
Setting <interface_param> in IPMode DUAL is invalid since it defies the DUAL mode purpose of
allowing both IPv4 and IPv6 connections
This error indicates that at least one of INTERFACE or TARGETINTERFACE was specified in IPMODE DUAL.
To resolve the error condition, please either do not specify INTERFACE or TARGETINTERFACE or do run a
proxy process with the interface parameters set for IPMODE IPv4 and IPMODE IPv6.
Failed to restrict listen socket use to IPv6 only according to given IPMode IPv6
When opening up an IPv6 socket, by default it listens for incoming connections on both IPv4 and IPv6. When
running in IPMODE IPv6 a special socket option has to be set on the socket. This error message will occur if setting
this restriction flag fails. If you experience this error, please contact HP support.
Invalid <ALLOWIP/DENYIP> value given: <detailed reason>
This error indicates that the ALLOWIP and/or DENYIP parameter was set incorrectly. See end of the message for
the detailed reason which should give enough information to resolve the error condition. Also see parameter
description for ALLOWIP/DENYIP for further information.

Troubleshooting of Typical Errors

Address already in use

If the message "Fatal error: Could not listen on socket: Address already in use" appears, please check whether the Source
Port, which you assigned as PORT parameter is not in use by any other process.

Could not open xxx file

If the message "Could not open xxx file" appears, please check whether the file with the specified name (e.g. key file ,
certificate file, log file) is in use by any other process.

Decode Error

If a message with a "Decode Error" occurs in the HP NonStop SSL log, a client may have tried to create a non-secure
connection to a secure HP NonStop SSL server (FTPS, TELNETS, etc.).

Handshake Error

If a message with a "handshake error" occurs in the HP NonStop SSL log, please check the following:
•
does the client support the configured SSL protocol versions (MINVERSION, MAXVERSION)?
•
does the client support the configured CIPHERSUITES?
•
Is NonStop SSL run in client mode and the server side rejects the Client Hello? Please add the parameter
TLSEXTENSIONSESSIONTICKET with value FALSE to your NonStop SSL startup configuration. This will
disable one specific TLS Extension which is used by default in the Client Handshake. In general no TLS
implementation should fail due to this extension being sent since following the respective RFC, TLS extensions
shall be ignored if not understood. However there are some buggy implementations around which fail and reject
the Client Hello for that reason.
126 • Appendix
HP NonStop SSL Reference Manual