-
-
Notifications
You must be signed in to change notification settings - Fork 82
proxy method REDIS
Redis carries VotingPlugin messages between the proxy and backend servers. It does not replace VotingPlugin's shared SQL storage requirement.
- VotifierPlus or NuVotifier and VotingPlugin run on the proxy.
- VotingPlugin runs on each participating backend.
- Every instance uses the same SQL database/table naming.
- Every instance connects to the same Redis service and communication prefix.
Disable VotifierPlus/NuVotifier forwarding targets in this standard layout; VotingPlugin performs the backend forwarding.
BungeeMethod: REDIS
Redis:
Host: redis.internal.example
Port: 6379
Username: 'votingplugin'
Password: 'replace-with-a-secret'
Prefix: ''
#Db-Index: 0Configure the proxy Database section as well.
UseBungeecord: true
BungeeMethod: REDIS
Server: lobby
Redis:
Host: redis.internal.example
Port: 6379
Username: 'votingplugin'
Password: 'replace-with-a-secret'
Prefix: ''
#Db-Index: 0Give every backend a different Server value.
Configure the same SQL database and use:
AllowUnjoined: trueThis lowercase-d spelling is the backend key. The proxy key is separately named AllowUnJoined; in the standard 7.1.1 proxy-managed layout it remains false, so the proxy validates the player before forwarding.
With BungeeManageTotals: true (the supported release default), totals are owned by the proxy. Set SendVotesToAllServers: false when one backend should execute the per-vote reward for the network.
- Keep Redis on a private network or behind firewall rules that allow only participating hosts.
- Require a dedicated Redis ACL user and non-empty password with only the commands/channels VotingPlugin needs.
- Do not expose port 6379 to the public Internet or publish credentials in screenshots and logs.
-
Host: localhostworks only when Redis is on the same machine or network namespace as that VotingPlugin instance. - Use a trusted private tunnel or Redis TLS configuration when traffic crosses untrusted networks.
- Restart the proxy and every backend after changing the method.
- Run
/votingpluginproxy status. - Run
/votingpluginproxy vote <player> <site>. - Confirm exactly the intended backend or backends process the vote.
- Then send a real/listener-generated vote to test Votifier and public network reachability.
For duplicates, verify unique backend Server names, a consistent Redis prefix, SendVotesToAllServers, backend ProcessRewards, and disabled Votifier forwarding.
- Vote Milestones
- Vote Streak System
- Vote Reminders β Current System
- Legacy Vote Reminding
- Vote Broadcast System
- Vote Logging
- Webhooks
- Time Changes
- Month Date Totals
- VoteShop
- Rewards Overview β Start Here
- Special Rewards
- Reward System Concepts
- Reward File Format
- Where to Set Rewards
- All Reward Possibilities
- AdvancedPriority Rewards
- Reward Examples
- Delayed Reward Command
- World Example
- VotingPlugin-Specific Rewards
- Commands & Permissions
- Signs
- API
- PlaceholderAPI Placeholders
- Minecraft Server Lists
- Bedrock Player Support
- Transferring Data Storage