Adding nginx in front of the web query is not an issue for people who host their own servers.
I wonder how it is going to be for those who rent a TeamSpeak server?
we did not make further performance improvements with 3.12.0.
But if you are in a generous mood, could you please send @TS_Chris a small summary on how to replicate the 100% spikes so that we can better diagnose the issue?
I cant contact him sadly
You can still contact me, but apparently the easy access method is gone when you hide your public profile (the forum software is a bit weird in that regard it seems). You’d have to go to your own message center and write a new message there, where you have the option to add recipients.
Do you have a script/bot running which sends a lot of commands and what commands are these?
Ps 3.11.0 discussion should be done in https://community.teamspeak.com/t/teamspeak-server-3-11-0
I wrote you a private message 
I’d prefer native https aswell.
My server crashed after using new http API.
Logs and crash dump please?
It does crash is not much detail for us.
I don’t know where to upload on this forum.
Thanks. Forwarded it to our developers.
I will report back then.
Meanwhile we suggest that you use version 3.11.0.
How can I have 3.11.0? I am connected on the server I see 3.12.0-beta1. In logs is 3.12.0-beta1, and I can run the http API.
The server works fine when http is not enabled?
I misunderstood that. Thought it always does crash.
In that case do not enable http and wait for our response. Ignore the 3.11.0 part.
2 Likes
Works fine.
One thing that I forgot to mention
I created new key apikeyadd scope=manage lifetime=0
I send command curl -H 'x-api-key: BAD7xraIzreMuY8EVylb8GyCRmpDWEF53IwLa72' 'http://api.mydomain.tld/gm?msg=Hello+World'
Server crashed. After restart the API key still exists in apikeylist, but when I try to use it the key is invalid. Still exits but is invalid after the crash.
Could you please download the 64 bit version again and start a fresh server for tests?
Something is wrong with attached crashdumps. They seem to be created with a 32bit system/binary but should be 64bit.
Maybe files in server are mixed up and caused whatever happened there.
The api key is stored in the database soon it was created. the only way to make it invalid then is a broken database.
After re-update it seems all good. So probably I am only idiot and I messed up the first installation.
We can reproduce the crash but not that the key is invalid after the server did crash.
Maybe this is not relevant at all after the fix.
Meanwhile do not hammer in the same commands to fast to avoid the crash.
2 Likes
We just released a new beta version (updated Download and docker command in main post).
This one does fix the crash and an issue with the whitelist.
And we removed the POPCNT check form any Linux, MacOS and FreeBSD. It’s only needed for Windows.
2 Likes
