Barry Zhang Posted January 10, 2022 Report Share Posted January 10, 2022 WorldSocket::InitializeHandler ByteBufferException Invalid string value () found in ByteBuffer occured while parsing initial packet from 192.168.31.13. console print this. anyidea? Link to comment Share on other sites More sharing options...
Askanat Posted January 11, 2022 Report Share Posted January 11, 2022 On 1/10/2022 at 3:47 AM, Barry Zhang said: WorldSocket::InitializeHandler ByteBufferException Invalid string value () found in ByteBuffer occured while parsing initial packet from 192.168.31.13. console print this. anyidea? Hello, I have the same error. I have test to use an other client or update sources but always the same error. Link to comment Share on other sites More sharing options...
Barry Zhang Posted January 14, 2022 Author Report Share Posted January 14, 2022 On 1/11/2022 at 10:55 PM, Askanat said: Hello, I have the same error. I have test to use an other client or update sources but always the same error. you need Arctium WoW Launcher.exe to launch wow.exe and set port wtf like this: SET portal "81.70.95.36:8085" Link to comment Share on other sites More sharing options...
Askanat Posted January 14, 2022 Report Share Posted January 14, 2022 Barry Zhang, I use Arctium Wow Launcher. But i have this error... And also i use SET PORTAL "IP:8085" Link to comment Share on other sites More sharing options...
Psyanide Posted January 21, 2022 Report Share Posted January 21, 2022 TrinityCore branch master rev aa742c8752d35f3d1a216a4a8ac6a4987cc4da7e Compiles and runs fine in both debian amd windows 10. both x64. I am using arctium launcher thingy. when I log in, no matter what settings I put anywhere, I get a we can't log you in with what you just entered. BLZ51900003 I did bnetaccount create test@test test I have tried, when on windows for server and client, 127.0.0.1 and 192.168.1.183 with 127.0.0.1 in all the places... auth.realmlist and in config file LoginREST.ExternalAddress=127.0.0.1 LoginREST.LocalAddress=127.0.0.1 it should allow me to connect, but it does not. also, in config.wtf I have: SET portal "127.0.0.1:8085" but I have tried ports 8085, 8092, 1119... and nothing. 8092 is what I put for LoginREST.Port though I have tried 8086 etc. if I put a wrong IP in config.wtf, such as 192.168.1.100 it will time out and give me another error, so at least I know it is trying to connect to my server. Here is the connection log: 1/21 10:21:03.351 Connection Initialize 1/21 10:21:12.702 Glue Start Login 1/21 10:21:12.702 BattleNet Attempt Logon 1/21 10:21:12.802 BattleNet Front Disconnected 1/21 10:21:12.802 Glue Fatal Error: 3 1/21 10:21:12.810 BattleNet Defer Disconnect 1/21 10:21:17.145 Connection Destroy I have searched all over this site for 2 days, and all I found was 2 bits of info. first was to add the port in config.wtf and the second was nonsense, something about using 192.168.0.x instead of 192.168.1.x but that doesn't seem like it would be a problem. really don't want to redo my network to test that. I have a TC 335a realm running perfectly fine on my linux machine. I can connect. My friend in Canada can connect (I am in texas) so I know it isn't a firewall thing, especially since my windows firewall is disabled. I can give any information requested, except my passwords, of course Link to comment Share on other sites More sharing options...
Psyanide Posted January 21, 2022 Report Share Posted January 21, 2022 I have this exact same problem. Any updates? Did I setup the Arctium launcher incorrectly? it launches the game and appears to use the config.wtf file because changing IP:PORT causes different errors... Link to comment Share on other sites More sharing options...
Psyanide Posted January 21, 2022 Report Share Posted January 21, 2022 (edited) I had this problem. fixed it by removing the port in config.wtf. SET portal "192.168.x.x" instead of SET portal "192.168.x.x:8085" Edited January 21, 2022 by Psyanide Link to comment Share on other sites More sharing options...
Psyanide Posted January 21, 2022 Report Share Posted January 21, 2022 Don't use port in config.wtf SET portal "192.168.x.x" instead of SET portal "192.168.x.x:xxxx" that fixed it for me Link to comment Share on other sites More sharing options...
Recommended Posts