How to Set Up Votifier or NuVotifier on Your Server

Votifier is the standard way for server lists to tell your Minecraft server that a player has voted. When someone votes for your server on MinecraftServers.me, we open a connection to your Votifier listener and send the player's username. A reward plugin on your server then hands out keys, coins or whatever you choose. This guide covers NuVotifier, the maintained successor of the original Votifier plugin.

1. Install NuVotifier

1. Download NuVotifier for your platform. It supports Paper/Spigot, Velocity, BungeeCord, Sponge and Fabric.
2. Drop the jar into the plugins folder (or mods on Fabric) and restart the server. Do not use /reload.
3. NuVotifier creates plugins/nuvotifier/config.yml and an RSA key pair in plugins/nuvotifier/rsa/.
4. Install a reward plugin that listens for vote events, for example VotingPlugin or SuperbVote, and configure what voters receive.

2. Choose a protocol: v1 (RSA) or v2 (token)

NuVotifier understands two protocols, and our dashboard supports both. You only need one.

Votifier v1: RSA public key

The original protocol. We encrypt the vote with your server's RSA public key and send the encrypted block. To use it, open plugins/nuvotifier/rsa/public.key, copy the whole key (one long line of base64) and paste it into the voting settings of your server in the dashboard. Keep private.key secret and never paste it anywhere.

v1 has no acknowledgement. The server does not answer after it receives a vote, so a successful send only proves that the connection opened and the data was written. If the key is wrong, NuVotifier logs an error in your console, but we cannot see it. Always confirm a test vote in your server console.

Votifier v2: token

The newer protocol signs each vote with a shared secret token instead of encrypting it, and the server replies with a success or error message. That means our dashboard can tell you whether the vote was actually accepted. Find the token in config.yml under tokens (the default entry works for every list), copy it into the dashboard and choose v2. If you have the choice, use v2.

Votes from this site arrive under the service name MinecraftServers.me. If you prefer a dedicated token for us, add MinecraftServers.me: your-token under tokens and enter that token in the dashboard; the name is case-sensitive.

3. Pick the port and open the firewall

NuVotifier listens on its own TCP port, separate from the game port. The default is 8192, set by port in config.yml; host should normally stay 0.0.0.0 so it listens on all interfaces.

• Dedicated server or VPS: allow inbound TCP on the Votifier port, for example ufw allow 8192/tcp on Ubuntu, and in any cloud firewall or security group in front of the machine.
• Game server host with a panel: many hosts only expose ports you have allocated. Add an extra port in the panel (often under Network or Allocations), set that number as port in config.yml and restart.
• Home hosting: forward the port on your router to the machine running the server, in addition to the game port.
• Behind a proxy (Velocity or BungeeCord): install NuVotifier on the proxy and use its forwarding feature to pass votes to the backend servers, or install it on one backend and expose that backend's Votifier port. Only one public Votifier listener is needed.

If your server uses a DDoS-protected address or a TCP shield service, make sure the Votifier port is forwarded there as well, or enter the server's direct address for Votifier in the dashboard.

4. Connect your listing

1. Sign in and open your servers in the dashboard.
2. Choose your server and open Voting.
3. Enable vote forwarding, enter the Votifier host (usually your server's address without the game port), the Votifier port, and either the v1 public key or the v2 token.
4. Save the settings.

5. Send a test vote

On the same Voting page, use Send test vote with your own username. Then check two places:

• The dashboard result. With v2, you see whether NuVotifier accepted the vote or which error it returned. With v1, you see whether the connection succeeded.
• Your server console. NuVotifier logs every received vote, and your reward plugin should react to it. For v1 this is the only real confirmation.

Troubleshooting

• Connection timed out or refused: the port is closed. Check the firewall, the panel allocation and that NuVotifier started without errors.
• v1: "Unable to decrypt vote" in the console: the public key in the dashboard does not match public.key. Copy it again, without line breaks or spaces.
• v2: signature or token error: the token differs from the one in config.yml, or you regenerated it. Paste the current token.
• Vote arrives but no reward: the reward plugin is not configured or does not handle offline players. Check its settings for offline vote queueing.

Real votes are forwarded the same way, with automatic retries if your server is briefly unreachable. Votes count toward your ranking whether or not forwarding works; see how ranking works for details.