Conan Exiles Dedicated Server Launcher (Official Version: 1.7.5 / Beta: 1.7.7)

Dedicated server launcher (1.5.8) was working great before, for many months. Then I got a new computer (Windows 10). I used the same install of the game and launcher directory as before, just selected the new network configuration and updated the port forwarding on my router and firewall with my new IP. Get the green lights when I test port accessibility. But now I keep seeing “KDS passphrase provider” errors in the log, e.g.:

[2022.07.24-21.33.49:766][ 0]Network:Error: Code: KDS passphrase provider failed to initialize. KDS will at some point deny access unless the problem is fixed. Failure message: Error loading dedicated server provider id certificate: No certificate found with id #-1
[2022.07.24-21.33.49:767][ 0]Network:Error: Code: KDS passphrase failure: Server provider id certificate unavailable: 0x80092004

The effect is that no one can join my game. It shows up with 9999 in the server list, and when you join you can’t get past the loading screen. Direct connect works for me but for me only, everyone else times out.

I tried redownloading the launcher and starting from scratch but am still seeing this KDS item in the logs.

I have researched this error and find results going back to 2020 but with no answer or resolution. Still an issue in 2022 it seems. There is some stuff for Linux but I’m on Windows. I’ve spent many hours trying to resolve this and am at my limit but figured I would check her to see if there is a solution or something I could try.

Is this issue originating from my end or with the server launcher / software? Like I said ports are accessible according to the app. I have no idea what KDS passphrase provider or why it’s failing to initialize. Please help.

I figured it out. Seeing how I searched and searched online only to find zero resolution, and got no help here, I will share what I did in case someone with same scenario finds this.

It turns out KDS passphrase in the log was not actually the problem keeping people from joining my server, or causing the 9999 ping on the server list. Because now people can join my server even though those KDS passphrase errors still appear in the log.

What I did wrong when I got my new computer was copy the entire folder that the server launcher creates from my old computer. I thought I could just set my new ip address and update the port forwarding but that people couldn’t join even though all the lights for the ports were green.

Instead I moved the server launcher into an empty folder, opened it and effectively redownloaded all the server files. Then I replaced the ConanExilesDedicatedServer > ConanSandbox > Saved folder with the equivalent folder from my old computer, to transfer all the save data for myself and the people playing on my server. Doing this, they were finally able to join again, and the server in the list shows normal ping.

1 Like

Interesting, so it seems that some stuff in the folder was “computer dependent” and that made the connection to fail?

You got the window doubled?

Just to be sure, have you excluded the entire Dedicated Server Launcher install folder in your anti-virus?

I checked your two logs, and the DSL did restart your server early because no player was detected, and indeed the last line of stats report is that one:

[2022.07.22-08.49.19:846][715]LogServerStats: Sending report: exiles-stats?players=0

If you look in the game server logs, you’ll see that there were up to two players connected, then they all dropped for some reason, and then there was some reconnection attempts that took some time and the server was restarted before the entire processing of the new connection was done, so the exiles-stats?players=1 was not yet sent.

Linking this over in case anyone needs it:

2 Likes

I’m kind of confused, I tried the test live versions before the summer break - to test the log file format change - and there was no problem deploying the server.

I’m currently checking with the team, looks like the Steam ID of the server changed, but I need confirmation.

Right now I’ve no idea how I can support 443030 for the current Live version and 931580 for Test Live, I don’t have anything like that in the code… I guess I could possibly add a new override parameter when defining branches, like “Name|Password|ID”?

I launched your dedi and setup a testlive, turned the server and dedi off, used that command pointed at the server exe in that folder, then when I reopened the dedi launcher, it had the right version. When it started it didnt get the old version either.

MAGIC

1 Like

If other encounter the same issue, could you try the following:

  • Instead of starting the Dedicated Server Launcher normally, open a command shell at the same location the launcher is located, and start it with the following command line:

DedicatedServerLauncher1600.exe -steamid 931580

Basically the DSL is compiled with hardcoded values 443030 and 440900 for the server and client ID values, but this command line can be used to override the value (there’s also “-steamidclient” for the client value).

What happened is that the 3.0 TestLive version has a different Steam ID, so when you try to fetch it with the DSL, it will get the old Test Live server, not the 3.0 one.

Until I find an elegant way to solve that, it’s possible to use this manual launch with the override parameter.

6 Likes

That is certainly more elegant on its own! Thanks!

Getting mixed results but one of the two methods has worked so far for the cases I’m aware of fyi.

After a mishap (I accidentally changed branch by typing in the wrong field) I cannot get the server back up and running using either method…

Okay I managed to fix it by installing the server in a new folder and doing the simple -steamid method

Here’s exactly what I had to do:

Make a new server folder. Put the dedilauncher in that folder and run “DedicatedServerLauncher1600.exe -steamid 931580” to create the folders with only the right id. Edited all the fields to be what I wanted (ports, server name, branch, etc). Now it had the right server version because I never ran it with 443030 (which confused my original).

Ok, good to know :-/

Probably means that going from one product id to another on the same install location is not working smoothly, possibly some SteamCMD artifacts, or maybe some local differences between the two versions of the game server) :thinking:

1 Like

Yeah its something like that. If I tried in the old server, it was giving me messages like “931580 is already up to date!” even tho it was stuck. Fresh install only using your fix on first launch of dedi is apparently key…. That and dont change the branch accidentally after creating it (like I stupidly did)

Suggestion: If it were possible to point the “players joined” and chat box to the discord hook with a checkbox, it would be very, very cool. With a certain mod we could do this before, but it would be awesome if it were directed to discord by the launcher like the update events and such.

1 Like

Wondering if anyone can assist with an issue I’ve started to have in recent days.

I’m using Dedicated Server Launcher 1.5.8 on a Window 10 machine to host two servers, and for some reason I’ve got a version mismatch between the server, and the steam client.

It seems to be a server issue with my box, because I can connect to any other public server on the internet no worries, but for some reason my server version is way ahead of what’s currently public.

  • Dedicated Server is showing 372351/32628
  • Game client is showing 354133/32628

When running, the servers seem perfectly healthy, boot fine, and when I try to validate files on startup, they’re all good, and return a good validation with no need for an update.

They’re both showing 9999 ping in the server list and can’t be connected to.

Can anyone assist in troubleshooting this?

No idea what’s causing it, and there doesn’t seem to be a difinitive answer on how to fix it everywhere I’ve looked.

Any help would be much appreciated :slight_smile:

I dont know whats causing it but I know what I’d try. I’d make a new folder with the 1.6.0 dedi launcher, run it to generate the server data and folders, then move over the old database and server settings.