NuVotifier not working? Common fixes

Most NuVotifier problems come down to a handful of causes. Work through this list from top to bottom: each fix takes a minute or two.

If you list on CraftVote, start with Vote deliveries on your server's page. It shows each test and real vote, and when one failed, the reason. That tells you which section below to read.

1. NuVotifier didn't start

Look at your server console right after a restart. You should see NuVotifier say which address and port it listens on.

• Nothing from NuVotifier at all? The plugin didn't load. Check that the `.jar` is in `plugins` and that it matches your server type (Paper and Spigot use the Bukkit version).
• An error like "address already in use"? Something else already uses that port. Pick another port in `config.yml` and restart.

2. The port is closed

This is the most common cause by far. The list can't reach your server, so the test says something like "nothing answers" or "connection refused".

• On a game host, add the port in the panel (Network, Ports or Allocations), then put that exact number in `plugins/NuVotifier/config.yml` and restart.
• On a VPS, allow it in the firewall, for example `ufw allow 8192/tcp`.
• At home, forward the port on your router too.

You can check from outside with any online port checker while the server is running.

3. The Votifier port is the game port

NuVotifier needs its own port. If you typed your game port (often 25565) on the list, the list reaches Minecraft instead of NuVotifier. On CraftVote the test then says it got "an answer we couldn't read". Use the port from NuVotifier's `config.yml`.

4. The address is wrong

The address on the list must point to the machine NuVotifier runs on.

• With a proxy (BungeeCord or Velocity), that is the proxy, not a game server behind it.
• Some hosts give your game a domain that only forwards the game port. Use the server's real IP for Votifier instead.

5. DDoS protection is in the way

Services like TCPShield protect your game port by sending players through their network. They only pass Minecraft traffic, so votes sent to the protected address never reach NuVotifier.

Give the list your server's direct IP for Votifier. On CraftVote this address is only used to send votes: it is not shown on your public listing.

6. The token doesn't match

• Copy the token again from `config.yml`, the line after `default:` under `tokens`. Copy all of it, with no spaces at the start or end.
• Deleting `config.yml` makes a new token. If you did that, paste the new one on every list.
• After changing `config.yml`, restart the server, or run `nvreload` from the server console.

7. Your server runs the old Votifier

Some servers still run the original Votifier, which only understands public keys, not tokens. On CraftVote, pick Votifier v1 (public key) on the card and paste the content of `plugins/Votifier/rsa/public.key`. Never paste the private key.

Better still, replace it with NuVotifier: it understands both.

8. The vote arrives, but there's no reward

If the list says the vote was accepted, NuVotifier did its job. The reward comes from your reward plugin.

• Is a reward plugin installed at all? NuVotifier gives nothing by itself.
• In VotingPlugin, the vote site's `ServiceSite` must match the name the list sends. CraftVote sends `CraftVote`. See how to set up VotingPlugin.
• Was the player offline? Most reward plugins keep the reward until the player joins. Check your plugin's offline settings.

9. Bedrock players don't get rewards

If Bedrock players join through Geyser and Floodgate, their names start with a dot by default, like `.Steve_Craft`. The vote must use that name, or the reward plugin can't find the player.

CraftVote sends Bedrock votes with the Floodgate name for you. If you changed Floodgate's `username-prefix`, type the new prefix under Bedrock players on the Votifier card. More in Geyser and Floodgate setup.

Still stuck?

• Set NuVotifier's port, restart, and send one test vote while you watch the console.
• Read NuVotifier's own troubleshooting guide.
• Write to us through Contact with what the test vote said.