+ Add server

Votifier & NuVotifier tester

Send a test vote to your Minecraft server and see straight away whether Votifier or NuVotifier receives it. Paste a v2 token or a v1 public key: we tell which one it is.

The IP or hostname players join with. Add :port to it to use a different Votifier port.
8192 unless you changed it in the NuVotifier config.
Paste either one: your v1 public.key or your v2 token. We can tell them apart automatically, so there is no method to pick first.
Who the test vote is for. Your vote plugin runs its rewards for this player.

Your IP address is not sent to the server (the vote's address is 0.0.0.0), and nothing you enter here is stored.

Common Votifier errors and what they mean
Signature is not valid (invalid token?)

The token does not match the one your server has. Copy it again from plugins/NuVotifier/config.yml (the value under tokens, usually next to default), without the quotes, and make sure NuVotifier was reloaded or the server restarted after it changed.

error:1E08010C:DECODER routines::unsupported

That public key could not be read. Copy the whole contents of plugins/NuVotifier/rsa/public.key (or plugins/Votifier/rsa/public.key), or use your v2 token instead.

timeout

Nothing answered within a few seconds, so the Votifier port is probably closed. Check the port in the NuVotifier config, that your firewall allows it, and on a hosting panel that the port is allocated to your server.

connect ECONNREFUSED

The connection was refused: nothing is listening on that port. Check the port number and that NuVotifier is installed and enabled.

unexpected greeting

Something answered on that port, but it is not Votifier. You may have entered the game port instead of the Votifier port.

connection closed without response

The server closed the connection without answering. This usually means it rejected the token or key; your server console says why.

How to test Votifier

Enter the address players join with, the Votifier port (8192 by default) and a player name, then paste the credential from your server. NuVotifier's v2 protocol uses a token from plugins/NuVotifier/config.yml; the older v1 protocol uses the public key in plugins/NuVotifier/rsa/public.key. You do not need to say which: a public key is recognised by its format and sent as v1, anything else is sent as a v2 token.

A v2 server answers every vote, so you see immediately whether it was accepted and, if not, why. A v1 server never answers, so a sent v1 vote only proves the connection worked; confirm it in your server console. The test is a real vote, so any rewards your vote plugin gives run for the player you entered.

Questions

Should I use the token or the public key?

Use the token if your server runs NuVotifier: v2 votes are signed and acknowledged, so you know they arrived. The public key is for the original Votifier plugin and for vote sites that only support v1. NuVotifier accepts both unless v1 is turned off in its config.

Where do I find my Votifier token?

In plugins/NuVotifier/config.yml, under tokens. The value next to default is the token; copy it without the quotes. On a BungeeCord or Velocity network, use the token from the proxy's NuVotifier config.

Which port does Votifier use?

8192 by default. It is a separate port from the game port and has to be open to the internet. Many hosts need you to add it as an extra port in their panel, then set the same number in the NuVotifier config.

Will the test vote give rewards?

Yes. If your vote plugin gives rewards for votes, the test runs them for the player name you entered, like any other vote. Use your own name or a test account.

Is it safe to paste my token here?

The token is only used to sign this one test vote and is not stored or logged. If you would rather be sure, change the token in your config afterwards and update it on your vote sites.

Does it work with VotingPlugin, SuperbVote and other vote reward plugins?

Yes. The test vote goes to the Votifier listener (NuVotifier or Votifier), which hands it to whichever reward plugin you run: VotingPlugin, SuperbVote, GAListener, VoteParty or your own. If the vote arrives, those plugins see it exactly like a vote from a server list.

The test passed but nobody got a reward. Why?

Then Votifier works and the problem is in the reward plugin. Check that it is installed on the same server that receives the vote, that its rewards are set up for the service name, and whether it only rewards players who are online. Its own log or console line for the vote usually says why it skipped it.

Which Votifier versions does it support?

NuVotifier with the v2 token protocol, and the v1 public key protocol used by NuVotifier, the original Votifier and forks such as VotifierPlus. It works with Spigot, Paper, Purpur, Folia, Sponge and Fabric or Forge servers that run a Votifier port, as well as BungeeCord and Velocity proxies.

My network runs BungeeCord or Velocity. What do I test?

Test the proxy: its address, the port and token from the proxy's own NuVotifier config. The proxy then forwards the vote to your backend servers. If the test passes but nothing reaches a backend, check the forwarding method and secret in both configs.

How do I receive votes from VoxelRank?

Add your server to VoxelRank and enter the same token or public key in its settings. Every vote on your page is then sent to your server the moment it is cast.

Setting Votifier up from scratch? Read our guide: How to Set Up Vote Rewards (Votifier, VotingPlugin, and More)