Brickadia Server Not Showing Up or Friends Can't Join (Fixes)

When a Brickadia server does not show in Join Game or friends time out connecting, the cause is nearly always one of five things: the server never started because the hosting token is missing or wrong, UDP 7777 is not reachable from the internet, the server is on an older build than the players, public listing is switched off, or the host CPU lacks AVX2 so the server crashes on launch. Work through them in that order and test with Manual Connect after each change.

First, find out whether the server is running at all

Look at the server console or log before touching the router. A healthy start ends with the server posting itself to Brickadia's list. On a typical Linux setup you will see a line like:

Posting server.

If you never get that far, nobody can join no matter what your ports look like. Skip to the token and CPU sections below. If you do see it, the server is up and the problem is between the server and your players.

Fix 1: The hosting token is missing, expired or mangled

Brickadia will not run a dedicated server without a hosting token from the owner's account. Symptoms: the server exits within seconds, or loops on start, and never posts itself.

1. Go to your account page on brickadia.com, section Dedicated Server Hosting.
2. Create a new token and copy all of it. It is a long Base64 string that ends in ==.
3. Paste it into the start line as -token=... (or the token field in your host's panel) with no spaces or line breaks around it.
4. Restart and watch for the post line.

If you deleted a token on the website, every server using it stops authenticating. Each server should get a token you know is live.

Fix 2: UDP 7777 is not reachable

The server can run perfectly and still be invisible from outside your house. Brickadia uses UDP 7777 by default (or whatever you passed in -port=).

• Forward UDP 7777, not only TCP, on your router to the server machine's local IP. Our port forwarding guide has the steps, with router specific guides for Xfinity and Spectrum.
• Allow the port in the OS firewall. On Windows, let the Brickadia server executable through Windows Defender Firewall for both private and public networks. On Linux: sudo ufw allow 7777/udp.
• Check for CGNAT. If your router's WAN address does not match the address shown on a "what is my IP" site, your ISP shares one public IP across many customers and port forwarding cannot work.

A quick sanity test: if you can join through Manual Connect with the server's LAN address (like 192.168.1.20:7777) but friends cannot join with your public IP, the server is fine and the network is the problem.

The host can't join their own server by public IP

Many home routers do not support NAT loopback, so the person running the server cannot connect to their own public address from inside the same network. Join with the LAN address instead. Friends outside your house use the public one.

Fix 3: Version mismatch after an update

Brickadia is in early access and patches often. When the game updates on Steam, players get the new build at once, but a dedicated server installed with SteamCMD stays on the old one until you update it. Players on a different build cannot join.

Update the server:

steamcmd +force_install_dir /path/to/server +login anonymous +app_update 3017590 validate +quit

Then restart. Make it a habit to save the world (BR.World.SaveAs name) and copy your .brdb files before each update.

Fix 4: The server is unlisted or password protected

If the server is running and reachable by Manual Connect but missing from the list, check the server settings in game (press Esc on the server, then the server settings). A server set not to list publicly will only be reachable by address. Search for the exact server name too: the list can be long, and filters for full or password servers can hide yours.

If friends see the server but get bounced, ask what they were told. A password prompt means they need the password; a full server means raising the player limit in the same menu.

Fix 5: Server crashes on launch on some machines

The Brickadia server needs a 64 bit x86 CPU with AVX and AVX2. Old Xeons, some cheap VPS plans with masked CPU flags, and every ARM machine (Raspberry Pi, Oracle Ampere, Apple Silicon under Linux) fail here. On Linux, check the flags:

grep -o -w 'avx2' /proc/cpuinfo | head -1

No output means the CPU cannot run the server. Moving the server is the only fix.

Fix 6: Joined, but the world is empty

Not strictly a connection problem, but it looks like one: friends join a blank plate and assume they are on the wrong server. The server started without loading your world. Load it with BR.World.Load worldname and add -world worldname to the start line so it loads every time. The Brickadia hosting guide explains saves in detail.

Quick checklist

Skip the network part entirely

Most of these fixes exist because the server is running on a home connection. A Brickadia server on GamezServers has its own address, so there is no router or CGNAT to fight, and the Steam Auto-Updates setting keeps the server on the current build each time it starts. You paste your token into the panel, set the world to load, and watch the live console for the post line. If something still looks wrong, support is at support@gamezservers.com.

FAQ

How long does a new Brickadia server take to appear in the list?

Usually shortly after the console shows it posting the server. If it is still missing after a few minutes, try Manual Connect with the address to rule out the list itself.

What address do friends type in Manual Connect?

Your public IP and port, for example 203.0.113.10:7777. Leave the port off only if you are on the default.

Do Brickadia servers need TCP ports?

Gameplay uses UDP. Forward UDP 7777, or the port you set with -port=.

Can two Brickadia servers run on one machine?

Yes. Give each its own port, such as 7777 and 7778, and forward both ports.