I thought I had tried that but it seems it does not run validate unless “auto-update” is also selected.
Validate seems to have repaired it. The .exe is back where it’s supposed to be. I wonder why it got removed in the first place.
Weird
servers Players Helping Players Conan Exiles
Confira as permissões do seu antivírus e firewall não há nada de errado com o DLS1.7.9 o meu servidor funciona normalmente 
Maybe check your anti-virus history, maybe it decided to quarantine the file for no special reason (would not be the first time).
1 Like
2 Likes
I’m hosting a dedicated server from my PC using this application and trying to join the server on the same PC using the Gamepass version of Conan Exiles.
In the application I have “MultiHome” selected, all ports forwarded (TCP & UDP) on my router, and I went through Windows Firewall and allowed ports there, and allowed the connection of the dedicated server application itself.
I have seen others talk about using a different connection (like Ethernet) and the server works then, but I don’t have another connection to try. I tried setting the dedicated server up on another machine that has an Ethernet connection and the problem still occurred.
Furthermore, I don’t know if my issue is network related like an option in my router is interfering, or if I’m supposed to port forward something from Xbox since I’m using their version of Conan Exiles. If anyone can help me, I’d really appreciate it.
In the first post of this thread there are a number of Question/Answers you may want to consult.
Before trying to solve the local access, make sure the game server is properly configured and accessible by people from the outside your network (ie: They can see the server, they can connect to it an play a few minutes without timing out and getting disconnected).
Common issues when trying to access a server on your own network are:
- When trying to run both the client and the server on the same machine, you have to make sure that you use a different set of ports, because the client by default will use these ports.
- It is not uncommon to have local routing have problem with detecting the server through the public/external IP (which is what the server browser use when it lists the game server), in which case the solution is to use “direct connect” with the local IP of the server on your local network.
Regarding the different connection, that’s not necessary, but if you had that, you could keep using the same default ports, as long as the client uses one network card and the server uses the other.
1 Like
When I have my friend look at my server it shows 9999 ping and doesn’t allow them to connect. I’m not sure exactly what I’m doing wrong.
In my router settings, I have 7777-7778 and 27015 forwarded as well as the custom ports I have set for Game Client & Raw UDP. I figured the game uses 7777-7778 for its ports, so if I changed my ports to something else it’d work.
I tried direct connecting to my server using the external IP shown in the app and then the Source Query Port, like so “IP:27015”, but it didn’t work.
In my Windows Firewall, I allowed all connections to the dedicated server application, same with Conan Exiles. I made rules for the required ports to be opened on both inbound and outbound connections, not sure if both are required but I did it anyway.
I’m confused by all of this. If you can see I’m doing anything wrong, I’d really appreciate the help.
1 Like
When doing testing, try to temporarily disable both your firewall and antivirus completely, and ask your friend to connect again.
If they still can’t connect, then what we need is:
- The complete Conan Exiles client log file for the connection attempt
- The log of your Conan Exiles game server for the same attempt
By comparing the content of the two files you can see what was sent, what was answered, and where/when it stopped.
3 Likes
They’re currently not available so I can’t do much until then. I tried disabling my firewall and anti-virus and checked if I could direct connect or join directly, it didn’t work. Figured I’d try anyway 
Below is the server log for just me attempting to join. I assume the client log is the Players tab, but since I wasn’t able to connect nothing is there.
I have no clue if this log with just me joining helps or not. If not, I’ll either edit this message with the new log stating so, or reply to your message if you send a new one.
ConanSandbox.log (696.0 KB)
Thank you again for your help. Hopefully you can figure this out as I have absolutely no clue what it could be.
EDIT: After having my friend attempt to join my server after my firewall & anti-virus are de-activated they still could not join. They see 9999 ping and timeout connecting to the server after a few minutes. I had them try the external IP and port direct connect to no avail. Below is the log of the most recent server session with them trying to connect.
ConanSandbox.log (707.6 KB)
1 Like
I would like to see a debug mod that would show like above, or like a console to collect messages. The debug mod only needs to be assertive, and it must dump to console if assert()s fail.
Someone took a joyride with that much suggested before. I’m just asking to be liberal with the assert()s until some issues are resolved.
Looking at the log file, I see that you’ve put the DSL on your desktop, which is really not recommended.
Instead of
- C:/Users/Teste/Desktop/Main/Programs/ConanDedicated/DedicatedServerLauncher/
you should try something like:
- C:/ConanDedicatedServerLauncher/
Regarding connectivity, I don’t see a single attempt of connection from the outside.
Have you got some green results from the DSL when doing the port testing?
I’ll move the server to the root of my C drive.
As for the launcher, Game Client, Raw UDP, and Source Query ports are all green, and have been green for every attempt at starting the server.
What could be causing no connections to be from the outside when I have my ports forwarded and firewall disabled at the time?
Hard to say, I did a quick test with my own server, here is the difference between your log (on the left) and mine (on the right)
I did some cleaning (removed non relevant stuff to make it easier to follow), but basically if you check the log, we have the InitGame, StartPlay and MatchStarting sequences quite similar between yours and mine.
The thing is, your server is not doing anything during the 7 minutes between after the “Key distribution web service: Connected” and the “FPlatformMisc::RequestExit(0)”.
Mine on the other hand goes on the “NotifyAcceptingConnection”, the challenge between the client and server happens, the server answers that the list of mods does not match, my client updates the mod list, then reconnect, and eventually we reach the “Join succeeded: mike#76387”
So in your case, there’s not even an attempt at all, whatever your friend did did not manage to reach the server.
What I would suggest is that you try to connect to your server from your own local network, on another machine, using Direct Connect with the local IP of the server on your network, keep the server log file open (or check in the DSL by expanding the window so you see more lines), to check if you can see the connection attempt happening or not.
Doing that locally would eliminate any port forwarding issue.
What do you mean by the local IP of the server on your network? Where would I find that IP at?
And when I go to join using your method, do I look at my logs for whatever comes after Key distribution web service: Connected and see if a connection is trying to be made?
Local IP is the one shown in the selector at the top under “Network Configuration”, like “192.168.1.x”.
In the logs, search for anything related to “NotifyAcceptingConnection”
LogNet: NotifyAcceptingConnection accepted from: x.y.z.w:port
that one is the very first time where your server sees a new attempt at connecting from a client.
Alright. I’ll have to check that out. Hopefully we can get somewhere with this.
1 Like
I haven’t tried your method yet, but I wanted to add that before I posted here, I tried starting a server from another machine in my home that has a wired connection and I had the same issue.
I port forwarded for that machine before I tried starting the server. Does this help in diagnosing the issue any further?
Not really.
The symptoms are typical of port forwarding not working (for whatever reason), but you said the DSL “Test Port” was working, so would imply the port forwarding is working.
I did as you instructed and tried to directly connect from another machine (the machine has a wired connection) using direct connect and got an error saying “Server Timeout”.
I used the IP shown under the Network Configuration section in the DSL tool, as you said to do, with 27015 as the port. Joining the server from the other machine with and without Multihome selected made no difference.
I tried joining the server with the host machine’s firewall on and off, joining using the external and local IP, both with 27015 as the port. I’m not reconnecting my internet connection each time I disable my firewall as I’m not sure if that’s required or not.
Checking the logs before and after I ended the server for anything with NotifyAcceptingConnection, but I didn’t see anything. I’ll post the log of my last server session:
ConanSandbox.log (697.5 KB)
At this point, seeing hundreds of other servers without this ping issue is making me think I’m doing something wrong.
From this forum and threads like Reddit that I’ve scoured for a solution, people have success directly connecting to their server even with it showing 9999 ping. It allows them in and is the only way to play on their server, from what they say.
Every time I’ve tried directly connecting with MyIP:27015 from the game’s server browser, I always receive the Server Timeout error after about 30 seconds of it trying to connect. Since I don’t know where I may be messing up, if at all, I’ll go through my process for you to make sure I’m doing everything correct.
I start my dedicated server (with the Validate Files box ticked), launch the Xbox Gamepass version of Conan Exiles, go to the server browser and skip the PvP/PvE screen, click Direct Connect, enter my IP and port 1.1.1.1:27015 (example IP), and then wait for the error in red to pop up.
27015 is the Steam communication port, not the game port. For direct connect, use 1.1.1.1:7777 for WAN; if doing a LAN direct connect, use the port number you set as the game client port in DSL settings.
3 Likes