Unified Endpoint Errors

Unified Endpoint 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
`TCP connection error: ETIMEDOUT`	The TCP connection between the device and Soracom, or between Soracom and the destination server, was not properly closed. This can occur for the following reasons: A TCP layer error caused the connection to be terminated. The TCP connection was automatically closed due to a timeout.	After data transmission is complete, ensure that both the device and the destination server properly close the TCP connection. For example, if your device is implemented to send data, explicitly closing the socket after the request may help prevent a timeout in the TCP connection between the device and the Unified Endpoint.
`Subscriber configuration is not found`	Data was sent to the Unified Endpoint, but there is no valid forwarding destination configured in the group settings for the protocol used. This can occur for the following reasons: No settings are configured in the Soracom Beam Settings, Soracom Funk Settings, Soracom Funnel Settings, Soracom Harvest Data Settings, or in the Group field of the Flux IoT Device Event Source, and data was sent to the Unified Endpoint. Only an MQTT entry point is configured in Soracom Beam Settings, but data is sent to the TCP or UDP entry point of the Unified Endpoint.	Ensure that the entry point you are sending data to matches the type of forwarding destination configured. For example, if only the TCP → TCP/TCPS entry point is configured in Soracom Beam Settings, then data should be sent to the TCP entry point of the Unified Endpoint. Unified Endpoint does not have an MQTT entry point. For details on supported entry points, refer to Service Endpoints.