Skip to main content

​
How do I fix a “Webhook connection error”?

This error usually happens when there is a malformed url in your webhook app configuration. The destination url needs to include the protocol.

​
Common fixes

  • Change the URL from http://your-webhook-url.com to https://your-webhook-url.com, using the HTTPS protocol.

​
Common fixes

  • Double check that the message data payload is properly formatted with valid JSON. Common formatting issues are uses of single quotes and the inclusion of numbers. If in doubt, use a JSON validator.

​
How do I fix a “Socket error: timed out message”?

Socket error: timed out messages are the result of a failure to establish a connection. These are usually associated to devices being offline or not having the correct connection setup, which prevents connections to a SIM from being established.

​
Common fixes

  • Verify that the device is online and that the modem is **able to connect**. Some devices may restrict data connections to limit battery usage which can prevent device communication and also cause issues with eUICC operations.
  • Verify that the webhook connection setup is correct, especially the host and port.
  • Verify in your dashboard that the SIM is opening sessions and passing data correctly. If you see zero-byte sessions, you may need to troubleshoot the device’s connection setup.

​
How do I fix an “Error decoding JSON message”?

This generally comes from a misconfigured Route. If you see an error like “Error decoding JSON for variable decdata.foobar”, it means you have used an incorrect Data Router message variable.

​
Common fixes

  • Verify that the message data payload is properly formatted with valid JSON and Route variables. See available variables for more information.
Limited access: Routes access is limited to certain legacy contracted organizations. If you are having issues with routes, please reach out to support.