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.
When submitting a bug report, the system appends log files for our team to isolate and fix your issues quicker.The following data is gathered when you submit a bug report:
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.
To view logs as files, they have to be exported out of Docker.The following should be executed from the node repository folder, where your .env and docker-compose.yml are located.
Prints the last 100 lines of logs for all services, then continues streaming new ones.
Change --tail option to another value if required.If you only want to see the logs of a particular process, replace docker-compose-name.yml with that process’s name.
Logs can be exported to any directory, yet if you don’t define a custom path, the log file gets generated in the default location.
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.
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.
Default installation paths are relative to your home directory.
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.
Fortytwo App
Fortytwo Container
Fortytwo CLI
macOS
Windows
Linux (Ubuntu/Debian)
Short path:
Zsh
Copy
~/Fortytwo
Full path:
Zsh
Copy
/users/{username}/Fortytwo
Paste to address bar:
Copy
%USERPROFILE%\Fortytwo
Full path example:
Copy
C:\Users\{username}\Fortytwo
Path for PowerShell:
Copy
cd "$HOME\Fortytwo"
Short path:
Bash
Copy
~/Fortytwo
Full path:
Bash
Copy
/home/{username}/Fortytwo
macOS
Windows
Linux (Ubuntu/Debian)
MACOS IS CURRENTLY NOT SUPPORTED
Paste to address bar:
Copy
%USERPROFILE%\FortytwoContainer
Full path example:
Copy
C:\Users\{username}\FortytwoContainer
Path for PowerShell:
Copy
cd "$HOME\FortytwoContainer"
Short path:
Bash
Copy
~/FortytwoContainer
Full path:
Bash
Copy
/home/{username}/FortytwoContainer
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.
Fortytwo App
Fortytwo Container
Fortytwo CLI