#
Troubleshooting
Use this guide to quickly locate user data and logs, interpret CLI exit codes, and gather the right diagnostics for troubleshooting Kameleo. Following these steps accelerates root-cause analysis and enables efficient support escalation.
#
Locate user data files
Kameleo stores user-generated data (profiles, kernels, logs, settings) in a workspace directory.
Default location: C:\Users\YOUR_USERNAME\AppData\Roaming\Kameleo
Deleting this folder resets Kameleo (factory default) but permanently removes all profiles & settings.
Default location: ~/Library/Application Support/Kameleo
Deleting this folder resets Kameleo (factory default) but permanently removes all profiles & settings.
Default location: /data (the mounted named volume)
Removing the named volume has the same effect as deleting the data folder — all profiles & settings are lost.
Default location: C:\data (the mounted named volume)
Removing the named volume has the same effect as deleting the data folder — all profiles & settings are lost.
#
Review log files
Daily log files live under the Logs subfolder. File pattern: COMPONENT-YYYYMMDD.txt. Increase verbosity by setting Verbose to 2 (see Configuration in Installation guide) only while debugging; revert to reduce noise.
Log files location: C:\Users\YOUR_USERNAME\AppData\Roaming\Kameleo\Logs
Log files location: ~/Library/Application Support/Kameleo/Logs
Log files location: /data/Logs
If the named volume is mounted, logs are accessible on the host at the volume's mount path. To read the latest log file directly from a running container:
docker exec kameleo-app sh -c 'cat /data/Logs/$(ls /data/Logs | tail -1)'Log files location: C:\data\Logs
If the named volume is mounted, logs are accessible on the host at the volume's mount path. To read the latest log file directly from a running container:
docker exec kameleo-app powershell -NoProfile -Command "Get-Content (Get-ChildItem C:\data\Logs | Sort-Object Name | Select-Object -Last 1).FullName"
#
CLI exit codes
Refer to the consolidated list in CLI exit codes for meanings and remediation guidance. Use these codes in scripts to branch on transient vs. persistent failures.
#
Gathering diagnostic info
- Reproduce the issue with Verbose=2
- Note timestamp & profileId (if relevant)
- Collect the most recent log files
- Export affected profile (if reproducible state matters)
#
Opening a ticket
Use the in-app Report a Bug button in the sidebar whenever you can. It automatically collects vital environment details and relevant log files so we can help you faster and with fewer back-and-forth questions.
- Reproduce the issue (if possible).
- In Kameleo, open the sidebar.
- Click Report a Bug.
- Describe what you expected vs. what happened.
- Attach any helpful files (for example screenshots, scripts, or test data) that make it easier to reproduce the issue.
- Submit the report.
If the app does not start, you cannot log in, or you cannot access the bug report feature, contact support through the Help Center.