Free tools Windows power users keep installed
One-click scans. No signup required.
To make Minecraft server-list votes work, install NuVotifier on the server or proxy that receives callbacks, expose an unused TCP port, register its generated public key with each voting site, and install a separate vote-listener plugin to issue rewards. NuVotifier receives and verifies votes; it does not give players items, currency, ranks, or commands by itself.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Minecraft Java servers with free DDoS protection and up to three free backups a day.
This guide covers Paper and Spigot servers, BungeeCord and Velocity networks, port and firewall requirements, end-to-end testing, and the common reasons a listener is online but rewards still do not arrive.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft | Java & Bedrock Ultimate Collection | Windows Digital Code | $49.99 | Buy on Amazon |
| 3 |
|
Minecraft | Standard Edition | XBOX Digital Code | $19.99 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What Votifier does—and what NuVotifier does not do
Votifier is the protocol used by many Minecraft server-list websites to notify a server that a player voted. NuVotifier is the current Votifier-compatible receiver for Bukkit-family servers and also has builds for Sponge, BungeeCord, Waterfall, and Velocity. A voting site connects to the endpoint you publish, sends an encrypted vote callback, and NuVotifier validates and hands that vote to other plugins.
NuVotifier deliberately stops at receiving the vote. The project documentation says that it includes no listeners by default. A separate listener plugin must decide what a vote should do: run a command, grant an item, add currency, award points, announce the vote, or queue a reward until the player next joins. Examples of compatible listener plugins include VotingPlugin and SuperbVote; follow the listener’s own documentation for reward syntax and per-site settings.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
That separation explains a frequent symptom: NuVotifier logs a successful vote, but the player receives nothing. The network path is working in that case; the listener is missing, disabled, or incorrectly configured.
Requirements and decisions before installation
- A Paper, Spigot, Bukkit-family, Sponge, BungeeCord, Waterfall, or Velocity installation that allows plugins.
- Permission to upload a plugin JAR, restart the relevant process, and read its console logs.
- An unused TCP port that outside voting sites can reach. Valid TCP port numbers are 1 through 65535. Do not reuse the Minecraft gameplay port or a port already owned by another service.
- Firewall, NAT, and hosting-panel access sufficient to allow that port. On shared hosting, the provider may require you to select an assigned port rather than choosing any number.
- A voting-site account or server-list entry that accepts a Votifier address, port, and public key.
- A separate vote-listener plugin if votes are to produce rewards.
For one public Minecraft server, NuVotifier normally listens directly on that server. For a BungeeCord or Velocity network, the usual design is one public NuVotifier endpoint on the proxy and forwarding to backend servers through plugin messaging. Backend servers can remain private. Proxy forwarding is available for more specialized topologies but requires additional ports and v2 tokens.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsSingle-server setup on Paper or Spigot
1. Install NuVotifier
- Download the NuVotifier build appropriate for your platform from the official project distribution or its Spigot listing.
- Place the JAR in the server’s
plugins/directory. - Start or restart the Minecraft server. On the first start, NuVotifier creates its data directory, configuration, and RSA key pair.
- Stop and start the server again after making configuration changes; a full restart is safer than relying on an unsupported generic reload.
NuVotifier’s platform support is documented across Bukkit-family servers, Sponge, BungeeCord/Waterfall, and Velocity. Use the build that matches the process receiving the connection; a proxy build belongs in the proxy’s plugin directory, not in a backend server’s directory.
2. Choose a reachable listener endpoint
Open the configuration generated in NuVotifier’s plugin data directory. Unless your host requires a particular interface, set the listener host to 0.0.0.0. That binds on all local interfaces and is usually the practical choice for a server behind a hosting panel or NAT.
Set port to an unused TCP port between 1 and 65535. The number 8192 is a common example and may be used as a default when a host assigns it, but it is not a universal entitlement. A panel may expose only a small list of ports; select one of those and use the same number when registering the server on voting sites.
Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
host: 0.0.0.0
port: 8192The snippet illustrates the values, not a complete configuration file. Preserve the other keys generated by your NuVotifier version. Never point the listener at the Minecraft gameplay port or a port occupied by another plugin, daemon, or proxy.
3. Restart and confirm that the port bound
Restart the server and read the console from startup through the NuVotifier enable message. You should see that NuVotifier enabled and is listening. If it reports that the address cannot be bound, another process is using the port, the host did not assign it, or the service lacks permission to open it. Choose another assigned port or ask the host to open one.
A successful local startup proves only that the process opened the socket. It does not prove that an Internet voting site can reach it. Firewall rules, NAT forwarding, cloud security groups, and shared-host restrictions still need to allow inbound TCP traffic on that exact port.
4. Copy the public key, never the private key
NuVotifier generates an RSA key pair in its data directory. Recent hosting instructions place the public key at plugins/Votifier/rsa/public.key. Open that file, copy the complete key including its beginning and ending lines, and paste it into the Votifier settings for every voting site that will notify this server.
The public key is intended for distribution to voting sites. The private key must remain on the receiving server and must not be pasted into a listing, chat, ticket, repository, or web form. If you replace or regenerate the key pair, every site using the old public key must be updated.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that is unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world full of surprises.
- SURVIVAL ADVENTURES — Face mysterious foes, travel across varied landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play solo or join friends in local split-screen and cross-platform play across console, mobile, and PC. Online multiplayer supports up to 8 players.
- COMMUNITY PLAY — Connect with players on community servers, or subscribe to Realms Plus (sold separately) to play with up to 10 friends on a private server.
5. Install and configure a vote listener
Install a maintained listener plugin on the same server that will process the vote. NuVotifier accepts the callback, while the listener maps the vote to a player and performs the configured action. Configure rewards, commands, cooldowns, vote multipliers, and site names in the listener’s own files.
Restart after installing the listener and check that both plugins enable without errors. If the listener has a dependency or optional integration, install the dependency specified by that listener’s documentation. Do not assume that installing NuVotifier alone creates a reward.
6. Register the endpoint on each voting site
In each server-list entry, provide the address that the site should contact, the NuVotifier listening port, and the complete public key. The Minecraft gameplay address and the Votifier address can be the same hostname with different ports, or they can be different hostnames. Use the externally reachable address, not an internal Docker, LAN, or proxy address that a public site cannot route to.
Listing sites use different field names and validation rules. Some ask for a hostname, some for an IP address, and some have separate fields for the Votifier address and port. Follow the fields shown by that site and keep a record of which endpoint and key each listing uses.
Recommended Free Tools
7. Test the complete path
On Bukkit-family and Sponge servers, run /testvote from the server console. The command is intended to simulate a vote without waiting for a public listing. Then check both the NuVotifier log line and the listener’s output.
Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
- Confirm that NuVotifier reports receipt of the test vote.
- Confirm that the listener identifies the expected player and voting site.
- Confirm that the configured reward, command, announcement, or queue entry appears.
- Check the player’s inventory, balance, permissions, or other target state.
If NuVotifier logs the test but no reward occurs, the network receiver is functioning and the remaining investigation belongs in the listener’s configuration and error log.
NuVotifier on a BungeeCord or Velocity network
A proxy network adds a forwarding decision: should the public proxy pass votes to backends over the proxy channel, or should each backend expose its own listener port? For ordinary networks with one proxy and connected backend servers, plugin messaging is usually simpler and supports queueing when a player is not currently connected to a target backend.
Recommended arrangement: pluginMessaging
- Install the NuVotifier proxy build on the public BungeeCord or Velocity proxy.
- Install the compatible NuVotifier backend component on every server that must process votes.
- Give the proxy a unique, externally reachable listener port and register voting sites against the proxy’s address, port, and generated public key.
- In each backend’s forwarding configuration, select
pluginMessaging. - Set the backend forwarding
portto-1. The backend receives the forwarded vote through the proxy channel rather than opening its own public Votifier port. - Verify that the proxy is connected to each target backend and that the necessary plugin channel is enabled on both sides.
Keep backend servers inaccessible directly from the public Internet when your topology permits it. A backend that accepts direct, unauthenticated vote traffic can be abused independently of the proxy. Restrict backend firewall rules to the proxy and management sources rather than exposing every backend listener.
Plugin messaging can queue a vote until the player joins the backend that should process it. That behavior is useful for networks where a player votes while offline or while connected to a different server, but the listener still needs to support the queue and the target server must eventually connect.
Specialized arrangement: proxy forwarding mode
Use proxy mode only when plugin messaging does not fit the network topology or an advanced deployment specifically needs it. In this design, every backend that receives forwarded votes listens on its own unused port. The proxy configuration lists each backend’s address and port and authenticates forwarding with that backend’s generated v2 token.
Best Value
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Do not substitute the RSA public key from the rsa/ directory for a v2 token. They serve different purposes: the RSA public key authenticates callbacks from voting sites, while the v2 token identifies and authorizes a backend in proxy forwarding mode. Copy the exact token generated for each backend and keep it private.
Because each hop can fail independently, test the proxy, every backend listener, and the reward listener separately. A proxy log entry proves that the public callback reached the proxy; it does not prove that a backend accepted the forwarded vote.
Proxy test commands
On BungeeCord, use /ptestvote to simulate a vote through the proxy. On backend Bukkit-family or Sponge servers, use /testvote as appropriate. Read the proxy log and every backend log during the test. The expected chain is public endpoint or test command, proxy receipt, forwarding, backend receipt, and listener reward.
Single server versus proxy deployment
| Decision point | Single Paper/Spigot server | Proxy network with pluginMessaging | Proxy mode |
|---|---|---|---|
| Public exposure | One public NuVotifier endpoint on the server | One public endpoint on the proxy; backends can remain private | One public proxy endpoint plus backend listener ports |
| Forwarding | None | Proxy channel; backend forwarding port is -1 |
Explicit backend address, port, and v2 token for each target |
| Reward processing | Requires a separate listener plugin | Requires a separate listener on the backend that grants the reward | Requires a separate listener on each backend that grants the reward |
| Queueing | Depends on the listener; no proxy hop | Can queue a vote until the player joins the target backend | Depends on the forwarding and listener design |
| Operational complexity | Lowest | Usually the simplest network option | Higher; more ports, tokens, and logs to verify |
| Main host constraint | One assigned and reachable TCP port | One assigned proxy port and working proxy-to-backend channel | Proxy port plus an unused reachable backend port for each destination |
Configuration reference
| Value | Where it is used | What to check |
|---|---|---|
host |
Listener bind address | 0.0.0.0 is usually workable unless the host requires a specific interface; do not use an unreachable private interface. |
port |
Public NuVotifier listener | Must be an unused TCP port from 1 through 65535 and allowed by the panel and firewall. 8192 is only a common example. |
| Public RSA key | Voting-site Votifier settings | Paste the complete key generated by the receiving NuVotifier instance. Never expose the private key. |
method: pluginMessaging |
Backend forwarding in the usual proxy design | Backend port is -1; verify the proxy is connected and the channel is available. |
| Proxy-mode backend token | Advanced proxy forwarding | Use the backend’s v2 token, not the RSA key in the rsa/ directory, and match every address and port. |
Troubleshooting by symptom
No NuVotifier log entry when a real vote is submitted
- Confirm NuVotifier enabled during startup and that you are checking the process that owns the public endpoint.
- Compare the voting site’s address and port with the current external address and NuVotifier configuration. A changed hosting IP or port invalidates the listing.
- Check whether another process already owns the port. A bind error in the startup log means NuVotifier never opened it.
- Review Linux firewall rules such as
iptablesorufw, Windows Firewall rules, cloud security groups, and router NAT or port-forwarding rules. - On shared hosting, ask whether the selected port is actually assigned and open for inbound connections. A port shown in a panel may still require activation by the host.
- For a proxy deployment, test the proxy endpoint rather than a private backend address.
NuVotifier logs the vote, but no reward appears
Install and enable a vote-listener plugin, then inspect its reward configuration and error output. Verify that the player name, site name, command syntax, permissions, economy integration, and offline queue behavior match the listener’s documentation. NuVotifier itself will not grant an item or currency, so changing its port or RSA key cannot fix a listener-side reward error.
“Could not decrypt data (is your key correct?)”
Copy the complete public key from the exact NuVotifier instance receiving the callback and replace the key saved at the voting site. Check for missing beginning or ending lines, wrapped text, extra spaces, or a key from a different server. If the server regenerated its RSA pair, every listing must receive the new public key.
The proxy receives votes, but a backend does not
- Confirm the backend uses the intended forwarding method.
- For plugin messaging, verify the backend port is
-1, the proxy is connected, and the channel is enabled. - Check backend whitelist or blacklist settings that could exclude the target server or vote site.
- Confirm the backend listener is enabled and read its log, not only the proxy log.
- Test while the target player is online, then test again after reconnecting if the listener is expected to queue votes.
Proxy mode fails to forward
Verify every backend address and port, use the v2 token generated by that backend, and compare proxy and backend logs at the same timestamp. A single wrong token or closed port breaks that backend’s hop while other backends may continue to work.
Reload commands do nothing or produce errors
For Bukkit and Sponge, run /nvreload from the server console only; the command is intentionally not available in-game. For BungeeCord or Velocity, use /pnvreload in the proxy console. Do not use the generic Minecraft /reload command or a plugin-manager reload operation for NuVotifier. The project’s troubleshooting guidance treats those generic reload methods as unsupported; if one was already attempted, perform a full process restart before diagnosing further.
Quick Recap
Security and maintenance practices
- Keep the RSA private key and all proxy-mode v2 tokens secret. Treat them like credentials and restrict file permissions on the plugin data directory.
- Expose only the endpoint that voting sites need. On a proxy network, firewall backend servers so the public Internet cannot submit direct vote traffic.
- Record the public endpoint, assigned port, key-generation date, and the voting sites that use it. This makes a host migration or key replacement less error-prone.
- After changing a port, public IP, hostname, forwarding mode, or key pair, update the affected listing entries and run a test before announcing the change.
- Read logs after every restart. A listener that failed to bind can look like a voting-site outage even though the Minecraft server itself is online.
A complete verification checklist
- NuVotifier is installed in the correct server or proxy plugin directory and enabled without startup errors.
- The configured host and port are valid; the port is unused, assigned by the host, and allowed through firewall and NAT rules.
- The voting site contains the current public key from the receiving NuVotifier instance.
- A compatible vote listener is installed and its reward configuration is enabled.
- A single-server
/testvote, proxy/ptestvote, or equivalent platform test produces a NuVotifier receipt. - The listener logs the same test and performs the expected reward.
- On a network, proxy and backend logs both show the vote, and queueing works when the player joins later if that behavior is required.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
