rockmaster007
-
Posts
5 -
Joined
-
Last visited
Posts posted by rockmaster007
-
-
Here is a note in the installation doc: Note: you will need a custom client launcher (not provided) to connect to master branch server. what does this mean?
-
Hi Everyone,
Running win 10, Trinitycore Master 8.3.0.34601 and client version to match.
followed the following procedure for the client setup. https://trinitycore.atlassian.net/wiki/spaces/tc/pages/74006268/Client+Setup
I can't for the hell of me, understand why the client is not using the modified config.wtf pointing to 192.168.2.26. (my internal IP)
I've confirmed with wireshark that my client is trying to talk to 69.28.191.24 with port 1119.
I know it's a client issue, since I used another instance using client version 7.3.5 and I see the connection come in on my server, but getting a message incompatible version (which is normal)
Any help would be appreciated.
Regards
-
On 3/17/2020 at 1:47 PM, bnblood said:
Fantastic work!
Not sure what is going on - I tried just about everything I could think of. Client does not indicate Trinity - ever. Using 8.3.0.33528 - (with 8.2.0 it did indicate trinity, but never able to log in - endless loop).
Client matches core. Compiling went great. DB up to date and matches client / core. Great instructions! LAN - client and server on same machine - (Win10). Firewall off.
Not internet connected - don't ever plan to be. Get message BLZ...1016 disconnected.--------------------------------
MySQL - two mirror users / db (tried also with just one root user)Realmlist auth table:
a.) Local Instance MySQL31, user: root, pass: *****, localhost:3306
'1', 'Trinity', '127.0.0.1', '127.0.0.1', '255.255.255.0', '3306', '0', '0', '1', '0', '0', '33528', '1', '1'b.) Trinity, User: trinity, pass: trinity, 127.0.0.1:3306
'1', 'Trinity', '127.0.0.1', '127.0.0.1', '255.255.255.0', '3306', '0', '0', '1', '0', '0', '33528', '1', '1'
also tried for both in the auth table:
'1', 'Trinity', '127.0.0.1', '127.0.0.1', '255.255.255.0', '8085', '0', '0', '1', '0', '0', '33528', '1', '1'----------------------------------------------------------------------
Client config.wtf:
SET portal "127.0.0.1"
SET realmList "127.0.0.1"------------------------------------------------------
BNetServer:
LoginREST.Port = 8081
LoginREST.ExternalAddress=127.0.0.1
LoginREST.LocalAddress=127.0.0.1
LoginREST.TicketDuration=3600MySQL
LoginDatabaseInfo = "127.0.0.1;3306;trinity;trinity;auth"(crashed when I tried 8081 or 8085)
It looks like it's working:
Using configuration file C:/Trinity/Build/bin/RelWithDebInfo/bnetserver.conf.
Using SSL version: OpenSSL 1.1.1d 10 Sep 2019 (library: OpenSSL 1.1.1d 10 Sep 2019)
Using Boost version: 1.66.0
Automatic database updates are disabled for all databases!
Opening DatabasePool 'auth'. Asynchronous connections: 1, synchronous connections: 1.
MySQL client library: 5.6.47
MySQL server ver: 5.6.47-log
Connected to MySQL database at 127.0.0.1
MySQL client library: 5.6.47
MySQL server ver: 5.6.47-log
Connected to MySQL database at 127.0.0.1
DatabasePool 'auth' opened successfully. 2 total connections running.
Started auth database connection pool.
Loading IP Location Database...
Login service bound to http://0.0.0.0:8081
Added realm "Trinity" at 127.0.0.1:8085.------------------------------------------------------------------
WorldServer: (I have tried all combinations of this with all of the root\admin and all the port numbers - doing this does crash it completely.)This works:
LoginDatabaseInfo = "127.0.0.1;3306;trinity;trinity;auth"
WorldDatabaseInfo = "127.0.0.1;3306;trinity;trinity;world"
CharacterDatabaseInfo = "127.0.0.1;3306;trinity;trinity;characters"
HotfixDatabaseInfo = "127.0.0.1;3306;trinity;trinity;hotfixes"WorldServerPort = 8085
InstanceServerPort = 8086
BindIP = "0.0.0.0"
World initialized in 2 minutes 21 seconds
TC>TrinityCore rev. unknown 1970-01-01 00:00:00 +0000 (Archived branch) (Win64, RelWithDebInfo, Static) (worldserver-daemon) ready...------------------------------------------------------------------------
Thoughts?
Same here and looking at the wireshark, i see my client trying to connect to blizzard server with port 1119, even if the config.wtf is changed to 127.0.0.1 or 192.168.2.26.
-
On 2/6/2020 at 8:16 PM, Vandam said:
Would anyone have a Client Link for Legion 7.3.5 and/or client link for 8.2.5 they are willing to share?
(also is their a way to get the 7.3.5 Trinitycore Source as the one on the site is 8.2.5)
Thanks been looking for it a while.
did you find the 7.3.5 client? I can provide it. i'm looking for 8.3.0.34601
Stuck at connected / infinite loop / login issues / battle.net
in Help and Support
Posted
Hi Sevy,
Same issue here, what fixed your issue?
Regards