MQTT Routes not forwarding data to server client

I am having some trouble with my MQTT route setup. Routes from Notehub to our servers are currently failing. To fix it, I tried updating the certificate keys and PEM files for both Notehub and our server clients.

Our setup uses the MQTT Route in Notehub, with Azure Event Grid acting as the MQTT broker.

After the certificate update, only one of my devices started syncing properly, while the others are still not showing data on the dashboard.

Has anyone experienced something similar after rotating TLS certificates?
Are there specific steps needed to refresh or re-establish the connection between Notehub and Azure after updating the certs?

Any guidance or troubleshooting tips would be really appreciated.

Hello @Arnold208

Each routing attempt from Notehub should be independent of the others. If certificates were changed then it should take effect immediately.

It’s hard to say what’s going on without getting more information. If you feel comfortable with it you can go under Settings → Members and click “Invite Support” to allow us to look at your project to help diagnose the issue. If you don’t want to do that, can you send us the errors that you’re getting from the failed routes?

From the looks of the screen shot it seems like it’s only intermittently failing, is that right?

Thanks, Scott

This is the log when the route fails.

But when I test the connection it works.

If “Test connection” works that means the certs, credentials, and ports are all set up properly.

I noticed that recently everything routed has been working. Are you still experiencing any issues?

Thanks, Scott