In Twingate connector logs, you may see an error related to token expiration. This message can appear concerning, especially when detailed logging is disabled, but it is an expected behavior. The connector automatically handles token renewal, so no manual intervention is needed.
The following error may appear in connector logs:
Jan 21 15:04:49 connector_hostname twingate-connector[6479]: pb=0x7f6814023d50 parsing response for transaction type #4 returned error 36
Jan 21 15:04:49 connector_hostname twingate-connector[6479]: Response was: {"error":true,"status":403,"service":"Access Manager","message":"Token is expired."}
Jan 21 15:04:49 connector_hostname twingate-connector[6479]: ../core/pubnub_netcore.c:581: pbpal_report_error_from_environment(pb=0x7f6814002c20): errno=0('Success')pbcc_parse_subscribe_v2_response(pbcc=0x7f6814023d50) - AccessDenied: response from server - response='{"error":true,"status":403,"service":"Access Manager","message":"Token is expired."}
This error occurs because a token used by the connector naturally expires. When this happens, the connector automatically requests a new token, and normal operation continues.
Key Points:
This is expected behavior and does not indicate a failure.
The token will be regenerated automatically.
If detailed logging is disabled, this may be one of the few messages visible, which can make it seem like an issue when it is not.
No action is required. The connector will automatically obtain a new token.