Server on Linux

Running an Eco server on the Linux operating system is not supported by Strange Loop Games.

Some Linux users have successfully run servers with certain tools, but they can have debilitating problems with new versions, which may require different workarounds each time.

If you have a support question regarding Linux servers, please join the #linux-discussion channel in Eco Discord, but keep in mind the information above.

User Guide: Running from a shell (linux/debian) with UI
Note: This is a guide submitted by User:Simonmicro, using Eco server version 0.7.5.2 on Ubuntu 18.04.1 LTS

If you want to run the eco server from a shell under linux with the UI for easier server configuration, you will need a virtual desktop environment. The following example will demonstrate a basic setup under linux (debian 9) using a minimalistic virtual desktop.

First you will need to install some required packages: vnc4server (the virtual desktop), lxde (minimalistic desktop), mono-devel (to execute .exe files). You can install them using the following command - maybe some packages can not found for your distribution (for that please see your distros documantation).

Now you can run your VNC server using the following command - please take a look inside the printed log file to query the vnc listening port!

Now use a VNC client to connect to your server. If you are connected right-click to the desktop background to open a terminal. Inside the terminal you can start the desktop with a file manager using the following commands:



Now navigate to your servers root (where EcoServer.exe is located) and right-click its file. Select "Mono Runtime (Terminal)" to run your eco server with its UI.



Alternatively, you can use the already opened terminal to navigate to your folder and start the eco server with the following command:

Please not that this procedure doesn't work with eco server versions 7.6.0 and 7.6.1 (see https://github.com/StrangeLoopGames/EcoIssues/issues/8577)!

After some time, it is possible that your server goes to sleep, this is blocking and you can no longer access it by VNC. For this, you can wake up your session with these commands in SSH :

List all sessions : Now, search for your session or unlock if you don't know what your session is (replace IDSESSION by your session name) :