# Certification exception- No subject alternative DNS name matching solace found

**URL:** <https://community.solace.com/t/certification-exception-no-subject-alternative-dns-name-matching-solace-found/1267>\
**Category:** Connectors & Integrations\
**Created:** [May 17, 2022, 6:08am UTC](https://community.solace.com/t/certification-exception-no-subject-alternative-dns-name-matching-solace-found/1267 "2022-05-17T06:08:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dam\_player](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/dam_player/32/678_2.png) [@dam\_player](https://community.solace.com/u/dam_player)\
**Post date:** [May 17, 2022, 6:08am UTC](https://community.solace.com/t/certification-exception-no-subject-alternative-dns-name-matching-solace-found/1267/1 "2022-05-17T06:08:09Z")

</div>

i have A service running on AWS ECS cluster that connects to Solace broker instance, it’s been working for last few years but suddenly from past few days it’s giving error like “ Client-1: Connection attempt to host ‘solace’ ConnectException com.solace systems.jcsmp.JCSMPTransportException: CertificateException - No subject alternative DNS name matching solace found”  
this issue does not arrive when we disable property SSL\_VALIDATE\_CERTIFICATE to false…  
but we want to verify that as we did earlier…  
please suggest any solution…

---

<div class="post-metadata">

**Author:** ![uherbst](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/uherbst/32/291_2.png) [@uherbst](https://community.solace.com/u/uherbst)\
**Post date:** [May 17, 2022, 6:52am UTC](https://community.solace.com/t/certification-exception-no-subject-alternative-dns-name-matching-solace-found/1267/2 "2022-05-17T06:52:37Z")

</div>

Hi @dam_player  
I read your error like this:

> Your application tries to connect to a host “solace”, but in the TLS server certificate on broker side, there is no SAN (subject alternative name) “solace” found.

(replace solace with name or IP of your broker and 55443 with your messaging port)  
Have a look here: [How to test TLS connection and server certificate — Solace Community](https://community.solace.com/discussion/510/how-to-test-tls-connection-and-server-certificate#latest) for details.  
Uli