Menu
 

Echoes of Elysium Dedicated Server Setup: Package, First Start & Join Test

Echoes of Elysium Dedicated Server Setup

Echoes of Elysium server tooling is still something to verify against the current package. The safest setup is a short sequence: identify the server app or provider template, make a test world, record the endpoint, and prove save/restart/join behavior before the crew invests time in the campaign.

Package note: SteamDB currently observes a server tool at app 2915100 with Windows and Linux artifacts. Confirm that your provider or Steam installation exposes that app and the same files before using any command from this page.

Install and record the package

  1. Use the current Steam dedicated-server tool, provider template, or package documented for your build.
  2. Record app ID, branch, build, operating system, install directory, and launch command.
  3. Keep the server files separate from the client install when the package supports that arrangement.
  4. Do not copy a port, INI key, or command from another Unreal/game-server guide.

First-run checklist

  1. Choose the region nearest the majority of players.
  2. Set a private password or access rule before sharing the endpoint.
  3. Start the server with a new test world.
  4. Confirm the process stays running and note the log location.
  5. Join with one trusted client using the endpoint supplied by the package or panel.
  6. Make a harmless world change, disconnect, restart, and confirm it persists.

Endpoint and firewall

Use the port shown by the current package or provider. If self-hosting, allow that port in the host firewall and router, then test from another network. A server browser result is not proof that the actual game connection works; test both listing and joining.

Move an existing world

  1. Stop the source process cleanly.
  2. Copy the complete active save and keep the original untouched.
  3. Place a copy in the target package's documented save location.
  4. Start a test instance and verify world identity, airship state, player access, and a new save.
  5. Only replace the production world after the test succeeds.

Use the save and restore guide for a rollback plan.

When setup fails

SymptomFirst checks
Process closesPackage/branch, working directory, launch command, dependencies, and log.
Not listedServer name, listing state, region, build, and provider query behavior.
Listed but cannot joinActual game endpoint, firewall/NAT, password, and client/server build.
Wrong or blank worldActive save path, clean stop, restore copy, and package-specific world selection.

References

Use the official game site for current game positioning and the SteamDB app observation only as a package clue. Recheck both after an update.

Related guides

Launch managed Echoes of Elysium hosting with current plan details.

Tired of fighting this issue every patch?

Run a managed Echoes of Elysium server with us. We handle the patches, mod-version pinning, save backups, and DDoS protection. Set up in minutes, multiple datacenter regions, no contract.

See Echoes of Elysium hosting plans →
Top