This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(259.20000000000005, 74%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDJ%3C/text%3E%3C/svg%3E)
Hi All
I am experiencing some issues with all our WiFi boards connecting to the IoT Hub all of a sudden. I anyone else have any issues or know anything about it?
It seems it's related to the SSL certification migration, which I believe is it takes place next year, but it seems there has been some change in the back-end servers.
We recently updated all our devices to:
DigiCertGlobalRootG2.cer This is in addition to BaltimoreCyberTrustRoot.cer.
We also tested our device on Hub g2cert.azure-devices.net, where we were able to connect and send a message with our devices.
But it seems we can no longer even connect to the test hub.
Has anything changed?
Thank You
![](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 @Dharmesh Joshi
We are checking on this issue, please stay tuned!
![](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(316.8, 56.00000000000001%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELD%3C/text%3E%3C/svg%3E)
Hi SatishBoddu-MSFT we are experiencing a estate wide issue similar to the issue logged above, and we have made no changes on our side, is there something that happened in the backend that would effect our connectivity.
thanks, I have manged to solve it by updating my chipset firmware, but it seems like something changed it the back servers causing this issue.
Hi, Dharmesh we have experienced the same issue with our devices losing all connectivity to the Azure IOT Hub due to something that changed on the Azure side, I see you updated your chipset firmware, why would that impact the ability to connect?
Dear Louisdu
I am not sure, but I suspect that as the TLS/SSL root cert is changing from Balitormoe to G2, the cipher suites have already been updated why still using the Baltimore root certificate?
My devices were all working well with the G2 root cert added. Then all of sudden, it stopped. I updated the chipset firm, and its working again.
I am using Microchip WINC3400 chipset, now on version 1.4.3
https://ww1.microchip.com/downloads/aemDocuments/documents/WSG/ProductDocuments/ReleaseNotes/WINC3400_1.4.3_release_note.pdf
Maybe the release note, could give a clue on what has changed?
What devices are you using?
Hi Dharmesh
We have an embedded system in a Safe, which is legacy and I am not actually sure what the chipset details are, everything just stopped working due to SQL sync stopping with the IOT Hub.
Thanks for giving me your answer and feedback!
Regards
Louis
So does your IoT Hub directly connect to an SQL?