Where Does Twingate Store Config and Logs?
Twingate keeps machine keys and connector config in system folders, with client logs via Troubleshoot.
Last updated
Twingate state is small and well documented. Clients authenticate to your tenant subdomain, so most settings live in the admin console. Local files hold machine keys, connector setup, and logs.
For support use the client Troubleshoot menu: View Logs opens the right folder, Upload Logs sends the bundle. Connector hosts log to stdout or journald depending on install type. Keep service keys out of chat threads and repos, and rotate any key that was ever pasted publicly.
Where Twingate stores this, by platform
%ProgramData%\Twingate\machinekey.conf
Machine key for pre login features, deployed by MDM. Client logs viewed from More, then Troubleshoot. Headless setups use a service key file you place.
/Library/Application Support/Twingate/machinekey.conf
Same machine key role. Standalone client supports full config, App Store build has limits. View Logs in Troubleshoot opens Finder at logs.
/etc/twingate
machinekey.conf plus connector.conf for connectors. Read connector logs with journalctl for the twingate-connector unit. CLI drives setup and start.
Frequently asked questions
How do I collect Twingate client logs?
Open the tray icon, go More, then Troubleshoot, and use View Logs or Upload Logs. Enable detailed logging first for flaky connections. Send the bundle support links to.
Where is the Twingate connector config?
At /etc/twingate/connector.conf on systemd hosts, with log level and analytics flags. Keep the service key file path outside web roots and restrict its permissions.
Notice an outdated path? Let us know.