Crashing servers

Game mode: Online private
Type of issue: Crash
Server type: PvP
Region: EU


My server is regularly crashing during raid time resulting in a 1020 ping.

Any chance you can put a preventative measure in to fix this ?

This is from the logs:

[2019.12.21-20.00.24:505][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 207146048242087245216193244190226199227017134038058160003083
[2019.12.21-20.00.24:520][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 040025056162230046100111044052190171043183062057196148013216
[2019.12.21-20.00.24:715][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 010058202187107251028035155068133032052063179065075249073081
[2019.12.21-20.00.25:007][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 067074046057238065208244064221034089025086143191189197023227
[2019.12.21-20.00.25:035][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 255189048225159116205146254155044019116102219226239027245182
[2019.12.21-20.00.25:067][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 203208184006148229245140051006054087123059183125183010203128
[2019.12.21-20.00.25:125][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 042234167064096113127242041068099061254255133072042194239061
[2019.12.21-20.00.25:216][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 019150101127109203034101249170127009244059158171222206043119
[2019.12.21-20.00.25:423][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 060117227206067001233208057093205117152051120198073061105001
[2019.12.21-20.00.25:529][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 207146048242087245216193244190226199227017134038058160003083
[2019.12.21-20.00.25:730][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 010058202187107251028035155068133032052063179065075249073081
[2019.12.21-20.00.25:801][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 096063050131180071093123117073169148118157075102090022039022
[2019.12.21-20.00.25:824][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 150151113004051130106251196006155160080198115187037048147193
[2019.12.21-20.00.26:638][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 067074046057238065208244064221034089025086143191189197023227
[2019.12.21-20.00.26:658][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 203208184006148229245140051006054087123059183125183010203128
[2019.12.21-20.00.26:705][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 042234167064096113127242041068099061254255133072042194239061
[2019.12.21-20.00.26:852][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 040025056162230046100111044052190171043183062057196148013216
[2019.12.21-20.00.27:133][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 255189048225159116205146254155044019116102219226239027245182
[2019.12.21-20.00.27:401][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 060117227206067001233208057093205117152051120198073061105001
[2019.12.21-20.00.27:501][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 019150101127109203034101249170127009244059158171222206043119
[2019.12.21-20.00.27:582][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 150151113004051130106251196006155160080198115187037048147193
[2019.12.21-20.00.27:634][554]LogHandshake: SendConnectChallenge. Timestamp: 14590.250000, Cookie: 067074046057238065208244064221034089025086143191189197023227


Please provide a step-by-step process of how the bug can be reproduced. The more details you provide us with the easier it will be for us to find and fix the bug:

  1. IDK
1 Like

Thats probably the reposability of the server host.

1 Like

Can i get some support?

it seems to happen to all server during raid time even officials. There’s something broken in the game.

Anyone @ funcom able to respond

If you have a private server as you have it labeled, that’s between you and the server provider.

1 Like

Hello @JayCee, we’ll need you to share further details in order to be able to assist with this matter.

Are you hosting the server yourself?

If so, have you looked into our troubleshooting guide?

We’d need you to share full crash dumps and/or logs to look into the matter:

If not, have you reached your current server provider in order to determine if there could be any possible issue on their end, either hardware or network related?

@Hugo

Yes i host the server myself through a dedicated server.

I9 9900k
64GB Ram
NvME SSD.

There are no hardware faults and the network is fine (100GB)

There’s nothing in the trouble shooting guide relating to this.

How would you like me to share the log files with you ? (i have ~100 backed up and they are large files)

Thanks.

Here is a link to the full log file. Please pay particular attention to the error messages in post #1

Any updates on this ? There’s quite a few threads on this and it would make sense if we all collaborated.

My server rent is due on 15th Jan and I don’t want to renew until this is fixed. Someone at funcom must know why the cookie/handshake errors occur or at least what it means…

Is it a vulnerabiliy which is being exploited ?

The server (1322) is under attack for about 1 hour. I don’t know where to go for this. The delay value continuously increases to 1020. DDos DDos DDos

Hi funcom, any chance of a response please?

Hey @JayCee

For the looks of the logs, somebody is clogging your server’s network. You should get in touch with your server provider to look into it and monitor future attacks.
We’re also looking into increasing network security and filters on our end.
Apologies for the frustration.

4 Likes

Thanks for confirming what I suspected.

The offender in this case is sending many ‘Connect’ packets to FunCom’s Conansandbox.exe server programme on the UDP port. The conan exiles server programme can’t handle the volume of handshake requests and locks/freezes up. (I counted c4,000 requests in one attack) – this just looks like normal traffic and wouldn’t trigger any anti-ddos.

Also quite important to note that the server bandwidth is never stressed under this attack. Your comment @Ignasi about clogging my server network is incorrect.

These are malformed UDP packets according to a friend.

To be clear my server never freezes up only the conan program so the attack specifically targets funcom conanserver.

Have you seen the amount of 1020 ping threads in these forums over the last few weeks alone? This is a major issue for populated servers.

Two further questions:

  1. Have funcom acknowledged that this attack is happening on many many servers? Both private and on gportal?

  2. Is anything being done about it & if so when can we get an update?

The only solution which I know of is to whitelist IP addresses in the firewall, which is hugely impractical.

I’m happy to test/support in any way I can.

1 Like

@Ignasi I have found what is causing the problem and how to re-create it.

please DM me for the info as this needs patching ASAP!

edit: DLC caused it, stop selling DLC until due dillengence has been applied!

You could also have a log parser that when that action happen to many times it will null-route in prerouting the source ip. But you’ll probably need a linux/*bsd firewall for that.

Probably when we get the patch for the modding engine not allowing thralls to eat and leveling, and to fix all the other exploits that can’t be said on forums or the thread get locked and hidden.
Remember this game is also for console, so it make sense for them to wait and make a big patch so it can be pushed to all platforms at once.
It make sense, I don’t blame them, so always think they won’t make a pc-only patch, that would sprout angst between pc and console players.

@q9c9p I’ve identified the specific issue which causes this: (1020 ping)

2.58.14:828][ 38]LogHandshake: SendConnectChallenge. Timestamp: 3723.670410, Cookie: 247041080095151144163047015184012177025206140010193204189007
[2020.01.11-12.58.14:829][ 38]LogHandshake: SendConnectChallenge. Timestamp: 3723.670410, Cookie: 247041080095151144163047015184012177025206140010193204189007
[2020.01.11-12.58.14:830][ 38]LogHandshake: SendConnectChallenge. Timestamp: 3723.670410, Cookie: 247041080095151144163047015184012177025206140010193204189007
[2020.01.11-12.58.14:831][ 38]LogHandshake: SendConnectChallenge. Timestamp: 3723.670410, Cookie: 247041080095151144163047015184012177025206140010193204189007
[2020.01.11-12.58.14:832][ 38]LogHandshake: SendConnectChallenge. Timestamp: 3723.670410, Cookie: 247041080095151144163047015184012177025206140010193204189007
[2020.01.11-12.58.14:833][ 38]LogHandshake: SendConnectChallenge. Timestamp: 3723.670410, Cookie: 247041080095151144163047015184012177025206140010193204189007
[2020.01.11-12.58.14:834][ 38]LogHandshake: SendConnectChallenge. Timestamp: 3723.670410, Cookie: 247041080095151144163047015184012177025206140010193204189007
[2020.01.11-12.58.14:835][ 38]LogHandshake: SendConnectChallenge. Timestamp: 3723.670410, Cookie: 247041080095151144163047015184012177025206140010193204189007
[2020.01.11-12.58.14:836][ 38]LogHandshake: SendConnectChallenge. Timestamp: 3723.670410, Cookie: 247041080095151144163047015184012177025206140010193204189007
[2020.01.11-12.58.14:837][ 38]LogHandshake: SendConnectChallenge. Timestamp: 3723.670410, Cookie: 247041080095151144163047015184012177025206140010193204189007
[2020.01.11-12.58.14:838][ 38]LogHandshake: SendConnectChallenge. Timestamp: 3723.670410, Cookie: 247041080095151144163047015184012177025206140010193204189007

All funcom need to do is reach out to me and i can share it with them so it can get patched.

Man, you’re talking with the wrong one here, I’ve reported several game breaking bugs, very long time ago, and they are still in the game.

@Ignasi

Can you take the time to read over the last few comments please and respond. it’s really important.

Hey @JayCee

We’ve sent you a DM. You can also send one to us by clicking on our username and selecting “Message”.

1 Like