Direct answer

Update the Velocity proxy separately from backend servers. Preserve its forwarding secret, TOML settings and proxy plugins, then check compatibility before switching to a new build.

Step-by-step procedure

  1. Back up velocity.toml, forwarding.secret and proxy plugins/, plus the current JAR and startup command.
  2. Review the official Velocity migration notes and Java requirements for the target release.
  3. On a staging proxy, install the new JAR and matching proxy plugin builds; keep backend addresses pointed at test servers.
  4. Verify joins, server switching, forced hosts, forwarding identities, permission nodes and restart behavior.

Common mistakes and trade-offs

Do not replace only the proxy JAR and assume every legacy plugin still works. Never regenerate the forwarding secret without also updating all backends that use it.

How to verify it worked

Record working build numbers and test several player routes; roll back the whole proxy configuration and binary together if required.

Version and platform differences

Backend Minecraft versions and proxy versions are separate compatibility concerns; check the official server compatibility reference.

Official references

These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000