Arma Reforger writes its server logs into the profile folder under a logs subfolder, with a new timestamped session folder created on each restart. The main files are console.log, script.log, error.log, and crash.log, and together they cover everything from boot messages to mod errors to crash traces. This guide shows you where the files live, how to open them from the LPV5 file manager and live console, and what to look at first when something breaks.
Where Reforger Writes Logs
Reforger keeps logs inside the profile folder of your server instance, in a logs subfolder. Each session creates its own dated folder so old runs are kept separate from new ones. On a Loafhosts server you can reach this structure through the LPV5 file manager without an FTP client.
- The path is roughly profile/logs/<timestamped-session-folder>/
- A new session folder is created every time the server restarts
- Old session folders are not deleted automatically; clear them out periodically
- On a self-hosted Windows install the same files live under Documents/My Games/ArmaReforger/profile/logs
The Four Files You Care About
Reforger splits its output across a handful of files so you can find the right detail quickly. Most debugging starts with console.log; the others narrow the diagnosis.
- Read console.log top to bottom for the timeline; jump to error.log or script.log for detail
- If a crash dump exists, crash.log usually tells you which subsystem went down
Opening Logs in the LPV5 File Manager
The LPV5 file manager lets you browse straight to the logs folder, open a file inline, and download a copy for archiving.
- Open hub.loafhosts.com and select your Arma Reforger server
- Open the File Manager
- Navigate to the profile folder
- Open logs, then pick the latest timestamped session folder
- Open console.log to start, or jump straight to script.log or crash.log if you know what you are after
- Download the file if you want to attach it to a bug report
- Sort the logs folder by modified date to find the latest run quickly
- Download a full session folder as one zip when you are reporting a crash
Watching Logs Live in the Console
When you are actively debugging, you do not want to refresh files; you want the lines as they happen. The LPV5 console streams the server's live output, which is the same content that lands in console.log.
- Open the Console tab in the LPV5 panel
- Press Start if the server is not already running
- Watch the output for warning and error lines
- Use the search box to jump back to a specific event without leaving the console
- Keep the console open during a mod change or scenario swap so you catch errors immediately
- If the console shows a crash dump, the matching file appears in the logs folder within seconds
What to Look For When Debugging
A few patterns recur across most Reforger problems. Knowing what to grep for shortens the path from log to fix.
- config.json parse errors print near the top of console.log right after start
- Missing or wrong scenarioId throws a load error that mentions the GUID it tried to resolve
- Mod download failures appear as connection or hash errors during the mod sync phase
- Out-of-memory and similar host issues land in error.log and often precede a crash.log entry
- If you are unsure where to start, search console.log for ERROR or WARN; those tags surface the lines that matter
Using the LPV5 Crash Dump Reader
On Loafhosts, the LPV5 panel ships with a Crash Dump Reader that parses the crash files for you so you do not have to hunt through raw text. This is the fastest way to triage a server that keeps falling over.
- Open hub.loafhosts.com and select your Arma Reforger server
- Open the Crash Dump Reader
- Pick the latest dump
- Read the parsed summary to see which subsystem crashed
- Cross-check with script.log if the dump points at a mod
- Pair the Crash Dump Reader with scheduled backups so you can roll back a bad mod before the next crash