Troubleshooting

Most sxPanel issues come down to the monitor/ folder swap, the FXServer launch command, or Discord bot configuration. This page covers the most common ones.

The panel URL does not open

sxPanel prints a setup URL to the console on first boot. If you started FXServer with +exec server.cfg, the panel may not have started. Launch without it — sxPanel manages the server lifecycle for you.

Confirm the monitor/ folder contains the sxPanel build and that FXServer loaded a resource literally named monitor (this is required — see the Events API note on the resource name).
Check the console for the printed URL; it usually runs on http://localhost:40120.
If the port is in use, set the TXHOST_TXA_PORT environment variable to an alternate port (see Configuration).

Migration from txAdmin appears broken

Existing txData directories work without modification. If something looks off:

Verify you replaced the entire monitor/ folder, not just part of it.
Confirm txData is in its original location and is readable by FXServer.
Restart FXServer so sxPanel re-scans the data directory.

See the Quick Start for the full migration walkthrough.

The Discord bot is offline

Double-check the bot token and "Bot Enabled" toggle in the panel's Discord settings.
Make sure the Server Members Intent and Message Content Intent are enabled for your bot application in the Discord Developer Portal — the bot needs both to resolve roles and read command interactions.
Re-invite the bot with the correct scopes if it was removed.

Players can't connect after enabling whitelist

Confirm the active whitelist workflow matches what you intend (Admin Only, Discord Member, Discord Role, or Manual Review).
For Discord Role workflows, verify the role IDs configured in Discord settings.
Remember only one workflow is active at a time — check the Whitelist guide if you expected multiple checks to combine.

Charts or console look empty

Insights and the live console depend on the server running through sxPanel. If you bypass the panel and start FXServer directly, telemetry won't be captured. Always start via sxPanel so it can instrument the server.

Still stuck

If none of the above helps, join the Discord community or open an issue on GitHub. Include the relevant JSONL log lines from the system logger — they make diagnosing much faster.