Tomcat HTTPS启动后访问8443端口抛NPE、Chrome报ERR_SSL_PROTOCOL_ERROR
Tomcat HTTPS访问Chrome报ERR_SSL_PROTOCOL_ERROR故障排查
故障基本表现
- Tomcat服务启动无异常,访问
https://localhost:8443时,Chrome浏览器弹出“此网站无法提供安全连接,localhost发送了无效响应”提示,错误码为ERR_SSL_PROTOCOL_ERROR - 同地址在Safari浏览器中可正常访问,故障仅出现在Chrome端
- 服务端在SSL握手阶段反复抛出NullPointerException堆栈,核心日志如下:
SEVERE [https-jsse-nio-8443-exec-7] org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun java.lang.NullPointerException at org.bouncycastle.crypto.signers.PSSSigner.generateSignature(Unknown Source) at org.bouncycastle.jcajce.provider.asymmetric.rsa.PSSSignatureSpi.engineSign(Unknown Source) at java.security.Signature$Delegate.engineSign(Signature.java:1382) at java.security.Signature.sign(Signature.java:698) at sun.security.ssl.CertificateVerify$T13CertificateVerifyMessage.<init>(CertificateVerify.java:931) at sun.security.ssl.CertificateVerify$T13CertificateVerifyProducer.onProduceCertificateVerify(CertificateVerify.java:1105) at sun.security.ssl.CertificateVerify$T13CertificateVerifyProducer.produce(CertificateVerify.java:1098) at sun.security.ssl.SSLHandshake.produce(SSLHandshake.java:420) at sun.security.ssl.ClientHello$T13ClientHelloConsumer.goServerHello(ClientHello.java:1096) at sun.security.ssl.ClientHello$T13ClientHelloConsumer.consume(ClientHello.java:1032) at sun.security.ssl.ClientHello$ClientHelloConsumer.onClientHello(ClientHello.java:716) at sun.security.ssl.ClientHello$ClientHelloConsumer.consume(ClientHello.java:683) at sun.security.ssl.SSLHandshake.consume(SSLHandshake.java:376) at sun.security.ssl.HandshakeContext.dispatch(HandshakeContext.java:444) at sun.security.ssl.SSLEngineImpl$DelegatedTask$DelegatedAction.run(SSLEngineImpl.java:983) at sun.security.ssl.SSLEngineImpl$DelegatedTask$DelegatedAction.run(SSLEngineImpl.java:970) at java.security.AccessController.doPrivileged(Native Method) at sun.security.ssl.SSLEngineImpl$DelegatedTask.run(SSLEngineImpl.java:917) at org.apache.tomcat.util.net.SecureNioChannel.tasks(SecureNioChannel.java:423) at org.apache.tomcat.util.net.SecureNioChannel.handshakeUnwrap(SecureNioChannel.java:483) at org.apache.tomcat.util.net.SecureNioChannel.handshake(SecureNioChannel.java:238) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1475) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:748)
故障根因
从报错栈可定位,异常发生在TLS 1.3协议的CertificateVerify消息生成环节,由BouncyCastle加密库处理RSASSA-PSS签名逻辑时触发空指针。
Chrome与Safari的TLS协商逻辑存在差异:Chrome默认优先协商TLS 1.3协议,在算法支持列表中优先要求使用RSASSA-PSS签名;Safari默认优先采用TLS 1.2协议,不会触发该签名算法的调用路径,因此可正常建立连接。
空指针的直接触发原因是所使用的BouncyCastle版本存在缺陷:当密钥库中的证书未正确初始化PSS签名所需的盐值、掩码生成函数等参数时,PSSSigner类会因读取空参数抛出空指针,直接中断SSL握手流程,最终Chrome侧收到无效的握手响应,报协议错误。
可行解决路径
- 升级BouncyCastle依赖:将Tomcat类路径下的
bcprov.jar升级到1.68及以上修复版本,该版本已补齐PSS签名器的空参数校验逻辑,从根源上避免空指针触发。 - 临时规避TLS 1.3握手路径:修改
server.xml中8443端口的HTTPS连接器配置,显式限定SSL协议版本为TLS 1.2,关闭TLS 1.3支持,配置示例:<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol" maxThreads="150" SSLEnabled="true"> <SSLHostConfig protocols="TLSv1.2"> <Certificate certificateKeystoreFile="conf/localhost-rsa.jks" type="RSA" /> </SSLHostConfig> </Connector> - 修正证书参数:重新生成RSASSA-PSS算法证书时,显式指定PSS参数中的盐值长度、掩码生成函数,确保密钥库中存储的证书参数完整,无缺失项。
内容的提问来源于stack exchange,提问作者Sachin
相关产品推荐
相关产品推荐

