Dedicated Server "Unable to find machine for peer"

[Takedeze]

I've set up a variety of dedicated servers and am familiar with the general process (steamcmd and port forwarding is usually about all it takes). But with Enshrouded I've been having problems. I have tried installing the Enshrouded Dedicated Server both via steamcmd (my preferred method), and through the Steam Library, and have had identical results (unsurprisingly, but some posts online indicated this could be an issue).

I am running the dedicated server on a separate machine from the one I game on. They are, of course, both on the same LAN.

When I run the dedicated server I was not able to find the server in the in-game server list, or using the Steam Game Servers list. In addition to verifying the port forwarding rules on my router, I have also verified that the Windows Defender firewall on the server is set to allow ports 15636-15637 for both TCP and UDP. I was only able to find it by favoriting the server's local IP address to the Steam Game Servers list, at which point it showed up in game.

Now, when I try to connect, it asks for a password. I enter the password, and the cutscene starts. "Long ago, a wanderer brou-" Then I get an invalid password error. The password is correct, and to be sure I made a single character password and also tried it with no password.

The log shows:
[online] Client 'mysteamid' authenticated by steam
[session] Unable to find machine for peer 0.
[session] Unable to find machine for peer 0.
[session] Could not store acknowledge of packet id: 2
[online] Disconnecting peer #0 (SteamSessionConnectionMsg).
[online[ Removed Peer #0.

Any help would be appreciated.

[Takedeze]

Ok, for anyone else having this problem, it's not an issue with ports or anything complicated like that, it's a problem with the default enshrouded_server.json. The default is generated the first time enshrouded_server.exe is run. It is missing:

    "gamePort": 15636,

just before the "queryPort" entry. But that isn't the problem (It may be a problem, but it is not the problem.)

The actual problem is in the "userGroups" section, which has 3 groups: "Admin", "Friend", and "Guest". Add a fourth group: "Default". I'd suggest copying the "Friend" group, and then change the password to match the password specified at the top of the file. Done.

        {
            "name": "Default",
            "password":"<SamePasswordAsAbove>",
            "canKickBan": false,
            "canAccessInventories": true,
            "canEditBase": true,
            "canExtendBase": true,
            "reservedSlots": 0
        }

[Quartzan]

@Takedeze Thank you! I finally was able to get my server working by following this.

[Reaper]

@takedeze Thanks man I was finally able to log in to my own server, this should all be set up by default by the game devs.

[Shadowfox85]

That worked for me. Thank you so much!

[Krellor]

Thank you so much. I thought I had a network config or wine issue running this.

[Эх Жекос]

Also your password to connect to the server will be the same as password from Default group in enshrouded_server.json
{
"name": "Default",
"password":"here_is_password",
"canKickBan": false,
"canAccessInventories": true,
"canEditBase": true,
"canExtendBase": true,
"reservedSlots": 0
}

[cjayride]

Save our game server, this worked -- thank you.

[Acva]

If anyone else is still looking at this later on. You do not have to specify a server password at the top of the file. You will only need to have the usergroups password specified. The players will actually join with those usergroups passwords rather than a global server password and depending on the password will put them in their respective groups.

This explains the behavior where you have to match the same password as the global server password since it doesn't need the global one and just the usergroups one. So make sure to remove the global password entry at the top of the file if you have it