Server Up/Down Discord Alerts for Arma Reforger

If your server crashes at 2am, you want to know before your players do. LoafHosts can post a message straight to a Discord channel the moment your Arma Reforger server goes up, down, or restarts — no third-party uptime monitor, no extra software, no editing config files. These alerts live on the Server Stats page, which is available for Arma Reforger servers, and the up/down/restart check reads your server’s live power state and session directly. This guide covers exactly what the alerts do, how to point one at your Discord channel, what the messages look like, and how the panel decides a server is genuinely down rather than just restarting.

What These Alerts Do

A server-state alert is a Discord message that fires on one of three things happening to your server: it comes up (a fresh running session starts), it restarts (the running session is replaced by a new one), or it goes down (your server reports a stopped or offline power state and no live session is running). Each event posts its own embed to the Discord channel you choose, titled with your server’s name. The check runs in the background on a roughly one-minute cycle, so an alert lands within about a minute of the change — and it keeps working even when nobody has the panel open in a browser.

The same Server Stats page also offers other Discord events — kills, player joins, and performance thresholds — which read your Arma Reforger game log. This guide focuses on the up/down/restart event; you can subscribe a webhook to as many of these events as you like.

Note: The check runs about once a minute in the background, so alerts arrive within roughly a minute of the change.

Note: Alerts keep firing even with the panel closed — you do not need a browser tab open.

Before You Start: Get a Discord Webhook URL

Alerts are delivered through a standard Discord webhook, so you need one webhook URL for the channel you want messages to appear in. In Discord, open the channel’s settings (Edit Channel), go to Integrations → Webhooks, create a new webhook, pick the channel it should post to, and use Copy Webhook URL. That URL is the only thing you paste into LoafHosts. A webhook URL looks like https://discord.com/api/webhooks/… — the panel only accepts genuine Discord webhook URLs and rejects anything else, so make sure you copied the full link.

Tip: Make a dedicated channel like #server-status so up/down alerts do not get buried in chat.

Tip: Treat the webhook URL like a password — anyone with it can post to that channel.

Add an Up/Down Alert

The Discord webhook controls live on your server’s Server Stats page, under the Settings tab. The Server Stats item appears in the sidebar for Arma Reforger servers. Open your server in the LoafHosts panel, choose Server Stats from the server sidebar, then select the Settings tab. Scroll to the Discord webhooks section and follow these steps:

1. Click Add webhook.
2. Paste your Discord Webhook URL into the Webhook URL field.
3. Optionally add a Label (for example, “Status channel”) so you can tell your webhooks apart later.
4. Under Post which events, tick Server up / down / restart. If you only want status alerts, untick the other event boxes.
5. Turn on the Enable toggle so the webhook starts posting.
6. Click Create webhook.

A new webhook needs a URL and at least one event selected, or the panel will ask you to add them before it saves. Once it is created, you will see it listed with an On badge while it is enabled.

Note: When you first add or enable a webhook, the panel treats your currently-running server as “already announced,” so you will not get an instant “up” message — the first alert arrives on the next real change.

What the Alerts Look Like

Each state change posts a single, clearly coloured embed showing your server’s name, sent by LoafHosts Server Stats:

• 🟢 Server up — a fresh running session has started (the server came online).
• 🔄 Server restarted — the running session was replaced by a new one (a reboot or crash-and-recover).
• 🔴 Server down — the server reported a stopped or offline power state with no live session.

The “up” and “restarted” embeds are blue; “down” is a dark red so it stands out in a busy channel. Each message is stamped with the time it was sent.

How Up, Down, and Restart Are Detected

The point of an alert is to be trustworthy, so the panel is deliberately conservative about calling a server “down.” Here is what it does and does not treat as a real event:

• Up fires the first time the panel sees a running server with a fresh session after it was previously down or newly added.
• Restart fires when a server that was already up starts a brand-new session — for example after a scheduled reboot or an unexpected crash that recovered.
• Down fires only when your server explicitly reports a stopped, stopping, or offline power state and there is no live session. It is sent once, not repeated every minute.
• Installing, starting, and restoring are skipped. While a server is mid-install, booting, or being restored from a backup, the panel sends nothing — those are normal in-between states, not a “down.”
• A momentary status blip is ignored. If the panel cannot read the server’s state for a tick (a brief connection hiccup), it stays quiet rather than firing a false “down” that would then flap back to a false “up.”

Each transition fires exactly once. While nothing changes, no messages are sent — so a healthy server sitting online does not spam your channel.

Tip: If you run a nightly scheduled restart, expect one “Server restarted” message around that time — that is the alert working, not a problem.

Posting to a Thread, Forum Post, or Multiple Channels

You can target a specific Discord thread or forum post instead of the main channel. When adding or editing a webhook, fill in the optional Discord Thread ID — the 17-to-20-digit numeric ID of the thread or forum post — and alerts will post inside it. Leave it blank to post in the channel itself.

You can also add up to 5 webhooks per server, each posting its own set of events to its own Discord channel. For example, one webhook can send up/down/restart to a #server-status channel for your admins, while a separate webhook sends something else elsewhere. Every webhook has its own enable toggle and its own settings.

Tip: To get a thread’s ID in Discord, enable Developer Mode, then right-click the thread and choose Copy ID.

Editing, Testing, and Removing a Webhook

Each saved webhook on the Settings tab has its own controls:

• Send test posts a test message to the webhook’s channel (or thread) so you can confirm Discord is receiving it. After sending, the panel confirms with “Test message sent — check your Discord channel.”
• Save applies any changes you make — a new URL, label, thread, or event selection.
• The Enable toggle turns the webhook on or off without deleting it. A disabled webhook keeps its settings but stops posting.
• Delete removes the webhook for good; the panel warns you that it will stop posting immediately.

If you ever change which Discord channel you want alerts in, just edit the webhook’s URL (or thread ID) and save — there is no need to delete and recreate it.

Note: Editing webhooks requires permission to manage the server’s startup/configuration. The server owner has this by default; a sub-user needs that permission granted to them.

In Short

LoafHosts turns “is my Arma Reforger server up?” into a Discord message you receive automatically. Grab a webhook URL from your Discord channel, open your server’s Server Stats page, add a webhook on the Settings tab, tick Server up / down / restart, enable it, and click Create webhook. Once it is saved, use Send test on the webhook’s row to confirm Discord is receiving messages. From then on you get a 🟢, 🔄, or 🔴 message whenever your server’s state actually changes — without watching the panel yourself.