> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fortytwo.network/llms.txt
> Use this file to discover all available pages before exploring further.
# Inference Node Support
P2P
Fortytwo P2P App
Fortytwo P2P CLI
Fortytwo P2P Container
Report Issues
Find Logs
Export Logs
Default Installation Location
Navigate to the main support page.
## Reporting Your Issues
Join our `#tech-questions` channel in the official [ Fortytwo Discord server ](https://discord.gg/fortytwo) to join the discussion on all issue-related topics.
1. **Fortytwo P2P App** users can submit a bug report directly through the app.
2. **Fortytwo P2P CLI** and **Fortytwo P2P Container** users can submit a bug report through the `#bug-report` channel on the [ Fortytwo Discord server ](https://discord.gg/fortytwo).
### Reporting via Fortytwo P2P App
Fortytwo P2P 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 P2P 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 P2P App. Only the last `2000 lines` of each log are submitted.**
## Finding Log Files
Paths where your logs are stored:
```bash Zsh theme={null}
~/Fortytwo/storage/debug
```
Paste into the address bar:
```bash theme={null}
%USERPROFILE%\Fortytwo\storage\debug
```
Path for PowerShell:
```bash theme={null}
cd "$HOME\Fortytwo\storage\debug"
```
```bash Bash theme={null}
~/Fortytwo/storage/debug
```
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.
### View Logs
```bash theme={null}
docker compose logs -f -t --tail 100
```
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.
```bash theme={null}
docker compose -f docker-compose-name.yml logs -f -t --tail 100
```
### Export Logs
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](/docs/quick-start)' page.**
`MACOS IS CURRENTLY NOT SUPPORTED`
```bash PowerShell theme={null}
docker compose logs -t > "ft_node_logs_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"
```
If you only want to export the logs of a particular process, replace `docker-compose-name.yml` with that process's name.
```bash PowerShell theme={null}
docker compose -f docker-compose-name.yml logs -t > "ft_node_logs_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"
```
```bash Bash theme={null}
docker compose logs -t > "ft_node_logs_$(date +'%Y%m%d_%H%M%S').txt"
```
If you only want to export the logs of a particular process, replace `docker-compose-name.yml` with that process's name.
```bash Bash theme={null}
docker compose -f docker-compose-name.yml logs -t > "ft_node_logs_$(date +'%Y%m%d_%H%M%S').txt"
```
**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](/docs/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`.
```bash Zsh theme={null}
~/FortytwoCLI/fortytwo-p2p-inference-scripts-main/FortytwoNode/debug
```
Paste into the address bar:
```bash theme={null}
%USERPROFILE%\FortytwoCLI\fortytwo-p2p-inference-scripts-main\FortytwoNode\debug
```
Path for PowerShell:
```bash theme={null}
cd "$HOME\FortytwoCLI\fortytwo-p2p-inference-scripts-main\FortytwoNode\debug"
```
```bash Bash theme={null}
~/FortytwoCLI/fortytwo-p2p-inference-scripts-main/FortytwoNode/debug
```
## Default Installation Location
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](/docs/quick-start)' page.**
Short path:
```bash Zsh theme={null}
~/Fortytwo
```
Full path:
```bash Zsh theme={null}
/Users/{username}/Fortytwo
```
Paste into the address bar:
```bash theme={null}
%USERPROFILE%\Fortytwo
```
Full path example:
```bash theme={null}
C:\Users\{username}\Fortytwo
```
Path for PowerShell:
```bash theme={null}
cd "$HOME\Fortytwo"
```
Short path:
```bash Bash theme={null}
~/Fortytwo
```
Full path:
```bash Bash theme={null}
/home/{username}/Fortytwo
```
`MACOS IS CURRENTLY NOT SUPPORTED`
Paste into the address bar:
```bash theme={null}
%USERPROFILE%\FortytwoContainer
```
Full path example:
```bash theme={null}
C:\Users\{username}\FortytwoContainer
```
Path for PowerShell:
```bash theme={null}
cd "$HOME\FortytwoContainer"
```
Short path:
```bash Bash theme={null}
~/FortytwoContainer
```
Full path:
```bash Bash theme={null}
/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](/docs/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`.
Short path:
```bash Zsh theme={null}
~/FortytwoCLI
```
Full path:
```bash Zsh theme={null}
/Users/{username}/FortytwoCLI
```
Paste into the address bar:
```bash theme={null}
%USERPROFILE%\FortytwoCLI
```
Full path example:
```bash theme={null}
C:\Users\{username}\FortytwoCLI
```
Path for PowerShell:
```bash theme={null}
cd "$HOME\FortytwoCLI"
```
Short path:
```bash Bash theme={null}
~/FortytwoCLI
```
Full path:
```bash Bash theme={null}
/home/{username}/FortytwoCLI
```
# FAQ
See the '[P2P Inference Nodes section in FAQ](/docs/faq#p2p-inference-nodes)'.