--- title: "TLS handshake issues" slug: "uws-ag-troubleshooting-tls-handshake-issues-3-29" updated: 2026-08-07T08:02:31Z published: 2026-08-07T08:02:31Z canonical: "docs.onespan.com/uws-ag-troubleshooting-tls-handshake-issues-3-29" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # TLS handshake issues ## Description/symptoms In some cases, configuring OneSpan User Websites manually with the admintool autoadd command completes successfully, and the web applications appear to be configured correctly. However, the instance cannot authenticate users or communicate with the configured OneSpan Authentication Server instance due to TLS handshake errors, such as "CommsProtocolException: Error -904 (soap_ssl_accept)". ## Possible causes - The URL hostname/IP address used to connect to the OneSpan Authentication Server instance does not match the common name (CN) or subject alternative name (SAN) in the used SOAP certificate (see [Configure primary and backup OneSpan Authentication Server instances](/sec/docs/uws-ag-configure-primary-and-backup-onespan-authentication-server-instances-3-29)). - The TLS handshake negotiation fails silently on the Apache Tomcat side. ## Solutions Verify the certificate matching requirements and adjust accordingly Verify that the certificate CN/SAN exactly matches the URL used to connect to the OneSpan Authentication Server instance and adjust the URL accordingly. openssl x509 -in soap_certificate_file -noout -subject -ext subjectAltName Where soap_certificate_file is the SOAP certificate used by the OneSpan Authentication Server instance. > Verifying the certificate matching requirements > > Verify the subject alternative name using OpenSSL > > ```shell > > openssl x509 -in ikey_soap_cert.pem -noout -subject -ext subjectAltName > subject=CN=192.0.2.1 > X509v3 Subject Alternative Name: >    IP Address:192.0.2.1 > ``` > > Use the respective SAN as the host for the server instance: > > ```shell > > admintool type selfmgmt autoadd primary https://192.0.2.1:8888 > ``` > Wildcard certificates > > You can also use wildcard certificates to cover an unlimited number of sub-domains in a main domain. For example, *.example.com covers host1.example.com, host2.example.com, etc. Verify the SOAP-level logs SOAP/TLS communication errors between OneSpan User Websites and OneSpan Authentication Server are not written to the standard Tomcat logs (catalina.out) of the respective OneSpan User Websites application. To identify and investigate such errors, verify the OneSpan Authentication Server trace log, usually at the following location by default: - %PROGRAMFILES%\VASCO\IDENTIKEY Authentication Server\log\ias.trace (Windows) - /var/log/vasco/identikey/ias.trace (Linux) Note that you need to [enable tracing](/sec/docs/oas-ag-basic-strategies-and-tips-3-29) via the **OneSpan Authentication Server Configuration Utility** first.