The support archive is a single file gathering the whole context of your Recalbox: version, configuration, logs, detected hardware, controllers, emulator settings… It is the file to provide when asking for help on the Recalbox Discord: it saves half an hour of back-and-forth questions.
For the archive to be genuinely usable:
START → ADVANCED SETTINGS → ACTIVATE DEBUG/VERBOSE LOGS);Open the web manager in a browser (http://recalbox.local). At the bottom right of the page, a round button unfolds the actions menu: pick Support archive. Generation takes a moment, then a download link appears and your browser fetches the archive.

The same menu holds Versions, Reset to factory settings and the EmulationStation / Recalbox restart commands.
Connect over SSH and run:
/recalbox/scripts/recalbox-support.sh
The script prints the path of the resulting file once it is done.
Either way, the archive is named recalbox-support-<date>.tar.gz and dropped in the share/saves folder, reachable through the network share.
The script notably collects:
recalbox.conf and the boot files (recalbox-boot.conf, recalbox-user-config.txt, boot and update logs);share/system/logs, plus /var/log/messages and the Bluetooth log;dmesg, lsmod, lsusb, lspci, processes, memory, free space, mounted disks, network (connman, interfaces), audio (ALSA, PulseAudio), display (output EDIDs, Xorg);evtest and udevadm information for every event, es_input.cfg;share/system/configs), the system list, the list of installed themes, an approximate rom count, and the Kodi and LIRC logs.Your games and saves are not included.
The archive may contain secrets — send it in a private message, never in a public channel. The script does mask the Wi-Fi key, the patron private key and the RetroAchievements / ScreenScraper credentials in
recalbox.conf, but the archive also shipsrecalbox-backup.conf, a full copy of that same file, which is not filtered. The root password is masked nowhere.
Once the archive is sent, disable debug mode to get normal performance back.
For one-off diagnostic commands (a controller that is not detected, a silent USB dongle…), see Collecting system information.