Viability of EOS for hosting dedicated servers and multiple instances on the same machine

Hello,

Our current build relies on EOS for connectivity and we are currently implementing a dedicated server.

While turning off Relaying from the P2P setup it sounds like it should work reasonably well. However we did come into an issue mostly affecting commercial hosting services. The server, as the game, requires a proper device id authentication and connect before starting the lobby and accepting connections. However this device id auth is unique to the machine. Trying to start two separate servers on the same machine just invalidates the older ones as EOS identifies the same authenticated entity as in the old lobby. Is there a workaround for this? And mainly is safe to use the EOS networking layer to for the dedicated server setup?

Hello! Dedicated servers do not require authentication via the Connect Interface to use Epic Online Services.

Using device IDs to authenticate dedicated servers is not a supported workflow, so there are no workarounds for this.

Instead, creating an EOS Platform instance with a set of trusted server client credentials is enough to start using the various SDK APIs.

You’re correct that device ID tokens are unique to the machine, and it is not possible to create multiple IDs simultaneously.

EOS P2P is also not designed for use with dedicated servers, which is why a Product User ID is required.

Instead of using P2P with dedicated servers, a direct IP connection is recommended.