Troubleshooting Guide
Common issues and their solutions
🔍 Quick Debug Checklist
Before diving into specific issues, verify these basics:
- Both plugins installed (proxy + backend on ALL servers)
- All servers restarted after installation
- Server names in config.toml match velocity.toml exactly
- Config file has no syntax errors (valid TOML)
- Players have
velocitynexus.serverpermission - Using compatible Minecraft versions (1.16.5+)
❌ Issue 1: "Server Offline" Error
Player clicks server in GUI → "This server is offline or doesn't exist"
Cause
Server name in config.toml doesn't match the name in velocity.toml
Solution: Verify Server Names
Step 1: Check Velocity Configuration
# Location: Velocity/velocity.toml
[servers]
hub = "127.0.0.1:25566"
Survival = "127.0.0.1:25567" # Note: Capital S!
minigames = "127.0.0.1:25568"
Step 2: Match Names Exactly in Config
# Location: Velocity/plugins/velocitynexus/config.toml
[servers.hub] # ✓ Matches exactly
display-name = "HUB"
enabled = true
[servers.Survival] # ✓ Capital S matches!
display-name = "SURVIVAL"
enabled = true
[servers.minigames] # ✓ Matches exactly
display-name = "MINIGAMES"
enabled = true
"hub" ≠ "Hub" ≠ "HUB"
"survival" ≠ "Survival"
Verification Steps
- Open
Velocity/velocity.toml - Note the exact spelling and capitalization of each server name
- Open
Velocity/plugins/velocitynexus/config.toml - Update the
namefield to match exactly - Run
/velocitynexus reloador restart - Test the GUI again
❌ Issue 2: GUI Not Opening / "Internal Server Error"
Player types /server → Nothing happens or "An internal error occurred"
Cause
Most Common: Backend plugin is missing on the current server
Solution: Verify Backend Plugin Installation
Step 1: Check Plugin List on Backend Server
On the Spigot/Paper server console (NOT Velocity), run:
plugins
You should see:
Plugins (5): VelocityNexusBackend, OtherPlugin1, OtherPlugin2, ...
If you don't see VelocityNexusBackend in the list, the backend plugin is NOT installed!
Step 2: Install Backend Plugin
- Download
velocitynexus-spigot.jarfrom download page - Place it in
SpigotServer/plugins/folder - Restart the Spigot/Paper server
- Verify with
pluginscommand again
Step 3: Install on ALL Backend Servers
The backend plugin must be on EVERY Spigot/Paper server in your network:
- ✓ Hub server
- ✓ Survival server
- ✓ Minigames server
- ✓ Creative server
- ✓ ALL other servers
Other Possible Causes
- Plugin failed to load (check console for errors)
- Incompatible Minecraft version
- Plugin messaging not enabled in Velocity config
❌ Issue 3: Items Not Showing in GUI
GUI opens but shows no items, or items appear as "MISSING" blocks
Cause
Invalid or incompatible material names in config.toml
Solution: Fix Material Names
Common Material Name Issues
❌ Wrong (Common Mistakes)
material = "RED_BED" # Wrong in 1.16
material = "NETHER STAR" # No spaces!
material = "minecraft:grass_block" # No namespace!
material = "GrassBlock" # Wrong case!
material = "bed" # Too generic!
✓ Correct
material = "BED" # Correct for 1.16
material = "NETHER_STAR" # Underscore!
material = "GRASS_BLOCK" # No namespace
material = "GRASS_BLOCK" # Uppercase with underscore
material = "WHITE_BED" # Specific color
Version-Specific Materials
Some materials have different names in different Minecraft versions:
| Old Name (1.12) | New Name (1.16+) |
|---|---|
BED |
WHITE_BED, RED_BED, etc. |
SKULL_ITEM |
PLAYER_HEAD |
WOOD |
OAK_WOOD, SPRUCE_WOOD, etc. |
STEP |
STONE_SLAB |
How to Find Valid Material Names
- Check Spigot Material Javadocs
- Look for your Minecraft version (e.g., 1.16.5, 1.20)
- Copy the exact material name (all caps, underscores)
- Use in your config.toml
❌ Issue 4: "You are already connected to this server"
Player tries to connect to the server they're already on
Cause
This is expected behavior - Velocity prevents connecting to the same server twice
Why This Happens
- Player is on "hub" and clicks "hub" in the GUI
- Player types
/server hubwhile already on hub - This is a safety feature from Velocity
Solution (If Desired)
To test with multiple servers:
- Connect to server A
- Open GUI with
/server - Click on server B (different server)
- Connection should work!
If you see this message, it means Velocity Nexus is functioning correctly. The plugin successfully sent the connection request to Velocity.
❌ Issue 5: Config Not Reloading / Changes Not Applied
Ran /velocitynexus reload but changes aren't showing in GUI
Solution 1: Check Reload Command
/velocitynexus reload
Make sure you're running this on the Velocity proxy console, not a backend server!
Solution 2: Verify Config Syntax
TOML syntax errors prevent config from loading:
❌ Invalid TOML
title = Server Selector # Missing quotes!
rows = "3" # Shouldn't be string
name = hub # Missing quotes!
✓ Valid TOML
title = "Server Selector" # Quoted string
rows = 3 # Number
name = "hub" # Quoted string
Solution 3: Full Restart
Some changes require a full restart:
- Stop Velocity proxy
- Wait 5 seconds
- Start Velocity proxy
- Test the GUI again
Solution 4: Check Console for Errors
Look for error messages after reloading:
[ERROR] Failed to load config: Invalid TOML syntax at line 15
❌ Issue 6: Permission Errors
"You don't have permission to use this command"
Solution: Grant Base Permission
Using LuckPerms
# Give everyone access to /server
/lp group default permission set velocitynexus.server true
# Give specific user access
/lp user PlayerName permission set velocitynexus.server true
Verify Permission
/lp user PlayerName permission check velocitynexus.server
Admin Permission Issues
If admins can't reload:
/lp user YourUsername permission set velocitynexus.admin true
🔧 Complete Debug Checklist
Work through this checklist systematically:
1. Verify Plugin Installation
- Run
/pluginson Velocity → See "VelocityNexus" - Run
pluginson EACH backend server → See "VelocityNexusBackend" - Both plugins show as GREEN (enabled)
2. Check Configuration Files
- Config file exists at
Velocity/plugins/velocitynexus/config.toml - Server names match velocity.toml exactly (case-sensitive)
- No TOML syntax errors
- Material names are valid for your Minecraft version
3. Verify Permissions
- Players have
velocitynexus.serverpermission - Admins have
velocitynexus.adminpermission (for reload) - Per-server permissions set correctly (if using them)
4. Test Functionality
- Type
/server→ GUI opens - GUI shows all configured servers
- Clicking server connects successfully
- Player counts show correctly
5. Check Console Logs
- No errors during plugin load
- No errors when opening GUI
- No errors when clicking servers
Still Having Issues?
We're here to help! Get support from the community