[2021] Conan Exiles Dedicated Server Launcher (Official Version: 1.3.8 / Beta: 1.4.5)

Another minor version, with tweaks on the Zombie Check and Discord Webhook features

1.4.1 (12 april 2021)

• The “Zombie Check” now ignores the “other” part of the IO information: Apparently when the server is stuck on shut down, it still perform some other stuff.
• Added some magic tokens to the messages: {server_pid}, {map_name}, {date_now_iso}, {date_now_human} (please note that the ISO date is in UTC, while the human readable one is using the local time of the server)
• The magic tokens can now be used in the Discord bot name, so you can use {servername}: ‘{map_name}’ if you want to display the name of the server and the selected map automatically
• The Discord JSON packet will now use the “description” instead of the “content” field when the “Time” check box is enabled, since apparently the API was changed last week
  Dedicated Server Launcher 1.4.1

As usual, please report any weird thing, regression, or feature not behaving as expected.
Thanks

Nope, no idea, and unfortunately the error message it not clear enough, so I just pushed a new version that adds the error code in the error message.
https://dl.conanexiles.com/exiles/DedicatedServerLauncher/DedicatedServerLauncher1402.exe

Could it be that there’s another dead server process lying around?

Sure, you can even keep the old one if you want, they are generally compatible, and you can switch from one to the other, that rarely cause problems

Made a minor version with some tweaks reported by one of the testers of th Zombie feature.

1.4.4 (19 april 2021)

• The “Looks like this is an unkillable Zombie :’(” message should not be displayed anymore if the server was successfully killed just before
• The “Checking if SteamCMD started…” should appear less frequently now
  Dedicated Server Launcher 1.4.4

If it works for everybody, it will replace 1.3.8 as the new version, if you found some blockers, please tell

Because of some weird networking bug introduced in the FLS code last year, the servers are having trouble accepting connections from machines on the same local network, when their external (the one other players outside need to connect to) IP is used, so if your local machine is on the same network as the server, you often need to use the local network ip of the server.

If you type “what’s my ip” in a search engine, it will most probably answer something like “Your public IP address is 39.173.237.34” but if you open your network settings on the machine you will see the local IP.

In the launcher you can see that in the top of the UI:

“External IP” is the one players outside the building need to use, the other one is the local network address.

Have you tried to run this server with all the other VM/game servers shut down?

Generally the “Failed to bind” happens when a port on a specific IP is already used by something else, in that case the solution is to other have another network adapter (that requires using MULTIHOME to select the right one), or to use a completely different set of ports for each server (and obviously redo the port forwarding).

In your configuration, which services are associated to ports 8291 and 14001? These are some quite unusual port choices