This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
I have 4 devices sending data to an IoT Hub for a while now and yesterday it stopped sending as it was receiving a Connack Error 5 (0x05 Connection Refused, not authorized).
I then tried a different device with the same credentials just in case the device was having an issue but the same was happening with that device also.
I then created new device and device certificates in case they were expired but again I am getting the same error 5.
I even tried connecting with MQTTfx (an MQTT client application) but with same results. Also tried with MQTT Explorer...
This all started happening on 1/8/2022.
Any ideas? Did anything change? I am using the MQTT Paho library and so is MQTTfx.
These devices were working for months with no issues... something must have changed and it's not the root certificate as the old baltimore one is still active and the connections is established.
my username looks like this: thermos.azure-devices.net/testing/?api-version=2018-06-30
Also tried with /?api-version=2021-04-12
So the Hub name is thermos and the device (client id) is testing
Broker address is thermos.azure-devices.net port 8883
Using TLS1.2 and x509 certificates connecting to East US region.
This config is based on this
Edit: This is not only happening on my IoT Hub but on a clients account also.
This is urgent.
thanks
An Azure service that enables bidirectional communication between internet of things (IoT) devices and applications.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 38%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQ%3C/text%3E%3C/svg%3E)
Hello @Haris Papageorge Is there any Microsoft support ticket submitted on this issue?
Hello @QuantumCache ,
No there isn't one.
My subscription doesn't allow for a ticket at this point but I might have to upgrade.
Hello, @Haris Papageorge Send us an email and I will help with an immediate support ticket, no worries, we will help on this issue as soon as possible.
Answer accepted by question author
Hello, @Haris Papageorge , hope you are doing well!
We have mitigated the issue which was caused during the backend update process. I hope your issue is now resolved. Please let us know if you need further help in this matter.
Please let us know if we are good to close this case.
Happy to help you!
Hello @QuantumCache ,
As of 18:00 (EEST) of September 9, my devices started getting the CONNACK error again. They cannot connect to the IoT Hub as connection is denied by Azure.
So the same issue that prompted this forum question is again present.
I suspect it has to do with the backend update process again?
And again I get this changed property in my hub like I did the last time I was having issues: "features": "GWV2",
Is there something I can do to mitigate this? Should I contact the support engineer that helped me through this?
Thanks.
Hello @Haris Papageorge Yeah please contact the support team and do let us know if you need further help in this matter.