Soulmask: Can't connect to server
Fix a Soulmask connection by matching the client and server build, using the UDP game port from Overview, checking startup, and entering the separate join password.
If Soulmask cannot connect, work through these checks in order. Keep the tribe save in place. A common failure is a client that updated before the dedicated server.
Stop as soon as one fix works. If you are helping somebody else, test with one player before asking the whole group to retry.
Soulmask 1.0 shipped in April 2026. The official 1.0 announcement and Steam store page show the current full-release status.
1. Match the client and server build
The client and dedicated server must run the same Soulmask build.
Update the player's game
Close Soulmask, let Steam finish the update, and stay off a beta branch the server is not on.
Update the dedicated server
Stop the server. On berrybyte, Auto Update pulls the current dedicated build on the next start. Restart once after the patch is live.
Compare versions
The version on the main menu must match the version in the server log.
For managed updates, rent a Soulmask server that updates on start.
2. Wait until Console finishes the update
A Soulmask process can show as running while it is still installing a dedicated build.
Confirm Overview shows running
On berrybyte the process must be running, not still installing.
Read Console
Wait until startup finishes. The first boot after a patch can take several minutes.
Retry one client
Test with one tribe member before inviting everyone.
3. Use Connect to the server directly
The reliable test is Online Game → Connect to the server directly.
Copy Server address
On berrybyte, copy Server address from Overview.
Split host and port
Launch Soulmask, open Online Game, press Connect to the server directly, and put the part before the colon in the IP field and the part after it in the Port field.
Paste the password if one is set
Enter the server's join password. Self-hosted servers set
this password with -PSW.
See How to join a Soulmask server.
4. Check both UDP ports
Soulmask gives the two public UDP ports different jobs. -Port
sets the game port, which defaults to 8777. Players type this
port into direct connect. -QueryPort sets the Steam query port,
which defaults to 27015 and publishes the server to Steam's
browser.
Use the berrybyte game address
On berrybyte, copy the direct-connect address from Overview. The port after the colon is the allocated game port.
Open both ports when self-hosting
Allow the configured UDP game port through the firewall and router. Public listing also requires the configured UDP Steam query port.
berrybyte opens the allocated port for you. Self-hosters who are fighting NAT can rent a Soulmask server that already has it reachable.
The current
Soulmask dedicated-server reference
documents -Port, -QueryPort, and the defaults above.
5. Use the join password
A passworded tribe server rejects a blank or mistyped string.
Soulmask keeps the player password and GM credential separate:
-PSW controls joining, while -adminpsw unlocks GM access.
Read the join password
On berrybyte, open Settings → Game Settings.
Send the exact string, or clear it
Check capitalisation and characters that chat apps rewrite. Clear it for a public test, then restart.
6. Confirm the dedicated server and save
A client-hosted listen server is not the dedicated process. An old Steam invite to somebody's PC will not reach the berrybyte box.
Join the dedicated address only
Use Overview, not a leftover invite from last session's listen host.
Upload the tribe save onto the dedicated server
If you migrated, wait until Console opens that save before testing again.
For self-hosting, SteamCMD installs the dedicated server with app
ID 3017310. The playable client uses app ID 2646460. Keep the
GM password private because players only need the -PSW value.
If none of the six fixes worked
Confirm Console reached a ready state. Then check the leftover causes:
- Check steamstat.us.
- Check berrybytestatus.com.
- Compare the build shown by the client with the dedicated-server log again.
Frequently asked questions
Why can't I connect to a Soulmask server?
Match the client and dedicated-server build first. If the versions match, wait until Console finishes startup, join through Online Game → Connect to the server directly, and enter the UDP game port shown on berrybyte Overview.
How do I join a Soulmask server by IP?
Launch Soulmask, choose Online Game, then Connect to the server directly. Split Server address at the colon. IP goes in the address field, port in the port field. Paste the password if the host set one.
Why does Soulmask say failed to connect?
The dedicated server may be offline or still installing an update. Copy Server address from Overview again and confirm that its port is the game port used for direct connect.
What port does a Soulmask dedicated server use?
Soulmask's default UDP game port is 8777 and is set with -Port. Direct connect uses that game port. UDP 27015 is the default Steam query port set with -QueryPort and belongs to server discovery.
Why is the Soulmask browser empty?
A self-hosted public server needs its UDP game port and Steam query port reachable. Direct connect can still work through the game address while Steam discovery is unavailable.