javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name when connecting a Remote Agent to Bamboo Server

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

When connecting a Remote Agent to the Bamboo Server the below exception is observed in the <bamboo-agent-home>/atlassian-bamboo-agent.log:

1 2 3 4 5 INFO | jvm 4 | 2017/03/29 14:00:17 | Exiting due to fatal exception. INFO | jvm 4 | 2017/03/29 14:00:17 | javax.net.ssl.SSLProtocolException: handshake alert: unrecognized_name INFO | jvm 4 | 2017/03/29 14:00:17 | at sun.security.ssl.ClientHandshaker.handshakeAlert(ClientHandshaker.java:1441) INFO | jvm 4 | 2017/03/29 14:00:17 | at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:2016) INFO | jvm 4 | 2017/03/29 14:00:17 | at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1125)

Cause

This typically occurs when trying to connect your remote agent to Bamboo through a misconfigured Apache HTTPD Server when the Apache Server supports SNI.

Resolution

The resolution in this case is to add the correct ServerName / ServerAlias to Apache virtual hosts configuration for Bamboo as this article describes:

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.