Most Soulmask connection failures have a specific cause: the server has not finished starting, the client and server builds or Workshop mods differ, the wrong password is being used, or UDP traffic is blocked. A server missing from the browser is a different problem from a failed direct connection: Steam query traffic controls discovery, while the game port carries player connections. Work through those checks in that order before changing router settings. For self-hosted servers, use the configured UDP game and query ports, forward them to a stable private IP, and investigate CGNAT or ISP filtering when local players can join but outside players cannot. Lag that affects everyone usually points to host load, memory, storage, or the server process rather than an individual player’s PC.
What is the fastest way to diagnose Soulmask server lag or a lost connection?
Classify the failure before changing anything. Note who is affected, whether the server appears in the browser, whether direct connect works, and whether the issue started after an update. Those observations identify whether you should work on the client, server process, Steam discovery, or the network path.
| What you observe | Start here | Likely fault owner |
|---|---|---|
| One player is disconnected while others remain online | Compare that client’s build and mods; check its firewall, NAT path, and local network | Client or the player’s network |
| Every player drops at once | Inspect the server process, restart history, launch parameters, host firewall, and ports | Server or host network |
| The problem began after an update | Match client/server builds and Workshop mod sets before touching the router | Version or mod mismatch |
| Direct IP works but the server browser is empty | Check the Steam query port and discovery path | Query-port or listing path |
| Players on the same home network can join, but friends outside cannot | Test externally, then check forwarding, CGNAT, ISP filtering, and hairpin NAT | Router or ISP path |
How do I know whether the Soulmask server has finished starting?
A running process is not necessarily a ready server. Soulmask may still be loading the world and registering with Steam while a control panel shows a process. Wait several minutes, confirm the panel reports Online or the console shows completed startup, and test with one player before inviting the whole group.
Check startup before restarting
- Watch the hosting panel or console until world loading and Steam registration finish.
- Do not repeatedly stop and start a server that is still loading; each restart can extend recovery time.
- Join with one player first. Add the rest only after that test succeeds.
- If startup never completes, inspect the console for an error, confirm the configured ports, and check available memory and storage.
A panel that says “running” only confirms that a process exists. The readiness state and completed console output are the useful tests.
How do I fix a Soulmask “Connection to Host Lost” error?
First make the client and dedicated server identical in build, Workshop mods, and load order. Then verify the join password, confirm startup completed, and use direct connect with the game port. A misconfigured dedicated server is a common cause of this message, so a client-only reinstall should not be your first move.
Match the game build
Update the game client and the dedicated server to the same release. A player who updated automatically can be rejected by a server that is still on the previous build. If the server updated but a client did not, update that client before testing ports.
Match Workshop content and load order
Every player needs the same Workshop mod set and the same load order as the server. Remove or update a mod that exists on one side only. When possible, change one mod at a time so you know which change fixed the connection or caused the next error.
Use the correct password
Enter the join password exactly, including capitalization. Soulmask’s join password is separate from the GM or administrator password; an admin credential will not substitute for the player password. Restart the server after changing startup settings because those values are applied during restart.
How do I connect directly when my Soulmask server is not showing in the list?
Direct connect is the control test for a missing browser listing. In Soulmask, open Online Game, choose Connect to the server directly, enter the server address and configured game port, and provide the join password if one is set. Do not enter the Steam query port in the game-port field.
- Confirm the host’s public address, or use its private address when you are on the same LAN.
- Confirm the game port in the hosting panel, launch parameters, or instance configuration.
- Open Online Game and select Connect to the server directly.
- Enter the address and game port, then enter the join password with its exact capitalization.
- Test with one player while the server console is visible.
If direct connect succeeds while the browser remains empty, player traffic is reaching the server and discovery is the remaining problem. Focus on the query port and Steam listing path instead of changing the client’s firewall or reinstalling the game.
Which Soulmask ports must I open?
The commonly documented defaults are UDP 8777 for game traffic and UDP 27015 for Steam query and browser visibility. Your launch parameters or instance configuration are authoritative if custom ports are set. Forward the configured UDP game and query ports to the server’s stable private IP, and allow those same ports through the operating-system firewall.
| Traffic | Common default | What it does | Where to allow it |
|---|---|---|---|
| Game traffic | UDP 8777 | Carries the player connection and gameplay packets | Router port forward and host operating-system firewall |
| Steam query/browser | UDP 27015 | Lets the server answer discovery and appear in listings | Router port forward and host operating-system firewall |
Forward the ports safely
- Find the server machine’s current private IPv4 address in the router’s client list or network settings.
- Create UDP forwarding rules for the configured game and query ports, targeting that address.
- Create matching inbound UDP rules in the host operating system’s firewall.
- Save the router changes and restart the server if its panel or launch settings require it.
- Test from a network outside the home, such as a phone hotspot. Testing only from inside the same LAN can be misleading when the router lacks hairpin NAT.
Do not forward a port merely because it is a commonly listed default. If the instance uses a custom game or query port, forward the custom value shown by the server configuration.
Why can local players join while outside players time out?
When local players work and outside players fail, the game itself is usually healthy; the break is between the internet and the host. Confirm forwarding and firewall rules first, then investigate carrier-grade NAT (CGNAT), ISP inbound filtering, or a router that does not support reliable hairpin NAT.
Reserve the private address
Reserve the server’s address with DHCP reservation or the equivalent router setting. Without a reservation, a reboot can assign a different private address and leave the old port-forwarding rules pointing at the wrong machine.
Check for CGNAT or ISP filtering
Compare the router’s internet-facing address with the address shown by an independent internet connection. If they differ, the ISP may be placing the connection behind CGNAT, which prevents unsolicited inbound traffic from reaching your router. Some providers also filter inbound ports. Ask the ISP whether a public address or inbound UDP service is available, or move the server to a managed host that supports the required ports.
Account for hairpin NAT
Some routers cannot route a household device back to the same public address from inside the house. A failed test from your own LAN does not prove that outside players are blocked. Use an external network for the definitive test.
How do I reduce Soulmask server lag caused by the host?
Server-wide rubber-banding, delayed actions, and simultaneous disconnects usually indicate host load or a stalled server process. Check memory, storage, CPU activity, save timing, AI/NPC processing, and uptime before blaming an individual player’s connection.
Meet the documented capacity guidance
The GAMES.GG setup guide (2026) lists 16 GB RAM minimum, recommends 24 GB or more, and calls for 30 GB of free storage. It strongly prefers SSD storage for the dedicated server. These are capacity guidelines, not a guarantee of a particular player count or tick rate; mods, world size, and other applications can increase demand.
- Close unrelated applications on a self-hosted machine and watch memory while players are online.
- Keep at least the documented free storage available for the installation, updates, logs, and saves.
- Use an internal SSD when possible; slow storage can lengthen world loads and save operations.
- Lower the player limit or other server workload if lag correlates with high occupancy.
- Check whether pauses coincide with saves, heavy AI/NPC activity, or long uninterrupted uptime.
- Restart on a planned schedule only after confirming that uptime, not a configuration error, is the trigger.
Separate network lag from simulation lag
If the console shows warnings, the process consumes excessive memory, or all players freeze at once, investigate the host. If only one player rubber-bands while everyone else remains responsive, compare that player’s route, firewall, Wi-Fi, and client load instead.
What should I check on the client when only one player is affected?
Have the affected player update the client, match the server’s Workshop mods and load order, verify the join password, and retry direct connect. Then temporarily test without local security software that may block the game, and compare a wired or alternate network if available.
- Confirm the client build exactly matches the dedicated server.
- Verify every required Workshop mod is installed, current, and ordered identically.
- Check that the local firewall allows Soulmask and Steam network traffic.
- Test from another network to distinguish a home-router or ISP route from a game installation problem.
- Record whether the failure is a timeout, an immediate rejection, or a drop after joining; those symptoms point to different layers.
A Windows repair or driver-diagnostic utility can be considered only for a problem isolated to that client after these checks. It cannot repair server forwarding, NAT, or a host that has not completed startup.
How do I fix a Soulmask server that stops responding after an update?
Compare the update state of the client, dedicated server, and every Workshop mod before changing files. Update all three sides, restart the server, wait for completed startup, and test with one player. If the failure remains, inspect the console and WS.log for stack traces or a mod-loading error.
Use a controlled rollback of changes
- Shut down the server cleanly from its panel or console; do not close the window abruptly.
- Back up the complete save directory and configuration before removing or renaming anything.
- Disable one suspect mod at a time, restarting after each change.
- Test the unmodified or reduced-mod configuration with one player.
- Restore the last known-good mod set or save backup if the change does not help.
Changing several mods, deleting a save, and altering ports at once destroys the evidence needed to identify the fault and can make recovery harder.
How do I recover safely from a corrupted save or failed server start?
Protect the save before attempting repair. Make a complete copy of the save directory, configurations, and relevant logs. Then inspect WS.log, test with mods disabled one at a time, and restore a known-good backup when the log or symptoms point to save corruption.
Safe recovery sequence
- Stop the server cleanly and copy the entire save directory to separate storage.
- Preserve the current log files, including
WS.log, so the failure can be reviewed. - Check the log for stack traces, failed asset loads, or mod-related errors.
- Rename a suspected folder rather than deleting it, retaining the backup for reversal.
- Start with the minimum required configuration and test the world.
- If the world still fails, restore a known-good save backup and reapply changes gradually.
Never treat deleting a save or mod directory as a first-line connection fix. A network timeout does not prove that world data is corrupt.
Should I use a managed Soulmask server instead of hosting at home?
Managed hosting is a practical alternative when CGNAT, ISP filtering, unstable home internet, or recurring maintenance prevents reliable outside access. It does not remove the need to match builds, mods, and passwords, but it can provide a reachable network endpoint and offload port forwarding and hardware maintenance.
Home hosting fits when
- Your ISP provides a reachable public address and permits inbound UDP.
- You can reserve a stable private IP and configure both firewall and router rules.
- The machine has at least the documented memory and storage headroom.
- You are comfortable backing up saves, reading logs, and restarting after configuration changes.
Managed hosting fits when
- CGNAT or ISP policy blocks inbound connections.
- The home router cannot provide dependable forwarding or hairpin behavior.
- You need the server available without leaving a personal PC running.
- You prefer provider-managed updates, storage, and network exposure.
Before choosing a provider, verify current Soulmask availability, supported UDP ports, mod and save access, backup controls, region, pricing, and cancellation terms. Those details can change independently of the game.
What should I do when the browser listing is wrong but direct connect works?
Treat this as a discovery problem, not a gameplay connection failure. Confirm that the query port is the configured value, forward it as UDP to the stable private IP, allow it through the host firewall, and restart if the server applies query settings only at launch.
- Use the game port for direct connect and the query port for browser visibility.
- Check that another service is not occupying the query port.
- Verify the server completed Steam registration after startup.
- Allow time for the listing to update after a restart or network change.
- Continue using direct connect as a workaround while discovery is repaired.
How can I tell whether a timeout is caused by the server or the network?
Use controlled comparisons rather than repeated guesses. A successful local join but failed external join indicates routing or ISP exposure. A failed local and external join points toward startup, credentials, versions, mods, the host firewall, or the server process.
| Test | Result | Next action |
|---|---|---|
| One local player joins | Server process and local path are functioning | Test an external network and inspect public routing |
| No local player joins | Failure is before internet routing | Check startup, build, mods, password, firewall, and game port |
| Direct connect succeeds | Game traffic reaches the server | Repair query-port forwarding or browser discovery |
| All players disconnect together | Shared server or host event is likely | Inspect process restarts, load, logs, and host ports |
| Only one player disconnects | Per-client path is more likely | Compare that client’s network, firewall, build, and mods |
What is the correct order for a complete Soulmask troubleshooting pass?
Follow this order so reversible, low-risk checks happen before router edits or save changes.
- Classify the symptom: one player, everyone, browser-only, local-only, or update-related.
- Wait for startup to finish and confirm the server reports Online or completed console startup.
- Match client and server builds.
- Match Workshop mods and load order.
- Verify the separate join password and restart after changing startup values.
- Use direct connect with the configured game port.
- Check UDP game and query forwarding and matching host-firewall rules.
- Reserve the server’s private IP and test from an external network.
- Investigate CGNAT, ISP filtering, or hairpin NAT if local and external results differ.
- Reduce player limits or workload and check RAM, storage, SSD use, saves, AI/NPC processing, and uptime for host-side lag.
- Back up saves, inspect
WS.log, disable mods one at a time, and restore a known-good backup only when evidence points to data corruption.
This sequence also keeps interventions reversible. Port changes and file renames should come after version, startup, credential, and direct-connect checks; deleting data should be the final recovery step, never the first.
Frequently Asked Questions
Can I join a Soulmask server without it appearing in the server browser?
Yes. Use Online Game, select Connect to the server directly, and enter the host address, configured game port, and join password. A successful direct connection confirms the gameplay path even if Steam discovery is still unavailable.
Does changing the GM password fix a player connection timeout?
No. Players use the join password, while the GM/admin password is a separate credential. Re-enter the join password exactly, including capitalization, and restart after changing startup settings.
Why does Soulmask lag only during saves or heavy activity?
Save operations and AI/NPC processing can create short host-side stalls, especially when memory is tight or storage is slow. Monitor the server during those events and use SSD storage, adequate free space, and lower workload where necessary.
What should I preserve before removing a Soulmask mod?
Copy the complete save directory and configuration, and retain the current logs. Disable or rename one mod at a time so you can reverse the change and identify whether it caused the failure.
How can I test whether my ISP uses CGNAT?
Compare the internet-facing address shown by your router with the address observed from a separate internet connection. If they differ, your router may be behind carrier-grade NAT, which commonly prevents inbound server connections.