Can no longer connect to broker

I have been testing for about the last week and everything has worked perfectly. As of yesterday I am unable to connect to the broker (broker.hivemq.com, port 8883):

MQTT: connect()
MQTT: disconnected from broker broker.hivemq.com, isConnected=false source=SERVER
MQTT: connect failed: returnCode=NOT_AUTHORIZED

When I get a disconnect that is not USER (ie CLIENT or SERVER) it will attempt to reconnect in 10 seconds. If I wait long enough it will finally connect. What happened? I can provide code if necessary but the fact that it was working perfectly on the first connection attempt until yesterday tells me the issue is probably not in my code.

-Mark

Hello @mnuetzmann ,

First off, allow me to welcome to the HiveMQ Community! We are always happy to see new faces here.

To start with, I did want to mention that I am currently tracking some unexpected behavior with the public broker, broker.hivemq.com, during client connections. If possible, please provide any full errors you are receiving, or error logs generated during connection attempts, alongside the connection strings you are using. This will allow us to more directly review your current connection configuration in conjunction with our ongoing review.

With that in mind, I do also highly recommend utilizing our free HiveMQ Cloud offering, Serverless, for testing, especially if a Cloud broker is useful to you! Our serverless offering is free for up to 100 connects, 10gb of monthly traffic, and supports MQTT over TLS/SSL on port 8883. All of the details can be found here.

Best,
Aaron from the HiveMQ Team

Thank you Aaron. I created a serverless Cloud broker and a test user and it appears to be connecting well now.

Hello @mnuetzmann ,

I am glad to hear it! Serverless is a great platform, especially if you’re looking at testing a variety of devices with MQTT, or looking to set up custom clients!

I did also want to follow-up to note that we did identify some errant behavior with the broker.hivemq.com public broker, which has since been rectified and my local testing is showing proper connectivity.

Let us know if you are able to confirm access there as well, or if there is any additional assistance we can offer!

Best,
Aaron from the HiveMQ Team