Logs and troubleshooting

This table provides definitions of the status and error codes that the IoT Edge Connect logs in the connection monitoring topics.

Each status and error code consist of a letter and a number. The letter tells you the category where the status code or error belongs. These are the available categories:

  • C - Configuration

  • J - JSON Web Token (JWT)

  • M - Mutual Authentication

  • A - Authentication

  • F - Broker servers

  • D - Connection drop

Connects

This table presents the definition of the status code that the system logs in the following connection monitoring topic $SYS/monitor/con/connects.

Status codeStatus descriptionAdditional data
00Successful connection.-

Errors

This table presents the definition of the error codes that the system may log in the following connection monitoring topic $SYS/monitor/con/errors.

Error codeError descriptionAdditional dataTroubleshooting
C1You haven't configured an authentication method for this namespace.-Check your IoT Edge Connect configuration.
C3You haven't configured your namespace for the specified hostname.-Check your IoT Edge Connect configuration.
J1No JWT present during the connection.-Check the following connection options of your MQTT client:
  • A password needs to have a JWT as its value.
  • A username needs to have a value.
  • J2No JWT in the MQTT CONNECT or Websocket’s header.Specific parse errorCheck the validity of the token.
    J3A JWT signature is invalid.-Check if a JWT was sent with a correct private key.
    J4An unsupported signing algorithm for a JWT.Algorithm receivedCheck if RS256 signing algorithm was used to encrypt the JWT.
    J5A JWT has expired.Expiration timeCheck the JWT expiration date. It can't be set to the past date.
    J6The nbf claim in the JWT doesn't allow this token to be processed.Start timeVerify your JWT's nbf claim.
    J7You haven't passed any client ID claim in a JWT.-Check if the token has an ID claim.
    Check if the client ID field isn't empty.
    J8You haven't passed any authorization group claim in a JWT.-Check if the token has an authorization group claim.
    Check if the authorization group claim isn't empty.
    M1Client certificate didn't pass validation.Validation error-
    M2You haven't passed any client ID claim in the client certificate.-Check if the certificate has an ID claim.
    Check if the Client ID claim isn't empty.
    M3You haven't passed any authorization group claim in the client certificate.-Check if correct authorization group was passed during the connection.
    Check if the correct authorization group was passed in the certificate.
    M4Your mutual authentication behavior failed to include authorization groups-Contact technical support.
    M5Your mutual authentication behavior failed to include client ID.-Contact technical support.
    A1Client ID in MQTT Connect settings is different from the one in the JWT set as a password for the MQTT connection.Client ID received in MQTT ConnectCheck if the correct client ID was passed during the connection.
    Check if the correct client ID was passed.
    Check the client ID in the JWT.
    A3The system can't validate the client ID you sent.Specific parse errorConsult the parse error for more details.
    A4The system can't use the authorization groups you sent.Specific parse errorConsult the parse error for more details.

    Drops

    This table presents the definition of the status codes that the system may log in the following connection monitoring topic $SYS/monitor/con/drops.

    Status codeStatus descriptionAdditional data
    D2Publish to an unauthorized topic.Name of the topic
    D4Your connection is dropped due to the exceeded system limit. For example, the maximum number of connections for the namespace is exceeded.-
    D5Client time-out. The client hasn't sent a ping request within the set keep alive period.-