# Wolfssl/wolfmqtt to connect to hive cloud

**URL:** <https://community.hivemq.com/t/wolfssl-wolfmqtt-to-connect-to-hive-cloud/1407>\
**Category:** HiveMQ Cloud\
**Created:** [September 5, 2022, 7:41pm UTC](https://community.hivemq.com/t/wolfssl-wolfmqtt-to-connect-to-hive-cloud/1407 "2022-09-05T19:41:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Daria\_H](https://avatars.discourse-cdn.com/v4/letter/d/dfb087/32.png) [@Daria\_H](https://community.hivemq.com/u/Daria_H)\
**Post date:** [September 6, 2022, 7:23am UTC](https://community.hivemq.com/t/wolfssl-wolfmqtt-to-connect-to-hive-cloud/1407/2 "2022-09-06T07:23:32Z")

</div>

Hi @george_s ,  
Great that you are interested in MQTT and HiveMQ! Welcome to our community.

You indicated you have enabled SNI, but your log shows different. I can see your client receiving error -323 from the server and then asking to check if your client has TLS SNI extension enabled:

> [@george\_s](#):
>
> I (25239) wolfssl: wolfSSL error occurred, error = -323

> [@george\_s](#):
>
> Reason String: Please check the URL and if your MQTT client supports TLS SNI

[As WoflSSL explained](https://www.wolfssl.com/forums/topic839-solved-err-313-revcd-alert-fatal-error.html#pc2666), “-313” means that the server has sent back a Fatal Alert to the client. If this happens after the ClientHello message is sent, this most likely means that the client is not broadcasting support for a cipher suite or extension that the server requires."

So it seems your client does not really have TLS SNI enabled. Did you double-check the “Client Hello” packet in the Wireshark already, how [it is shown here](https://community.hivemq.com/t/client-is-not-authorized-to-connect/856/37), can you provide your screenshot?

Regards,  
Dasha from HiveMQ support

---

_[View the full topic](https://community.hivemq.com/t/wolfssl-wolfmqtt-to-connect-to-hive-cloud/1407)._