what?
Posts by Belstgut
-
-
have you set encoding correctly in your config?
-
I think I know what the bug is. Gsm doesnt encode the incoming data to utf-8.
I will see if I can fix it.
-
I already have the file.
I do not know if you could send me a tcpdump? for that you need to have access to the server gsm is running on.
You are using the russian version of the game I assume? Since I do not have that version I cannot really test it. so a tcpdump would be very helpful.
sudo tcpdump -n udp -w capture.pcap
leave if it running for a while or at least until you get the error. (try joining with a name which contains © for example)
This error looks like the character is not encoded in windows-1251 but something different.
-
why do you open another thread? I already posted in the other thread what I need to troubleshoot the problem...
-
$message = strtolower($message);
-
As you mentioned in the edit already, the password in the config has to be sha512 hashed.
-
thats just the data part of the message.
The whole message would look like this:
PHP
Display More$msg = [ 'type' => 'request', 'subtype' => 'apilogin', 'id' => 0, // something unique for each request 'data' => [ 'username' => 'myusername', 'password' => 'mypassword', 'token' => null ] ]; // send it $socket->send(json_encode($msg));
This is documented in the General Architecture section of the Document:
https://hackmd.io/s/rJz4eTadG#General-Archite
I would advise to create a method to create messages, such as:
-
The document in the previous post explains all available messages.
What kind of additional info would you like?
-
check your php installation. it seems to be broken. and you shouldnt start gsm as root.
-
it should be something like this: mysql:host=192.168.137.1;port=5432;dbname=anydb
-
well the error says that you cannot connect to the database server. so it is most likely a connection problem or a misconfigured connection string.
#0 /home/XXX/GS/daemon/libraries/database/database.php(168): PDO->__construct('mysql:host=66.7...', 'gs', 'H', Array)
can you check if that host=... string looks correct?
-
"mysqlhost": "66.7",
this doesnt look right. this should most likely be localhost or an ip
-
I believe we could publish the message catalog
edit:
TODO: Add to lexicon
-
Can you post the part of the logfile when the crash occured?
-
I think those notices come from a bug in the api. not from the api calls. Because I always send the token field, even if it is not needed.
And guids are not sent via the api, but found via the mapping in the users.json (apiuser => guid)
The missing secret was probably the cause for the Whoops, something went wrong error.
-
It's only needed if u have a q3 game anyway. if u use frostbite games u wont need it. (at least I haven't heard of a case of guid spoofing there.)
-
You just need the secret key which is written in the users.json if u lose ur phone. You could even write in on a piece of paper so you can set up your authenticator again.
-
The secret gets created anyway. He might want to enable 2fa later on, and then the secret is needed.
-
I have a few errors in the log which indicate that at least 1 user is missing his secret key. Those are needed in the users.json
I'll add a short fix for it when its missing but pls add it.