Skip to Content
FluxStore is currently invite-only. Some sections of this documentation are still being written and expanded.
ServersTroubleshooting

Troubleshooting

Solutions for common issues with the FluxStore plugin, server connections, and command delivery.

Start here: Check the dashboard Servers page first. The status indicator shows whether your server is connected. This tells you immediately whether the issue is with the connection or with command delivery.

Plugin Not Connecting

”Connection refused” or “Connection timed out”

Cause: Your server cannot reach the FluxStore platform over the network.

Solutions:

  1. Check internet access: confirm your server has outbound internet access. Try running curl https://api.fluxstore.net from the server’s command line
  2. Check firewall rules: ensure your firewall allows outbound connections on port 443 (HTTPS/WSS). The plugin connects outbound only, so no inbound ports need to be opened
  3. Check proxy settings: if your server is behind a reverse proxy or NAT, ensure WebSocket connections are not being blocked

”Invalid token” or “Authentication failed”

Cause: The connection token in your plugin configuration does not match the token in your dashboard.

Solutions:

  1. Navigate to Servers in your store dashboard and copy the connection token for this server
  2. Open plugins/FluxStore/config.yml on your server
  3. Verify the token value matches exactly, with no extra spaces, quotes, or line breaks
  4. Restart the server after updating the token

If you recently regenerated the token in your dashboard, the old token is immediately invalidated. Make sure the plugin config has the new token.

Plugin loads but shows “Disconnected”

Cause: The plugin started but could not establish or maintain a WebSocket connection.

Solutions:

  1. Check your server console for specific error messages from the FluxStore plugin
  2. Verify the server has a stable internet connection
  3. Restart the server entirely if the issue persists

Commands Not Executing

Player is offline

Some commands require the target player to be online (e.g., give, teleport). FluxStore will queue commands and attempt delivery when the player joins. Where possible, use commands that work on offline players. LuckPerms commands, for example, work regardless of whether the player is online.

Command syntax errors

Cause: The command as written in FluxStore contains a syntax error that the server rejects.

Solutions:

  1. Test the command manually in your server console, replacing variables with real values
  2. Make sure you are not including a leading slash. Write give {player} diamond 64, not /give {player} diamond 64
  3. Check that variable names are spelled correctly: {player}, {uuid}, {transaction_id}, {price}, {quantity}
  4. Verify the required plugin is installed and enabled on your server (e.g., LuckPerms must be installed for lp commands)

Permission issues

FluxStore commands execute from the server console, which has full operator permissions by default. If a command still fails, check that the target plugin supports console execution. Some plugins restrict certain commands to in game players only.

Commands queued but not delivered

Check that your server shows Online in the dashboard. Queued commands deliver automatically when the server reconnects. If commands remain undelivered after reconnection, check Orders in your dashboard for delivery status and error details.

Connection Drops

Server restarts

The plugin automatically reconnects after a server restart. Any commands queued during downtime are delivered once the connection is reestablished. No manual action is needed.

Intermittent disconnections

Cause: Unstable network between your server and FluxStore.

Solutions:

  1. The plugin reconnects automatically with exponential backoff. Brief disconnections are handled transparently
  2. Check your server’s network stability with your hosting provider
  3. Monitor your server console for repeated disconnect/reconnect cycles

”WebSocket error” in console

Cause: The WebSocket connection encountered a protocol level error.

Solutions:

  1. Ensure you are running the latest version of the FluxStore plugin
  2. Check that no network middleware (firewalls, proxies, DDoS protection) is interfering with WebSocket connections
  3. If you use a hosting panel (Pterodactyl, Multicraft, etc.), verify it does not restrict outbound WebSocket connections

Multiple Server Issues

Wrong server receiving commands

Open the package in your dashboard and check the server selection for each delivery command. Ensure each command is assigned to the correct server, and that each server has its own unique connection token.

One server online, another offline

Each server connects independently. One going offline does not affect others. Check the offline server’s console for connection errors and verify its token is configured correctly. Commands targeted at the offline server will be queued until it reconnects.

Plugin Version

Run /fluxstore version in your server console to check the installed version. If you’re experiencing issues, update to the latest version from Servers in your dashboard. See Plugin Installation for update instructions.

Running an outdated plugin version may cause connection failures or missing features. Always update to the latest version before investigating other issues.

Getting Help

If the steps above don’t resolve your issue:

  1. Check the dashboard: the Orders section shows detailed delivery logs for each command, including error messages and retry attempts
  2. Collect logs: gather relevant console output from your server showing the FluxStore plugin’s error messages
  3. Contact support: reach out through the FluxStore dashboard or join our Discord community 

When contacting support, include your server platform and version (e.g., Paper 1.21.4), FluxStore plugin version, relevant console errors, and a description of the expected vs. actual behavior.

Next Steps

Plugin InstallationStripe Setup