Hey Nishanth Sahaya
The “BAD CREDENTIAL” status on your Teltonika RUT241 indicates that the gateway is failing to authenticate with Azure IoT Hub. Since you’ve already verified the SAS token and tried multiple IoT Hub devices, the issue is likely related to one of these areas:
Common Causes & Fixes
1. SAS Token Expiry
- SAS tokens have a validity period (often 1 hour to 7 days depending on how they were generated).
- If the device was powered off overnight, the token may have expired. Fix: Regenerate a new SAS token from Azure IoT Hub and update it in the Teltonika configuration.
2. Device Identity or Policy
- Ensure the IoT Hub device identity is enabled and not disabled in Azure.
- Check if the IoT Hub access policy (SharedAccessKey) matches the credentials used by the gateway.
3. Time Synchronization
- IoT Hub authentication depends on accurate device time.
- If the gateway’s clock drifted while powered off, the SAS token signature will fail. Fix: Sync the Teltonika device time via NTP or manually set the correct time.
4. Connection String Format
Verify that the connection string or credentials entered in the gateway match Azure’s format exactly:
HostName=<your-hub>.azure-devices.net;DeviceId=<device-id>;SharedAccessSignature=<SAS-token>
5. TLS/SSL Certificates
- Azure IoT Hub requires TLS 1.2 and valid root certificates.
- If the gateway lost certificates or firmware settings during power-off, it may fail to establish a secure connection. Fix: Check firmware version and ensure certificates are present.
How to Troubleshoot Further
In Azure Portal
- Go to IoT Hub → Devices → [Your Device] → Overview and confirm status is enabled.
- Check IoT Hub metrics for failed connection attempts.
On Teltonika
- Review system logs for authentication errors.
- Confirm NTP settings and time zone.
Hope it helps.
Thank you