Use this guide after the Standalone or Proxy quick start. A successful admin test is not proof that your voting website can reach your server.
On a standalone/backend server, run as an administrator:
/av vote <player> <site>
Here, <site> is the configured VotingPlugin vote-site key (for example, MyFirstSite). Use a player account that has joined the server. Check that the expected test reward runs and the vote is recorded.
On a proxy setup, run on the proxy:
/votingpluginproxy status
/votingpluginproxy vote <player> <site>
The proxy status check is most useful with an online player when using PLUGINMESSAGING.
What this proves: VotingPlugin can process the test; the proxy command also exercises its forwarding path. What it does not prove: the website's public connection, firewall, Votifier key/token, or website-supplied service name.
[VotingPlugin] Received a vote from service site 'SERVICESITEHERE' by player 'ExamplePlayer'!
/av servicesites if you need to see received identifiers. Confirm that VoteSites.yml contains an enabled entry whose ServiceSite matches the received value (case-insensitive matching; do not guess other differences).Example text varies by listener build and debug settings. The important evidence is that the listener received a record and VotingPlugin processed the same vote.
| What you see | Likely stage | What to check next |
|---|---|---|
| Can't connect to the listener / timeout / no Votifier message | Network / listener | Verify public hostname/IP, allocated TCP port, listener startup, OS/host firewall, router forwarding; do not put 0.0.0.0 in the website settings |
| Listener receives nothing or rejects the request | Protocol / credentials | Website protocol must match enabled v1 public-key or v2 token support; check key/token and restart after listener config changes |
| Listener reports a vote but VotingPlugin does not | Plugin integration | VotingPlugin must be installed and loaded on the process receiving the vote; inspect startup errors and enable bounded debug if needed |
| VotingPlugin receives vote but site is missing/wrong | Site matching | Compare incoming ServiceSite to VoteSites.yml; use /av servicesites; make sure Enabled: true and remove placeholder URLs |
| VotingPlugin records vote but no reward arrives | Reward processing | Check Rewards block, reward command syntax, player online/offline behavior, ProcessRewards on backends, and console errors |
| Vote reaches proxy but not backend | Proxy routing | Confirm shared SQL, BungeeMethod, backend Server name, UseBungeecord, plugin-message online-player requirement, and allowed target servers |
| Reward happens more than once | Duplicate forwarding | Use a single Votifier intake; disable VotifierPlus backend forwarding when VotingPlugin does it; review SendVotesToAllServers |
| Bedrock player is missing rewards | Player identity | Follow Bedrock Player Support; ensure the complete configured player prefix reaches the voting service |
AutoCreateVoteSites: true is helpful during discovery. After every intended site is set up, switch it to false and reload so unknown services cannot create more entries.VoteDelay is not inherently vote rejection. Only enable WaitUntilVoteDelay if the website's interval actually matches the configured delay.If you open a support ticket, include your VotingPlugin version, server/proxy type, redacted listener and VotingPlugin log excerpts around a single test vote, and the relevant non-secret ServiceSite and reward configuration.