over 3 years ago - Toolguy - Direct link

Just a minor release to fix the issue found by @mogeizo

1.3.1 (1 october 2020)

  • Fixed a bug introduced in version 1.2.5 with the “Test Port Accessibility” showing grey instead of red lights for errors.
    Dedicated Server Launcher 1.3.1

Here is what the port testing is supposed to look like when it fails:

DedicatedServerLauncher13011207×663 90.2 KB

over 3 years ago - Toolguy - Direct link

Thanks, I took a look at the link, some of these were already flagged as “log spam” and may be fixed in future updates, but I can’t really tell you anything regarding if these errors are actually causing issues or not.

over 3 years ago - Toolguy - Direct link

Well, the main issue there is that your first message did not clearly state that:

Anyone know if you can set this up on a server that is already functioning, because I have tried so many ways to get this thing to work and at present it does nothing, it will not find the server, it will not connect to the server and it’s just driving me nuts.

The way I was reading it was that:

  • You already had a server running, using some other tool, script or whatever, on some machine
  • You wanted to use the Dedicated Server Launcher instead, and were trying to import the existing server

Now when I read “it will not find the server, it will not connect to the server and it’s just driving me nuts.” I think it’s a just a big misunderstanding: The Dedicated Server Launcher is not some kind of control panel you can use to control some remote server, it is a tool that allows you to run your own server - on the same machine where you install the Launcher tool.

Could you describe what you actually wanted/hopped to do?

over 3 years ago - Toolguy - Direct link

Still no solution on my side, that being said (crossing fingers) it has not happened to me this year.

Which version of the Dedicated Server Launcher are you using? Pretty much all the versions should be fine EXCEPTED 1.3.0 which had a bug where the lights stayed gray instead of switching to red (that was fixed in 1.3.1).

Anyway, if the lights don’t turn green, it will not allow anyone to join your server, only people who are on your local network.

To get the greenlights, you need:

  • An ISP that allows port forwarding
  • Enable port forwarding on your router to let the internet traffic reach your router on the selected ports
  • Make sure no firewall anywhere is blocking anything
  • Make sure no other application uses the same ports

Now i’m looking to be able to play it off of this machine as well, the notes weren’t all to descriptive on how to do this.

If you are planning to play on the same machine that has the server, what I recommend is:

  • Use different ports for your server (like 7780, 7781 and 27016 instead of 7777, 7778 and 27015)
  • Join using Direct Connect with the LOCAL IP (there is a bug in the game right now that causes issues if you try to use the External IP while being on the same local network)

so i load up the launcher. does steam need to be closed for this?

Not anymore

so i clicked multihome this will allow me to play game and run server on same machine?

It’s normally to get multiple servers running on the same machine, or when you have multiple network cards, this should not be necessary, but that generally does not cause any issue either: Just make sure that port forwarding is done on the right IP.

over 3 years ago - Toolguy - Direct link

Good, sorry for the confusion :slight_smile:

I apologize for the late reply, long story short, I was able to launch & run the server in the laptop after checking the tooltip of the launcher (I was port forwarding only UDP :o), but on the desktop PC, it was still all red.
It was the same even after disabling Windows Firewall, but somehow subscribing to Norton and changing firewall setting there did the trick. Now it is clear and all green.

Ok, so the good old “antivirus deciding to break things”

When I click the start button in the launcher app, it starts going but then the server shuts down itself with error log of “LogServerStats:Error: ServerStatReporter: Failed to find address and port, NetDriver is null”.

Well, for that one, I need you to send me the complete server log file, because without the context, the only thing this lines tells me is that “well, that did not work”, which is not super helpful :slight_smile:

over 3 years ago - Toolguy - Direct link

SteamCMD error Question for you people. :bulb:

There’s been an issue in this tool where sometimes it would fail with an error message:

‘\src\common\contentmanifest.cpp (650) : Assertion Failed: !m_bIsFinalized’

at this point SteamCMD stops updating, it just output errors after errors, until it gets reinstalled or some manual cleaning/deleting of files like the appmanifest for the project. :sob:

I know it has happened to me once last year, and also to @Nahso, @Piankhi, @RexChiller and @Darkbibou in the past, but that was more than 6 months ago, since then I had not seen any other report…

…but apparently it just happened to @Justice this week, so apparently this issue is still happening.

So my question to everybody here are:

  • Have you ever had this problem?
  • If it happened, were you able to fix it (how) or did you reinstall everything?
  • Has it happened recently?

Thanks :slight_smile:

over 3 years ago - Toolguy - Direct link

Glad that worked :slight_smile:
Enjoy!

over 3 years ago - Toolguy - Direct link

Sorry, I can’t answer to any question related to game messages, this is for the Conan Exiles support team, this forum thread is exclusively for Dedicated Server Launcher related questions.

over 3 years ago - Toolguy - Direct link

For the ones among you using version 1.3.1, do you think it is good enough to be the new official version as a replacement for 1.2.5 :question: