How to Fix Enshrouded Server Lag and Connection Problems

Most Enshrouded connection problems have a specific cause: the session is using the wrong hosting model, the dedicated server has not finished starting, the server is hidden by a browser filter, its query port is unreachable, the client is losing packets, or the host is overloaded. Identify whether you are playing peer-to-peer or on a dedicated server first. Then verify the server’s online log state, update both sides, check the queryPort (default 15637), confirm IPv4 forwarding and firewall rules, test packet loss, and reduce player slots or move to stronger hardware if the hosting-load indicator is yellow or red.

What is causing your Enshrouded lag or connection failure?

“Lag” covers several different failures. Rubberbanding, delayed interaction and players being kicked during play usually indicate packet loss, an overloaded host, or a weak network path. A server that never appears in the browser, cannot be joined, or vanishes after an update is more often a startup, visibility, version, port or address-family problem. The quickest fix depends on which of those symptoms you have.

• Not listed: check dedicated-server filters, Steam favorites, startup completion, the configured query port and IPv4 reachability.
• Join attempt fails: inspect the server log for a session failure and verify that the client and server are on compatible versions.
• Rubberbanding during play: measure packet loss, switch from Wi-Fi to wired networking, and check host load and available capacity.
• Everyone disconnects: investigate the server process, host resources, router or ISP path, and recent updates.
• Only one player disconnects: test that player’s local network and Steam connection before changing server settings.

Use the sections below in that order rather than changing several settings at once. Reversible checks such as filters, logs, cache clearing and packet-loss tests should come before replacing hardware or changing providers.

How do I tell whether I am using peer-to-peer or a dedicated server?

Peer-to-peer sessions run from one player’s computer and internet connection. A dedicated server runs as its own process with a configuration file, query port, logs and defined resource limits. The troubleshooting steps are different, so do not apply a peer-to-peer privacy fix to a dedicated installation.

Peer-to-peer sessions

The player who starts the session is the host. That computer supplies the CPU, memory and network connection for the world, and Steam privacy settings can affect whether friends can discover or join it. If the host closes the game, loses connectivity or becomes overloaded, everybody can experience a delay or disconnect.

For a peer-to-peer session, make the host’s Steam profile public and try inviting through the Steam friends list. Those are supported workarounds when the session cannot be found normally. A public profile does not repair packet loss or insufficient hardware; it only removes a discovery and permission obstacle.

Dedicated servers

A dedicated server continues independently of an individual player’s game session. It has an enshrouded_server.log file, a server configuration (including queryPort and slotCount), a firewall and usually a router rule forwarding traffic to the host machine. A rented server may also have a provider control panel and a provider-managed update schedule.

If you are unsure, look for the dedicated-server process and its log on the machine that hosts the world. If there is no such process or log, start with peer-to-peer checks instead of editing dedicated-server ports.

How can I confirm that a dedicated server finished starting?

A process that is running is not necessarily ready to accept players. Open the console output or enshrouded_server.log and wait for the host-online state before testing the connection.

1. Stop making join attempts while the process is still starting; repeated attempts obscure the useful log sequence.
2. Search the current log for [Session] 'HostOnline' (up)!.
3. Also look for [Session] finished transition from 'Lobby' to 'Host_Online' (current='Host_Online')!.
4. If both messages are absent, investigate startup errors, an incomplete update, configuration syntax or a process that has exited. Router changes cannot make a server joinable before it reaches the host-online state.
5. If a join fails, check whether a Session failed line appears immediately before Removed Peer. That sequence gives you a precise failure event to correlate with the client’s attempt and its timestamp.

Keep the original log rather than deleting it after a failed attempt. The exact time and the lines around the failure are more useful to a host or support team than a description such as “it just disconnected.”

Why is my dedicated server missing from the Enshrouded browser?

The server list can hide a healthy server. Enable the dedicated-server view and remove filters that exclude the server before changing networking settings.

Check the in-game Join filters

1. Open Enshrouded’s Join screen.
2. Enable Show dedicated server.
3. Review the filters for password-protected servers, empty servers, friends-only results and free slots. Temporarily broaden each one so a server with a password, no current players, no friends online or no open slot is not filtered out.
4. Refresh the list after the server has reached the host-online log state.

A slow or incomplete browser result does not prove that the server is offline. The list is a discovery tool, while a direct Steam favorite gives you a second way to locate a known address.

Use Steam’s Game Servers favorites

In Steam, open View > Game Servers, select Favorites, and add the server using its public IP address and query port. For a default configuration, that query port is 15637. Save the entry as a favorite and use it to test whether the address is reachable even when the in-game list is incomplete.

Enter the public address from outside the host’s local network when possible. A private LAN address is not a substitute for the public address that remote players need, and a favorite made with the wrong port will appear to be a dead server.

Which ports, firewall rules and address family does Enshrouded need?

Keen Games documents queryPort: 15637 as the default and states that Steam’s required ports are also needed. Enshrouded multiplayer uses IPv4. The configured query port, host firewall rule and router forwarding rule must therefore agree, and forwarding must target the current local address of the server machine.

