July Hotfix Broke my local server :(

Conan Exiles PC Discussion
1

I have been playing Conan Exiles on Steam since months after it came out and loving Enhanced.

Now I play it with my kids on a non-modded local SteamCMD server I setup on my PC, we just use the local router IP address:port to connect, the server isn’t online. Enhanced took us off Official servers because nobody could connect when it launched so I just created a local server and it’s been glorious family fun.

The process when a client update comes out is I do the “force_install_dir C:\ConanServer\DedicatedServer” and it’s always worked fine, until July Hotfix.

I’ve reVerified local client files, reForced_install a few times. I even waited a few days and did it all again every day hoping for a fix-fix. I always get the usual client-side “version mismatch” error when trying to connect to the running local server. Usually the error just means… UTSD. Update the server, dummy! But not this time.

Still not working. I’m at a loss. Any help would be great!

2

Try to use the official Funcom Dedicated Server Launcher. I use it and have no problems.

Here:

3
4

Hi, thank you both for taking time to reply.

I’m using Win11 to play Conan Exiles on Steam. Steam is setup to autoupdate the client-side (game), I always get any available updates as soon I fire up Steam.

Soon after Enhanced came out I created a Dedicated Server on my local machine and setup Win11 security so other PC connected to my local network can also connect to the server.

My usual routine is to startup the server from a shortcut on my desktop that opens a batch file in the appropriate director to open the server with the following: start ConanSandboxServer-Win64-Shipping.exe -log QueryPort=27016 Port=7777

I don’t have any problems starting the server. Connecting the game is a Direct Connect with my PC’s IP on the local network and server’s port :7777. Never had a problem connecting. Version Mismatch has always just meant I needed a server update.

Whenever the game has an update, I first open (where C:\ConanServer is where the dedicated server is located:

Run C:\ConanServer\SteamCMD\steamcmd\steamcmd.exe

Then in the subsequent command prompt I run the following:

force_install_dir C:\ConanServer\DedicatedServer
login anonymous
app_update 443030 validate
quit

I ran server update the day of the July Hotfix, I assumed this would just be same routine. Once both game and server were updated, I started getting the persistent version mismatch error.

Attempted fixes have included doing a validate game files in Steam, see no issues everytime I’ve done it. Then I’ll do another dedicated server update process, which seems to end quickly due to lack of files to download.

I’ve kept regular backups of my server with the last one being two days before the hotfix. I haven’t tried restoring and validating the backup yet. Nor have I completely uninstalled the game from Steam and re-downloaded. But that’s where I’m at next. Or I could just wait for the next update because I really think something went wrong with the last update on my side. Maybe I looked at the files downloading to the server wrong and corrupted something. But the game itself connects to Official server on Steam so it seems to be fine. I do NOT want to start this server over again! Nor do I want to quit playing Conan. I love this game!

5

Did you get it working again? If so, please share.

Thanks!

6

I did, everything I tried and discovered is in the linked thread.

I don’t see you mention using the Dedicated Server Launcher - I highly recommend using it, trying to force the server to update from the cli did not work for me, for some reason doing so through the DSL worked.

Look at the version in the game client - on the main screen at the top right you should see: “Revision #370,197/0 Backend Live(1)”. This way of presenting the game version was done by one of Funcom’s typical crackheads. From that string of nonsense take out the value “370197”. For the server run the DSL and look at the top where it says the version number - if it does not match then you legitimately have a version mismatch between the client and server. For me it was the server that refused to update. It finally worked after deleting some files (appmanifest_443030.acf, download, temp) and then checking “Validate files” in the DSL.