Menu
  Log out
 

Soulmask Server Not Showing - Soulmask Wiki

Soulmask Guide • Updated Jan 16, 2026

Soulmask Server Not Showing in Browser

If your Soulmask server is invisible or players cannot find it in the list, the issue is usually a port, Steam API, or version mismatch problem.

Quick Workaround: Servers take 5-15 minutes to appear in the public list. Use Direct Connect with IP:8777 to join immediately while waiting.

Quick Diagnostic Table

Check Why It Fails Fix
Game Port 8777 (TCP+UDP) Port not forwarded or blocked Open TCP+UDP 8777 and forward to server IP
Query Port 27015 (UDP) Browser query fails Open UDP 27015 for server listing
Steam installed on server "Steam API failed to initialize" Install Steam client on the dedicated server machine
Version match Client and server on different versions Update both - check Steam for client, SteamCMD for server
Port conflict Another game using 8777 or 27015 Check for ARK, Palworld, or other servers on same ports

Step-by-Step Fix

  1. Install Steam on the server. Unlike most games, Soulmask requires Steam client installed (not just SteamCMD) to initialize the API.
  2. Open required ports. Forward TCP+UDP 8777 and UDP 27015. Create separate firewall rules for each.
  3. Check for port conflicts. Run netstat -tulpn | grep -E "8777|27015" to check if ports are in use.
  4. Update server and client. Version mismatches cause connection failures. Update SteamCMD server after every game patch.
  5. Wait or use Direct Connect. Servers take 5-15 minutes to appear. Use Direct Connect with IP:8777 to join immediately.

"Steam API Failed to Initialize" Fix

Important: If you see "Steam Dedicated Server API failed to initialize", you must install the Steam client on the server machine. This is unusual for dedicated servers but required for Soulmask.

Config Example

[ServerSettings]
ServerName = "Tribal Adventures Server"
Port = 8777
QueryPort = 27015
BindIP = "0.0.0.0"

Firewall Configuration

# Windows PowerShell (Run as Administrator)
New-NetFirewallRule -DisplayName "Soulmask Game" -Direction Inbound -LocalPort 8777 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Soulmask Game UDP" -Direction Inbound -LocalPort 8777 -Protocol UDP -Action Allow
New-NetFirewallRule -DisplayName "Soulmask Query" -Direction Inbound -LocalPort 27015 -Protocol UDP -Action Allow

# Also create outbound rules
New-NetFirewallRule -DisplayName "Soulmask Out" -Direction Outbound -LocalPort 8777,27015 -Protocol TCP -Action Allow
New-NetFirewallRule -DisplayName "Soulmask Out UDP" -Direction Outbound -LocalPort 8777,27015 -Protocol UDP -Action Allow

Version Mismatch Issues

Known Issue: Soulmask updates frequently, and SteamCMD sometimes lags behind. If you see "password mismatch" or loop back to main menu after connecting:

  • Check client version in Steam (right-click → Properties → Updates)
  • Update server: steamcmd +login anonymous +app_update 2978680 validate +quit
  • Restart server multiple times if needed - some updates require 3-5 restarts
  • Join the Soulmask Discord private-server channel for admin support

Bug: Some players report they can't see their own server, but friends can. Use Direct Connect as a workaround - this appears to be a client bug.

Keep tribes connected. Host your Soulmask server with Supercraft for managed ports and rapid restarts.

← Back to Soulmask Guides
Top