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.
Tip: The path is roughly profile/logs/logs_YYYY-MM-DD_HH-MM-SS/ (a logs_ prefix plus the session timestamp)
Tip: A new session folder is created every time the server restarts
Tip: Old session folders are not deleted automatically; clear them out periodically
Note: 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.
| Command | Description |
|---|---|
console.log | The main server console output: boot, mod load, player join and leave, admin actions |
script.log | Script-side messages, warnings, and errors; the first place to check for mod issues |
error.log | Engine-level errors and exceptions; check this when the server misbehaves but does not crash |
crash.log | Enforce-VM script stack trace, written for script-side crashes; native engine crashes may produce only a .dmp minidump with no crash.log |
Tip: Read console.log top to bottom for the timeline; jump to error.log or script.log for detail
Tip: 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
Tip: Sort the logs folder by modified date to find the latest run quickly
Tip: 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
Tip: Keep the console open during a mod change or scenario swap so you catch errors immediately
Tip: 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.
Tip: config.json parse errors print near the top of console.log right after start
Tip: Missing or wrong scenarioId throws a load error that mentions the GUID it tried to resolve
Tip: Mod download failures appear as connection or hash errors during the mod sync phase
Tip: Out-of-memory and similar host issues land in error.log and often precede a crash.log entry
Note: If you are unsure where to start, search console.log for ERROR or WARN; those tags surface the lines that matter
Using the LPV5 Dump Reader
On Loafhosts, the LPV5 panel ships with a Dump Reader that surfaces the .dmp memory-dump files Reforger writes on a crash, parses each into a crash report, and shows the surrounding log context 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 Dump Reader
- Pick the latest dump
- Read the parsed summary to see the crash class (for example a null-pointer dereference, segfault, or script crash), the faulting module, and the surrounding log context; native stack frames are not symbolicated to function names
- Cross-check with script.log if the dump points at a mod
Tip: Pair the Dump Reader with scheduled backups so you can roll back a bad mod before the next crash
Frequently Asked Questions
Where does Arma Reforger save server logs?
Logs live inside the profile folder, in a logs subfolder, with a new timestamped session folder created on each restart. On Loafhosts you reach them through the LPV5 file manager without needing FTP.
What server log files does Reforger create?
The main files are console.log (server console output), script.log (script warnings and errors), error.log (engine-level errors), and crash.log (written when the server crashes). Most debugging starts with console.log.
How do I view Arma Reforger logs live?
Open the Console tab in the LPV5 panel. It streams the same output that lands in console.log in real time, which is ideal for watching boot, mod sync, and admin actions as they happen.
Where is the Arma Reforger crash log?
When the server crashes, Reforger writes a .dmp memory dump, and on script-side crashes a crash.log trace into the timestamped session folder under profile/logs. On Loafhosts the LPV5 Dump Reader surfaces these dumps, parses each into a crash report (crash class, faulting module, crashing-thread registers), and shows the surrounding log context so you do not have to read raw text.
How long are server logs kept?
Reforger does not auto-delete session log folders, so they accumulate until you clear them out. Periodically delete old session folders through the LPV5 file manager to keep storage in check, especially on busy servers.
What should I check first when my Reforger server will not start?
Open console.log from the latest session folder. config.json parse errors, missing scenarioId values, and mod download failures all print near the top of the file with clear ERROR lines that point at the cause.