Wreckfest 2 Server Not Showing or Can't Connect (Fixes)

Q: What port does a Wreckfest 2 server need?

UDP 30100 by default, or whatever "game port" is set to in serverconfig.scnf.

When a Wreckfest 2 dedicated server is missing from the browser or drivers cannot connect, the most common cause by far is an Early Access patch: players updated through Steam and the server did not, so update the server and restart. After that, check that UDP 30100 (the "game port" in server_config.scnf) is open, that the config files are valid JSON, that the server was started with an existing --save-dir, and that the password matches. Connect to Address in the game skips the browser if you need to test directly.

Cause 1: An Early Access patch

Wreckfest 2 has been in Early Access since March 2025 and gets frequent updates. Every update moves players to a new build straight away. A server installed with SteamCMD keeps running the old build until you update it, and mismatched builds cannot play together.

steamcmd +force_install_dir C:\WF2Server +login anonymous +app_update 3519390 validate +quit

Then restart the server. If the server suddenly vanished on an evening it worked the day before, check the game's Steam news for a patch before anything else.

Patches can also change config formats. If the updated server will not start, compare your files with the fresh defaults it writes, and restore from a backup if needed.

Wreckfest 2, a demolition racing game

Cause 2: Port not reachable

The server listens on the "game port" from server_config.scnf, UDP 30100 by default.

Forward that port as UDP to the server PC's local IP.
Allow Wreckfest2.exe through Windows Firewall, and through your provider's firewall if it is a rented machine.
Give the server PC a fixed local IP (a DHCP reservation), or the forward breaks the next time the router hands out addresses.
Compare your router's WAN IP with your public IP. If they differ, you are behind CGNAT and no forward will work.

If you run two servers, each needs its own "game port" and its own forwarding rule. Our port forwarding guide covers router screens.

Cause 3: Broken JSON

All of the server's files, server_config.scnf, .becl event loops, server_cup_config.ccnl and server_privilege.sprv, are JSON. A single missing or extra comma can make the server reject the file or fail to start properly. Symptoms include the server running with default settings, ignoring your track rotation, or not showing your name.

Paste each file you changed into a JSON validator, fix what it reports, and restart. Edit in a plain text editor, since word processors swap straight quotes for curly ones that JSON does not accept. The Wreckfest 2 config files guide shows what each file should look like.

Cause 4: Wrong or missing save folder

The server reads its config from the folder passed with --save-dir, and that folder must exist before launch. If it does not, or the path is mistyped, the server falls back to %LocalAppData%\Wreckfest 2\ and uses a different config than the one you edited. You then see the wrong name in the browser, or no password where you set one. Check the launch line and the path.

Cause 5: Browser search and filters

Search for the exact "name" in your config.
Clear filters for full, empty and passworded servers.
Use Connect to Address on the Multiplayer Server Browser screen with your IP and port. If that works, the server is fine and the issue is the listing or a filter.

Cause 6: Joined, then kicked or rejected

What happens	Likely cause	Fix
Rejected at the password prompt	Wrong password	Check `"password"`, max 31 characters
Removed shortly after joining	Ban or suspend in `server_privilege.sprv`	Lift it from the server console
Event full	Bots taking slots	Lower bots in the event's rules; 24 total
Stuck after track change	Admin stopped the rotation	Restart or reload the event loop

The automatic report limits in server_config.scnf can suspend a player after enough reports from others. On a server full of friends trading paint, that can catch someone by surprise. Check the ban durations and limits if regulars keep getting removed.

One driver cannot join

If everyone else gets in, the problem is on that driver's side: they may not have updated yet, may be on a beta branch, or have a firewall or VPN blocking the connection. Ask them to restart Steam so the latest patch installs, and verify the game files.

Checklist

Server updated to the current build and restarted.
Log shows it started without config errors.
UDP game port forwarded and allowed.
--save-dir exists and holds the files you edited.
Connect to Address works from outside your network.

Wreckfest 2 gameplay screenshot

A server that keeps up with patches

A GamezServers Wreckfest 2 server runs with Auto Update on, so a restart from the panel pulls each Early Access patch, and it has its own address with the port open, so causes 1, 2 and 4 are handled. Server Name and Password come from the panel and are written into server_config.scnf on every start, the live console shows the server starting, and the save folder is in the file manager for fixing JSON. Install details are in how to host a Wreckfest 2 server.

FAQ

Why can't I connect to my Wreckfest 2 server after an update?

The server is still on the old build. Update it with SteamCMD (app 3519390) and restart.

What port does a Wreckfest 2 server need?

UDP 30100 by default, or whatever "game port" is set to in server_config.scnf.

How do I join a Wreckfest 2 server by IP?

In the Multiplayer Server Browser, click Connect to Address and enter the IP and port.

Why does my Wreckfest 2 server ignore my settings?

The JSON has an error, or the server loaded a different save folder than the one you edited.