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.
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.
Structure for database is non modified and we checked all of it, there is columns and indexes correct way.
Please let me know, when it’s gonna fix it. Permissions also been checked and nothing helps us, on every database from MariaDB that problem occur.
Wouldn’t a WebSocket Server be a better option to go with? Because you can then also have the ability to e.g. use the “servernotifyregister” option… And I think a lot of people would support this idea.
From what i see in shown logs the amount of chars your server wants to create in the column “api_key_hash” is bigger than allowed 40 chars.
When you raise the length for that column to 44 it should work.
Need to discuss this with our server developer.
Update
We will raise the possible value to 44 in the stable release.