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
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