Two pages in your server menu answer two different "what happened?" questions. Activity is the panel's paper trail: who clicked what, and when. Logs is a browser for the files your server writes — the console output and crash reports that say why something broke. Knowing which one to open saves a lot of time. Both live in your server menu.
| At a glance | |
|---|---|
| You need | Any Falix server |
| Plan | All plans |
| Time | Five minutes each |
Activity — who did what
The Activity page is an audit log of actions taken in the panel: files edited, the server restarted, settings changed, a backup deleted. It's the first place to look when you share a server and something changed that you didn't do. Each entry shows:
- Who — the person's username and avatar, or System for automated actions.
- What — the action, tagged with a category.
- When — in your local time.
- Details — the specifics (which file, which setting), and the IP address the action came from when one is recorded.
Filter to find it fast
Filter the log by category, and the buttons only show categories that actually have entries:
| Files | Server | Settings | Backups |
| Database | Network | Firewall | Version |
| World | Player | Add-ons | Schedules |
| Git | Billing | Users | (All) |
On top of categories you can search the text (matches the action, the person, and the details) and filter by member to see just one person's actions, with type-ahead. There's no calendar filter — the page loads your most recent activity (the latest few hundred entries) and pages through it 25 at a time.
🎯 Good to know: Activity is the accountability layer for sub-users. If a teammate deletes the wrong thing, this is where you see it — down to the IP. It survives reinstalls, because it's panel history, not a server file.
Logs — reading your server's own files
The Logs page opens the log files your server writes — not panel history, but the raw output. Its trick is that it knows where each game keeps its logs, so you don't go hunting through folders.
- Minecraft —
latest.log,server.log,debug.log, and thecrash-reportsfolder. - Applications (Node, Python, Java, and the rest) —
server.log,app.log,error.log,output.log, and friends. - Other games — Factorio, Terraria, Valheim, ARK, Rust, Palworld and many more each have their own known log locations.
Pick a file and it opens with syntax highlighting. From there:
| Button | What it does |
|---|---|
| Refresh | Re-read the file (it's updating live while the server runs) |
| Auto-refresh | Keep pulling new lines automatically — a live tail |
| Download | Save the file to your computer |
| Share | Create a safe public link to the log (see below) |
| Analyze | Scan a Minecraft log for known problems (Minecraft only) |
Search, with regex
A quick filter box narrows the view as you type. Open the advanced filters for level chips (Errors, Warnings, Info, Debug), and — on Minecraft — type chips (Chat, Commands, Players, System). Turn on Regex for pattern searches, plus Match case and Invert (show everything that doesn't match). This is how you pull every ERROR line, or every message from one player, out of a 10,000-line file.
Share a log the safe way
Share is built for asking for help without leaking secrets. It creates a public link to the log, but first it redacts the sensitive stuff automatically — IP addresses, tokens, passwords, keys, emails — both in your browser and again on the server. The link expires after seven days, and you can review the redacted version before you send it. Paste that link into a support ticket or Discord instead of copying raw logs.
⚠️ Heads up: Even with automatic redaction, glance over a shared log before you post it. Redaction catches common patterns; a one-off secret in an odd format is worth a manual check.
Analyze (Minecraft)
For Minecraft servers, Analyze scans the log and lists likely problems with suggested fixes — out-of-memory patterns, plugin errors, connection issues, and more, each with a severity and a recommended solution. It's a rule-based diagnostician, not the AI assistant: it matches your log against a library of known issues. Great for a fast first read of a crash; when it can't explain something, open the file yourself and read from the top.
Which page do I want?
| I'm trying to… | Open |
|---|---|
| See who changed a setting or deleted a file | Activity |
| Find out why the server crashed | Logs (or Monitoring crash history) |
| Get an error out of a huge log file | Logs (regex search) |
| Send a log to support without leaking secrets | Logs → Share |
| Audit a teammate's actions | Activity (member filter) |
Who can see these
Activity needs the activity permission; Logs needs the file read-content permission. Hand them out per person on the Sub-users page — you can let someone read logs to help debug without giving them the run of your files.
Troubleshooting
- The log file I want isn't listed — the server may not have created it yet (it writes on start), or it's in an unusual place; use the File Manager to browse directly.
- Activity doesn't show an old change — the page holds recent history; very old events age out of the view.
- A shared link stopped working — shared logs expire after seven days; share it again.
- Analyze isn't there — it's a Minecraft-only tool; other servers use the search and level filters instead.