[2020] Conan Exiles Dedicated Server Launcher (Official Version: 1.1.1 / Beta: 1.1.2)

So, with the team now using the tool, I get some change requests, so here is a new version for you (and I’ll push 1.1.1 as the new official version since I got no negative feedback about it).

1.1.2 (28 august 2020)

• Moved the “Additional Command line parameters” before all the other parameters (’-MULTIHOME’, ‘-useallavailablecores’, ‘-MaxPlayers’) to allow passing things like custom map names which apparently need to appear first in the list
• Added some magic tokens to the Discord messages:{steamconnect_nopassword}, {ip}, {game_port}, {steam_port}, {rcon_port}, {server_password}, {admin_password}, {rcon_password}
  Dedicated Server Launcher 1.1.2

IMPORTANT: This version was built differently from the previous versions (which I did locally on my machine), that one (and future ones) was built using our automatic internal build/deployment system, which in theory should give the same result, but you never know, if you encounter any issue, please tell.

Regarding the new magic tokens, please use common sense and don’t use {admin_password} or {rcon_password} on a public discord

Somebody was asking for a {directconnect} token, I did not do that but you can make your own using a combination of {ip}:{game_port} and {server_password}.

It’s been working reliably for me, at least when I remember to check the “Show modded servers” box. Also there’s a known bug in the name filter edit field where what you see is not necessarily what’s there if you’ve done some mistakes and used backspace (I was told there was a fix coming for that one).

I see, that could be a problem with the server, but also with the back-end system that registers which server is up and running.

What would be interesting is to see two complete server logs:

• One when the server starts well and is visible
• One when the server is not visible in the server list

Maybe in the logs there are things like error messages about connecting to some funcom servers, if you could send me that (complete logs please), I could take a look.

I’m not sure I understand this part:

it prompts for a password and not a long download and after a lousy crash into the main one every time

From what I understand, your friend tries to connect (using Direct Connect, or from the Server List?), he enters the server password, then not sure what “long download” is (could be the loading page, could be the server asking your friend to update a mod list?), and “louse crash into the main one”, is it an actual crash (of what, the game client, the game server, the server launcher?) or do you mean that your friend’s connection fail and he is back to the game main menu page?

That’s actually interesting, your are the first person to report an actual crash of the server launcher, so yes I’m very interested by your crash dump, and by which version of the dedicated server launcher you are using, as well as information about where you installed the launcher, which version of Windows (actually a DX Diag report would be nice if you can).

For sharing the DMP file, there are plenty of temporary online sharing systems you can use (places where you upload a file, you get an anonymous link valid from 24 hours to a few days, and then it gets deleted).

In general this type of problem can be caused by:

• The ISP is doing things like multiplexing lines so the same IP maps to multiple customers.
• People who have both a Modem and Router, that both require to be setup properly.
• Incorrect port forwarding (not all the ports, opening UDP for TCP ports and vice versa, forwarding to the wrong IP, …)
• Firewall that blocks transmission in one or both directions, leading to “handshake” on the connection to not happen properly.

What I suggest in general is to:

• Make sure the IP of the machine is fixed on the router (ie: No DHCP, that guarantees the IP never changes when the server or router is restarted)
• Check that all three import ports (Game Client, Raw UDP, Steam Query) are properly forwarded to the correct IP and are not the same as anything else running on the same machine (important if you try to run both the game client and server on the same machine)
• Check that “Test Port Accessibility” button returns everything green
• Disable all the firewalls temporarily (on the machine itself, router, modem, friends machine, etc…) to see if that helps

If that still does not work, then the next step is to look in log files, both on the server and client, to see where the connection attempt fails.

Obviously, if a loading screen appears, it means that the server detected the attempt at connecting, but then at some point it failed, either because of a version problem, incompatible mods, or some timeouts during the connection process.

It’s unfortunately hard to diagnose, because there are many parts that can fail, and it’s hard to identify which one is actually causing the issue.

Team viewer???

That’s fine.
Another player had the same issue, he sent me his logs.
Thanks

Cool, it’s not actually a crash, it’s what we call a “unhandled exception”, apparently your ini files contain a parameter that should have been been numerical but that for some reason is a string, could you give me your ini files (you can hide the passwords if you want), mostly: serversettings, engine and game.ini, so I can reproduce the problem here?

Actually it’s probably this particular line:

m_ServerSettingsIni.GetEntry("[ServerSettings]", “DedicatedServerLauncherServerAffinityMask”)

in theory you should have something like that in your ServerSettings.ini:

DedicatedServerLauncherServerAffinityMask=508

obviously the tool should not fail on that, but I really wonder how you managed to get the code to fail, so if you can give me the value, that would be easy to check

Damn, that’s a shame: As a general rule of thumb, when you are in a bug reporting/qa process, always make a copy of all the relevant files, specially when it’s a rare bug.

I’ve managed to reproduce the issue, but my problem is that I don’t see how this can even happen in normal use if it’s only the server launcher writing the value (it just write a number), so knowing what the value was would have been a useful information possibly pointing to something else corrupting ini files.

Something don’t remember the launcher doing (all the times I had issues before) was that it now asks if I’m sure I want to close it, when I close the launcher.

This line of code:

  if (dw::win32::AlertBox(MB_ICONQUESTION | MB_YESNO, "Are you sure you want to close the Dedicated Server Launcher?") == IDYES)

was already present in version 1.0.1 from June 2018

So you had a running server, and you overwrote it with the content of another server, and it stopped working?

Did you keep a backup of the earlier server (you should have proper backups of your ini files at least)?

It’s hard to diagnose this type of thing, but I would suggest first to try to recreate a new clean server from scratch (keep the other one but don’t run it), with the same ports, and see if it runs.

If it runs, then copy the ini files of the server that does not run over the new server, and see if that still runs.

If that still runs, then try to copy the game.db and see if that still runs.

There are known issues on the game regarding the Ping error 9999, and hopefully a fix will be available soon, there’s not much you can do on your side, sometimes restarting the server helps for a while, but that’s about all I can say.

Have you checked that the “Test Ports” gives you all green lights on all ports?

I guess at this point I need to see the logs for the server, as well as your ini files, else it’s just going to be guess work.

You should consider joining the server admins discord, there are experienced people there who could probably also help and have ideas about that the problem could be: Admins United: Conan - Discord for Server Admins!