This article addresses a known issue where logging is broken upon the installation of our macOS client if the optional "Detailed Logging" option is not checked. This can result in only non-relevant repeating errors appearing in the logs, which may hinder troubleshooting efforts. Follow the steps below to ensure proper logging functionality.
com.twingate.macos.tunnelprovider.txt
2024-06-12 14:29:11.688-0800 [ERROR] [client] -[TunnelProvider startHydraWithCompletion:isRestart:]_block_invoke [Line 221] Hydra connection finished with error (null)
2024-06-12 14:29:11.688-0800 [ERROR] [client] -[TunnelProvider startHydraWithCompletion:isRestart:]_block_invoke_2 [Line 240] Packetflow start with error (null)
2024-06-12 14:29:11.716-0800 [ERROR] [client] -[TunnelProvider shutdownWithError:withCompletion:] [Line 287] Shutting down with error Error Domain=com.twingate.tunnel Code=5 "system_stopped_with_reason:1" UserInfo={NSLocalizedDescription=system_stopped_with_reason:1, reason=1}
com.twingate.macos.txt
2024-06-12 14:16:13.259-0800 [ERROR] [client] -[VPNManager pluginMessage:withUserInfo:withCompletion:] [Line 681] Failed to send Error Domain=com.anchorfree.hydra.manager Code=5 "vpn must be connected" UserInfo={NSLocalizedDescription=vpn must be connected}
2024-06-12 14:16:13.629-0800 [ERROR] [client] -[VPNManager pluginMessage:withUserInfo:withCompletion:] [Line 669] Failed to send Error Domain=com.anchorfree.hydra.manager Code=5 "rate limit reached" UserInfo={NSLocalizedDescription=rate limit reached}
Once you have verified that the logging system is functioning correctly
Disabling detailed logging after the initial troubleshooting should be done cautiously. While it reduces log verbosity, it might omit critical debug information needed for future troubleshooting.