Log Files & Reporting a Bug

When something misbehaves, the log files are what turn "it broke" into a fixable report. Grab them close to when the problem happened.

Where the logs live

The quickest route on any OS: in the dashboard, open Settings, and under Diagnostics & support on the General tab click Open data folder. On Windows the logs are in its logs subfolder; on macOS they live in the separate folder listed below.

The locations themselves:

• Windows: %ProgramData%\Nexus\logs
• macOS: ~/Library/Logs/Nexus
• Linux: the service logs to the system journal; read it with journalctl -u nexus (add -f to follow live).

The main file is nexus-service.log. On each service start the previous run is archived as nexus-service-<timestamp>.log (the five newest are kept), so the folder holds the current run plus recent history. On Windows the same folder also collects the logs of the other Nexus components, named nexus-*.log. The first line of every service log records the Nexus version it came from.

The support bundle

The dashboard can package everything relevant into a single ZIP: click Export support bundle in Settings under Diagnostics & support, or at the top of the Diagnostics page (both produce the same file). It holds every log, the OpenRGB daemon's logs, the diagnostics data, and a copy of your settings with credentials removed. Attaching that bundle to a report beats hand-picking files.

How to report

Join our Discord; it is the fastest place to get help and where bug reports are tracked. Include:

1. Your Nexus version. It is stamped on the first line of nexus-service.log, so the log file itself carries it.
2. Your OS (Windows, macOS, or Linux, plus the version).
3. What happened and when: what you did, what you expected, what you saw instead, and roughly when it occurred so it can be matched against log timestamps.
4. The log files or the support bundle, captured while the problem was still fresh.