Soracom Beam

Soracom Beam Errors

Soracom Beam stores error logs for the last 14 days that can be viewed from the User Console or API. These errors can be used for debugging when troubleshooting issues with your deployment.

The following error messages can be found in the error logs:

Error Message Explanation Troubleshooting
Connection to the destination has been timed out The device is unable to connect to the destination server. Make sure that the destination server set in the Beam configuration is correct and is running. For details, refer to Beam Configuration.
TCP connection error: ECONNRESET Beam has disconnected the TCP connection. This can occur for the following reasons:
  • Beam received an RST packet (reset packet) from the device or destination server, causing the TCP connection to be disconnected. RST packets are sent when the device, destination server, or routers in the communication path terminate the TCP session for some reason.
  • The device disconnected the TCP connection without waiting for an ACK from Beam after sending data.
  • The device did not terminate the TCP connection correctly after sending data.
 Even if this error log is output, data communication may not be significantly affected if the device reestablishes the TCP connection. If data communication is affected, check the settings of the device, destination server, router, etc.
Beam configuration for {url} is not found The device sent data to a Beam entry point, but no Beam configuration corresponding to that entry point has been created in the group settings. The group assigned to the IoT SIM does not have the corresponding entry point added. The {url} in the error log is the identifier for which entry point received the data and is not configured:
Failed to resolve {url} Failed to resolve the domain name of the destination server. Ensure that the URL of the destination server set as the entry point is correct.
Service unavailable on the destination When Beam attempted to transfer data, the connection to the destination server was unexpectedly disconnected. This can occur for the following reasons:
  • The destination server is not running.
  • The destination server did not disconnect correctly.
  • The connection was lost due to network issues between Beam and the destination server.
  • The connection timed out.
 Ensure that the transfer destination server is working properly and that there are no problems with the network between Beam and the destination server.
Subscriber configuration is not found There is a problem with the group settings of this subscriber. There are various possible causes for this error:
  • No entry point was found that corresponds to the protocol being used by the device. In the group settings, ensure that a Beam entry point that corresponds to the protocol used by the device is configured. For details, refer to Beam Configuration.
  • Soracom Binary Parser is configured incorrectly. For details, refer to Binary Parser.
  • Your Soracom LTE-M button is not assigned to a group with a UDP entry point configured. For details, refer to the Soracom LTE-M Button Setup Guide.