Verify the query port

• Open the dedicated-server configuration and note the value assigned to queryPort.
• If it is unchanged, use 15637 in the Steam favorite and in the network rules.
• If it has been changed, use the new value everywhere; a mismatch makes discovery and direct connection fail even when the server process is healthy.

Check forwarding and firewall scope

1. Give the host machine a stable local IPv4 address, or create a DHCP reservation so the address does not change.
2. Forward the configured query port from the router to that exact local IPv4 address. Do not forward it to an old address left by a previous DHCP lease.
3. Allow the dedicated-server executable through the host operating system’s firewall on the required network profile.
4. Confirm that the router rule and firewall rule use the same protocol and port values expected by the server and Steam. Keen Games also notes that Steam’s required ports must be available; opening only the query port is not a complete substitute for those requirements.
5. Retest from a different network, such as a friend’s connection or a phone hotspot, because some routers do not correctly test their own public address from inside the same LAN.

Because the game uses IPv4, an IPv6-only route or an address copied from an IPv6 display will not solve a reachability problem. Use the host’s public IPv4 address for remote testing.

How do I fix Enshrouded rubberbanding and packet loss?

Rubberbanding is usually a delivery problem rather than a browser-list problem. First determine whether packets are being lost between one player and the host, or whether the host itself is too busy to process the world.

Test the client’s network path

1. Play one session while watching for packet loss or a network-quality warning. Note whether every player sees the delay or only one connection does.
2. If the affected machine is on Wi-Fi and shows high packet loss, switch to a wired Ethernet connection. Keen Games specifically recommends a cable connection in that situation.
3. Clear Steam’s download cache, then restart Steam and the game. A download or corrupted cache state can interfere with a clean connection test.
4. Open Windows Command Prompt and run ipconfig /flushdns. This clears local DNS resolver entries without changing the server configuration.
5. If name resolution remains suspect, test Google DNS at 8.8.8.8 and 8.8.4.4. Change DNS only long enough to compare the result, and restore the previous setting if it does not help.

These checks are most useful when one player is affected or when the problem changes with Wi-Fi signal quality. If every player rubberbands at the same moment, continue with the host-load and server-process checks instead of repeatedly changing each client’s DNS.

Separate packet loss from server load

A stable ping does not guarantee that the host can simulate the world on time. The in-game hosting-load indicator is a practical signal: yellow or red means the host is under significant pressure. In that state, reduce the number of players or move the server to a stronger machine. Host hardware and internet quality both affect multiplayer stability.

How do I reduce dedicated-server load?

Lowering player capacity is the least disruptive load reduction. The dedicated-server slotCount must be a number from 1 through 16, and Keen Games states that each additional slot increases the server’s performance impact.

Reduce slots safely

1. Stop the dedicated-server process cleanly.
2. Back up the configuration and world save.
3. Set slotCount to a value between 1 and 16 that matches the number of players you actually need.
4. Save the file without changing unrelated syntax.
5. Start the server and wait for the two host-online log messages before inviting players.
6. Watch the hosting-load indicator during a normal play session. If it remains yellow or becomes red, reduce the load again or migrate the process to stronger hardware.

Reducing slots limits simultaneous demand; it does not make an underpowered machine faster at a fixed player count. If the world still lags with a small group, CPU performance, available memory, storage pressure or the host’s internet connection may be the limiting factor.

When is moving to another machine justified?

Move the server when the load indicator stays yellow or red after reducing slots, when the host is also running demanding applications, or when the host’s upload connection cannot remain stable. A stronger machine and a better-connected location address different bottlenecks: more CPU and memory help simulation, while a cleaner network path helps delivery. Change one variable at a time so you can tell which intervention fixed the lag.

How much memory and storage does an Enshrouded dedicated server need?

Keen Games’ 2025 planning figures provide a useful capacity check, but they are not guarantees for every world or release. The measurements are physical RAM guidance, not a promise that a virtual-machine allocation with the same number will behave identically.

Resource	Planning figure	How to use it
Physical RAM at idle	About 4.4 GB	Reserve this before counting player overhead.
Additional RAM per player	Up to 100 MB	Multiply by the expected simultaneous player count when sizing headroom.
Total physical RAM	No more than 6 GB	Keen Games’ stated total guidance; actual behavior can vary by world and release.
Free disk space	30 GB recommended	Leave room for the server, updates, logs and saves.
Save-file size	1 MB to 100 MB	Worlds vary; do not assume every save uses the same space.
World-save interval	Every five minutes	Storage must remain writable during recurring save generation.

Check free disk space before troubleshooting a crash or a server that repeatedly stops during saving. A nearly full drive can also prevent updates and produce confusing startup symptoms. Keep backups outside the live save directory before editing configuration or moving hosts.

Could a game or server version mismatch be causing the failure?

