#tech-support channel in the official Fortytwo Discord server to join the discussion on all issue-related topics.
Reporting Your Issues
- Fortytwo App users can submit a bug report directly through the app.
- Fortytwo CLI users can submit a bug report through the
#bug-reportchannel on the Fortytwo Discord server.
#bug-report channel or join the discussion in the #tech-support channel on the official Fortytwo Discord server.
Reporting via Fortytwo App
Fortytwo app is the optimal way to submit a bug report. It is easier to use and will provide us with all the necessary information to solve your issue quickly.Only report your issues via the Fortytwo App if you actually operate your node with it. Otherwise we will not get any relevant information on how your node was operated and what was causing an issue.
- App log — helps us determine if the issue stems from the app functioning incorrectly.
- Capsule log — the capsule launches models on your node. This log helps us see if the issue is related to launching models, your system configuration or a particular model.
- Protocol log - this is the log of your interactions with the network. This log helps us understand if your issue is rooted in your node’s interaction with the whole of the Fortytwo network.
We receive only the latest and most critical data logged by the Fortytwo app. Only the last
2000 lines of each log are submitted.Finding Log Files for Manual Report
Paths where your logs are stored:- >_ Fortytwo CLI
- ::|| Fortytwo App
The path where your node is installed might differ from the default path if you altered it at the node installation step as defined on the ‘Quick Start’ page.
On October 23, 2025, we’ve changed the name of the default folder from
Fortytwo to FortytwoCLI. If you’ve installed your Fortytwo CLI before this date, your default path will differ. To access the folder, look for Fortytwo instead of FortytwoCLI.- macOS
- Windows
- Linux (Ubuntu/Debian)
Zsh