Votifier lets server-list sites notify your Minecraft server when a player votes. Your reward plugin listens for that event and can give kits, keys, coins, or other perks.
NuVotifier is the modern maintained fork. Prefer protocol v2 (shared token + HMAC). Classic v1 uses RSA public-key encryption and is mainly for older setups.
Test as you go — use our free Votifier Tester to send a real TCP vote the same way a listing site would.
Step 01
Install NuVotifier
- Download NuVotifier for your platform (Paper / Spigot backend, or a proxy build if votes terminate on BungeeCord / Velocity).
- Drop the JAR into
plugins/and start the server once so it generates config files. - Confirm the plugin enabled in console (
/pluginsshould list NuVotifier in green).
Step 02
Configure host and port
Open plugins/NuVotifier/config.yml (path may vary slightly by fork).
- Set
host: 0.0.0.0so the listener binds on all interfaces — notlocalhost/127.0.0.1. - Note the
port(default8192) and open TCP for that port in your VPS, panel, or cloud firewall. - On a proxy network, bind and expose the host/port where NuVotifier actually runs — matching what list sites will use.
If the listener only binds on LAN, external testers and vote sites will time out even when the plugin looks fine locally.
Step 03
Copy your v2 token (or v1 public key)
Protocol v2 (recommended): copy the token from the tokens: section (often under default:). Paste it exactly — no quotes or trailing spaces.
Classic v1: use the contents of the RSA public.key file (never the private key). Listing sites encrypt the vote with that public key.
Step 04
Send a test vote
- Open the Votifier Tester.
- Choose NuVotifier v2 or Classic v1 to match your config.
- Enter a dummy Minecraft username, your public hostname or IP, port, and token (or public key).
- Send the test vote and watch server console / your vote-reward plugin for the incoming event.
A real vote event is sent — reward plugins may react. Use a dummy username while testing.
Step 05
Troubleshooting
| Symptom | Likely fix |
|---|---|
| Connection refused / timeout | Port not open, wrong IP, or NuVotifier not running. Check /plugins, firewall rules for TCP 8192, and that host is 0.0.0.0. |
| Handshake failed (v2) | Plugin may not speak v2, or wrong port. Classic Votifier does not speak v2 — switch to Classic v1 + public key. |
| Signature rejected (v2) | Token typo. Copy from config.yml exactly. |
| Decrypt / encryption failed (v1) | Wrong RSA key. Use public.key, not private.key. |
| Vote sent but no reward | Votifier received it, but the reward plugin isn’t listening or filters the service name. Check that plugin’s config and logs. |
FAQ
Frequently asked questions
What port does NuVotifier use?
The default NuVotifier port is 8192 (TCP). Open that port in your VPS or panel firewall and point list sites at the same host and port.
Should I use NuVotifier v2 or classic v1?
Use NuVotifier protocol v2 with a shared token whenever possible. Classic v1 uses RSA public-key encryption and is mainly for older setups.
Why does my test vote time out?
Usually the listener is bound to localhost, the port is closed, or NuVotifier is not running. Set host to 0.0.0.0, confirm the plugin is enabled, and expose TCP 8192 publicly.