Yes. Update the game client and the dedicated server together, then restart the server before testing. A client that has updated while the server remains on an older build can fail to join even when ports and filters are correct.

Keen Games’ Hotfix #11, dated March 28, 2024, fixed an issue that prevented connection to dedicated servers in some cases. Self-hosters had to download the server update. Players renting a server generally had to wait for the provider to deploy the update or restart the server through its control panel. The hotfix is historical evidence that a connection failure can be a server-side software defect rather than a local router problem; check the current game and server build before editing network rules.

1. Close the game and stop the dedicated-server process.
2. Update the client through Steam.
3. Update the self-hosted server files, or verify that the rental provider reports the current version.
4. Start the server and wait for the host-online messages.
5. Test with one player before opening the server to the full group.

What should I do when only one player cannot connect?

The scope of the failure is a valuable diagnostic. If other players can join and play normally, avoid changing the server’s ports or configuration first. Compare the affected player’s network path, Steam state, game version and filter settings with a player who can connect.

• Confirm the affected client is updated to the same game version as the server and other players.
• Have that player clear Steam’s download cache and run ipconfig /flushdns.
• Test a wired connection if Wi-Fi shows packet loss.
• Try joining through the Steam friends invitation for a peer-to-peer session, or through the known Steam favorite for a dedicated server.
• Record the exact time of the failed attempt and ask the server owner to check for Session failed followed by Removed Peer.

If every player fails at the same time, return to server startup, version, port, firewall and host-capacity checks. A client-only fix cannot repair a server process that never reached Host_Online.

What is the fastest diagnostic order for a disappearing or laggy server?

Use this sequence to avoid making several unverified changes at once.

1. Classify the host: identify peer-to-peer versus dedicated.
2. Check versions: update the client and dedicated server together.
3. Confirm startup: find both host-online messages in the console or enshrouded_server.log.
4. Broaden discovery: enable Show dedicated server and review password, empty-server, friends and free-slot filters.
5. Use a direct favorite: add the public IPv4 address and the configured query port in Steam’s Game Servers > Favorites.
6. Verify network rules: match queryPort, firewall permissions, router forwarding and the host’s current local IPv4 address; include Steam’s required ports.
7. Test the path: switch from Wi-Fi to Ethernet when packet loss is high, clear Steam’s download cache, flush DNS and compare with Google DNS if necessary.
8. Check load: if the hosting indicator is yellow or red, lower slotCount or move to stronger hardware.
9. Check capacity: compare physical memory and free disk space with the planning figures, and confirm that saves can be written.
10. Capture evidence: save the log, the exact failure time, the player count, the host model and the changes already tested before restarting again or contacting support.

When should I stop changing settings and contact support?

Contact support or your hosting provider after the server reaches Host_Online, both sides are updated, filters are clear, the query port and IPv4 forwarding are correct, and the failure still reproduces. Include the exact UTC or local timestamp with its time zone, the server region, the number of players affected, whether the problem is listing, joining or in-game lag, and the relevant log excerpt.

For a rented server, ask the provider to confirm its deployment version, public IPv4 address, query-port mapping and restart history. For a self-hosted server, include the configuration values without posting passwords or private keys. Keep the original log around the failure; do not overwrite it with a later successful launch.

How do I choose between a quick client fix, a host change and a server migration?

Observed pattern	First action	Escalation if it persists
Server absent from the list, but host log says online	Enable dedicated-server visibility and remove restrictive filters	Add the public IPv4 address and query port to Steam favorites
Join fails for everyone	Check versions, startup messages, query port, firewall and IPv4 forwarding	Preserve the log sequence and contact the host or support
Rubberbanding on Wi-Fi for one player	Switch that player to Ethernet and test packet loss	Compare another network before altering the server
Rubberbanding for everyone with yellow or red load indicator	Reduce slotCount	Move to stronger hardware or a better-connected host
Server stops during saves or updates	Check free disk space and writable storage	Back up the world and investigate the process log

The most reversible action in each row comes first. A migration is justified only after the evidence points to host capacity, uptime or network quality rather than a filter, version or configuration error.

Frequently Asked Questions

Can I change Enshrouded’s query port from 15637?

You can use a different configured query port, but every dependent setting must change with it. Update the host firewall, router forwarding and Steam favorite to the same value, then restart and wait for the host-online log messages before testing.

Why does a server show online but reject a join immediately?

An online process can still reject a session because of a version mismatch, an address or port mismatch, or a failed session handoff. Compare the client and server builds and inspect the log lines immediately around the join attempt rather than relying on the browser status alone.

Does lowering slotCount delete players or world progress?

Changing slot capacity limits future simultaneous connections; it is separate from the world-save data. Stop the process cleanly and keep a configuration and save backup before editing the value so you can restore the previous setting if needed.

What information should I send a hosting provider for a disconnect?

Send the precise failure time with time zone, whether one player or everyone was affected, the player count, the server’s public address and query-port setting, and the log excerpt around any Session failed and Removed Peer entries. Also state which client and server versions were running.