How to Fix a Wreckfest Server Missing From the Browser

Wreckfest servers go missing for a small number of reasons, and the first one accounts for most tickets.

1. The ports in the config do not match

Open server_config.cfg in Files and check:

steam_port=
game_port=
query_port=

All three must match the ports allocated to your server, shown on the server overview. Wreckfest starts happily with wrong values and is simply unreachable, which looks like a much bigger problem than it is.

2. The browser filters

• Community hosted servers are in the custom or community list, not in quick match.
• Clear the search box and untick the filters that hide password protected and empty servers.
• Add the server to Steam favourites using the query port, which bypasses the in-game search entirely.

3. The track name is wrong

The track setting expects an internal name, not the name shown in game. A track the server cannot resolve stops it reaching a playable state. Run tracks in the panel console to print the valid names for your build, and copy one exactly.

4. Read the console

Open Console in the panel and read from the top of the last start. Wreckfest reports settings it did not accept, by name, and the track it loaded.

5. Startup parameters overriding the config

Wreckfest accepts settings on the launch line, and those win over the config file. If a setting refuses to change no matter what you do to server_config.cfg, check the parameters on your server's Startup Settings page, reachable from the server overview, for the same setting.

6. After a game update

A server on an old build is invisible to updated clients. Restart it so it pulls the new version.

7. Give it a distinctive name

An empty or default server_name makes the server almost impossible to find by search even when it is listed correctly. The limit is 63 characters.

What to send support

Open a ticket with your IP, the three port values from your config, and the first hundred lines of console output from a fresh start.