HomeGuidesNetworkingLinking servers with Velocity
Guide External plan Setup

Connecting an external server

Already hosting somewhere else? Put your server on the PulsedMC network and get your own pulsedmc.net address players can join from the lobby.

1

What the External plan is

The External plan connects a server you already host — BisectHosting, another provider, a machine at home — to the PulsedMC network. You get an address like yourserver.pulsedmc.net, and players can hop to you straight from the lobby.

We don't host it, bill it for resources, or touch your files. It stays entirely yours. All that changes is that our proxy knows how to reach it.

You keep full control Your world, plugins, backups and console stay with your existing host. Nothing moves.
2

Add your server

Go to pulsedmc.net/connect and enter three things: a name, the address players currently use to reach your server, and its port (usually 25565).

Example
Server name   My SMP
Address       mc.example.com
Port          25565

Use the real public address of your server. Private or local addresses (localhost, 192.168.x.x) are rejected, because our proxy has to reach it over the internet just like a player would.

3

Prove the server is yours

You'll be given a short code that looks like pmc-verify-a1b2c3d4. Put it anywhere in your server's MOTD, restart, then press Verify.

server.properties
motd=My SMP pmc-verify-a1b2c3d4

We read your MOTD back off a normal server-list ping. This stops anyone adding a server they don't own. Once it's confirmed you can remove the code again.

Not working? The MOTD only changes after a full restart — a reload usually isn't enough. Check the server list in your own client first; if you can't see the code there, neither can we.
4

Wait for staff review

Every external server is checked by a staff member before it joins the network. Your server shows as Awaiting review until then. Nothing happens on your side while you wait.

Once approved you'll see it marked Live along with your new yourserver.pulsedmc.net address.

5

That's it — nothing to configure

Once a staff member approves your server it goes live within about twenty seconds. There is nothing to change on your side: no config edits, no secrets, no restart.

Your server keeps its own online-mode, its own settings and its own IP. When a player joins your pulsedmc.net address our proxy hands them straight to you, so anyone using your original address is completely unaffected.

Both addresses work Players can reach you at your pulsedmc.net address or at your original IP. Neither one interferes with the other.
One requirement Being handed off needs Minecraft 1.20.5 or newer. Older clients are shown your direct address instead of being dropped somewhere confusing.
6

Optional: let players get back to the hub

Because players are handed off to you rather than proxied, they are no longer connected to the PulsedMC network once they arrive — so the network's own /lobby cannot reach them. If you want them to be able to come back without reconnecting manually, install PulsedLink.

Install
1. Download pulsedlink-1.0.0.jar from pulsedmc.net/connect
2. Drop it in your server's plugins/ folder
3. Restart your server

That gives your players /lobby, /hub and /leave, which send them straight back to the PulsedMC hub. It also shows a one-line hint shortly after they join so they know the command exists — both the message and the delay are configurable in plugins/PulsedLink/config.yml.

Entirely optional Your server works on the network without it. This only adds the trip back, and it changes nothing else about how your server runs.

If something isn't working

Players land in the lobby instead of your server.
Usually the server has not been approved yet — check your status on the connect page. If it says Live and players still reach the lobby, they are probably on a Minecraft version older than 1.20.5, which cannot be handed off automatically.

“Could not reach” when you press Verify.
We couldn't open a connection to the address and port you gave. Check the server is running, the port is right, and your host isn't firewalling it.

“Verification code was not in its MOTD”.
We reached your server but didn't see the code. Restart fully after editing server.properties, and make sure you edited the server you actually pointed us at.