Skip to main content

Switching Proxy Types - BungeeCord & Velocity

To start with, switching your proxy version should be done in a controlled environment which is not in current production, such as pre-release before your network opens or on a development network. Switching from Bungee to Velo and vice versa can be difficult and irritating to understand at first, but they basically work fundamentally the same, they are a proxy manager, sending players to the server they request.

Firstly, take a backup of your current proxy and download it. Store it on your PC and open the archive so you can alt tab back to it when you need to read a configuration file.

Before we start, this might solve your issue if you have come from not being able to join after your switch to Velocity.

The most annoying problem that has existed for many years is Velocity for some bizarre reason defaults to 25577 instead of the normal 25565. It makes complete no sense as you wouldn't be running dual proxy on the same port, and that's not even possible on Pterodactyl panel anyway? Rant over. We really don't understand this stupidity. Anyway, to solve it:



Open velocity.toml and find the bind = line. Change it to :25565. Done. Simple as that.

As they say, always read the documentation, the console logs or the application reports first.

Three major differences should be taken into consideration though:

1. When switching to Velocity, you will see an error like the below if you are starting your server with BungeeCord plugins installed in the plugins folder. You need to go and download the Velocity alternatives which can be found on the relevant websites you obtained the plugin from. For example, on GeyserMC's site, you have Velocity and BungeeCord tabs.

2. You need to take into consideration that both types of proxy use different file types.

  • BungeeCord: YAML file type - colons (:), apostrophes (') and code bracket ({}) symbols.
  • Velocity: TOML file type - Commas (,) brackets ([]) and equals (=) symbols.

When you configure your proxies, make sure you YAML/TOML validate your configurations, using websites such as https://www.yamllint.com/ and https://www.toml-lint.com/

3. Plugins will loose ALL their configuration due to the different file types AND the folder names will change their casing to denote a different proxy type. Notice how Velocity always names the folders in lowercase where BungeeCord keeps them uppercase? It's for a reason, to make it easier to reference back and not corrupt any of your old data.