-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to login to game server! Error code: 1B - Warmane WOTLK 3.3.5 #75
Comments
Setting client to Windows got it to write server system messages in the discord channel but something else is bothering him. 15:26:46.673 [nioEventLoopGroup-4-1] INFO wowchat.realm.RealmPacketHandlerTBC - Successfully logged into realm server. Looking for realm Frostmourne |
ah yeah. Error 1B means there is a login queue in effect. Unfortunately I never wrote support in the bot for it :( |
Fixed by 7ffc62e . Please redownload the release. |
Always use platform=Mac whenever possible. It's likely your account will disconnect or be banned due to failing to respond to Warden requests if using Windows. |
@fjaros Thank you for your swift response. I did a clean mvn build and now I can confirm the queue works on platform=Windows but it gets disconnected after 20 sec or so.
|
@dusancvetanovic i can connect fine with platform=Mac . can you wait a little bit between connections? if you use platform=Windows , you will be disconnected due to warden. |
@fjaros Still no luck with platform=Mac and you say that it works for you on Warmane 3.3.5 08:07:56.813 [nioEventLoopGroup-2-1] INFO wowchat.realm.RealmPacketHandlerTBC - Connected! Sending account login information... |
The protocol for realm (auth) server is the same for TBC and WotLK. RealmPacketHandlerTBC is correct. I can connect to Frostmourne realm with platform=Mac on my account. There was an issue in the past with "Invalid game version for this server" being returned for Mac logins for Warmane realms, however it was fixed by commit 490b79d by computing the proper build hash for the logon proof packet. Are you quite sure you are compiling the latest version? Look at line 167 in RealmPacketHandler.scala file. Maybe debug the bytes it fetches from the buildCrcHashes map. My log:
Notice that in REALM PACKET 0000, we do indeed send the same info (besides account name). |
@fjaros I downloaded the latest release, this is the checksum of the file I have
I think that on mac it gets stuck when trying to connect to the realm server. The second
Windows for comparison gets a full length of the second RECV REALM PACKET
|
Using the same checksum jar, the login for platform=Mac works. At this point I have no idea how to help you since I can't reproduce the issue. I even downloaded the same JRE:
If you want, you can try emailing me your wowchat.conf so I can try to login with your account. I can't see why that would make a difference for invalid game version error but I don't have any other clue. |
@dusancvetanovic Hey did you ever get this solved? I am currently trying to setup my own chatbot on the same server but also get the same message for invalid game version. I redownloaded the latest version, 1.3.8, as mine was 1.3.6 so I figured I'd try the update as a fresh copy to no success. |
@Shulishin It didn't work on my newly created account. I used VPN when I created the account on Warmane so maybe that kinda messed it up (I'm running the bot in cloud hence the different IP). After not logging in for 2-3 days the bot simply started to work and now I have him online for 2 days straight. |
Ok interesting. I'll leave it for a few days and see how I go thank you. I created the account yesterday and today could not log in outside of using Windows Warden (which of course disconnects). I could log in myself as normal but tried running the bot both locally on the same machine as well as on the cloud service I utilise but had no success with either. |
@Shulishin did it work? I think its Warmane issue. Tested it with two new accounts (same ip). Got the same error as you two. Then i tested it with my alt account (with 1 lvl 80 on it, so it has 4 months atleast) and bot connected (it worked). Dont know whats the issue, but issue is there (probably on warmane side). 1. Account with lvl 80 (older account)
2. Account for bot (new account with lvl 7 toon)
3. Account created yesterday (newest account with lvl 1 toon)
|
It's definitely some logic on warmane side. It's very tough for us to guess what it could be since we don't have access to their source code. And warmane don't allow this tool on their servers so they won't be willing to work with us to figure it out. |
@mzelenka I managed to log in for a couple days, but after one too many restarts where it would sit waiting for me to restart the entire bot (another Warmane only thing, bot would reconnect itself on Atlantiss realm), the bot was back to stating it was an invalid game version. This is definitely a Warmane thing. The first time I managed to connect after waiting the 2 days, but it was only a couple days later that it went back to being unable to connect. I have since been unable to reconnect the bot, which was over a week ago, so I have given up. |
Hi, just to clarify, this sometimes works on Warmane? Or it never works? If the account has Premium on Warmane, it'll skip the queue, would that fix the issue? |
There are 2 issues here - Error code 1B (queue in effect) this has been fixed and is no longer an issue. |
Hello fjaros and thank you for creating this tool.
My friend recommended me this project and I wanted to see how it works.
I did everything right and after running the jar it says: Invalid game version for this server!
07:19:41.807 [main] INFO wowchat.WoWChat$ - Running WoWChat - v1.3.8 07:19:42.639 [main] DEBUG io.netty.util.internal.logging.InternalLoggerFactory - Using SLF4J as the default logging framework 07:19:42.650 [main] DEBUG io.netty.util.internal.PlatformDependent0 - -Dio.netty .noUnsafe: false 07:19:42.651 [main] DEBUG io.netty.util.internal.PlatformDependent0 - Java versi on: 8 07:19:42.652 [main] DEBUG io.netty.util.internal.PlatformDependent0 - sun.misc.U nsafe.theUnsafe: available 07:19:42.653 [main] DEBUG io.netty.util.internal.PlatformDependent0 - sun.misc.U nsafe.copyMemory: available 07:19:42.654 [main] DEBUG io.netty.util.internal.PlatformDependent0 - java.nio.B uffer.address: available 07:19:42.658 [main] DEBUG io.netty.util.internal.PlatformDependent0 - direct buf fer constructor: available 07:19:42.659 [main] DEBUG io.netty.util.internal.PlatformDependent0 - java.nio.B its.unaligned: available, true 07:19:42.659 [main] DEBUG io.netty.util.internal.PlatformDependent0 - jdk.intern al.misc.Unsafe.allocateUninitializedArray(int): unavailable prior to Java9 07:19:42.659 [main] DEBUG io.netty.util.internal.PlatformDependent0 - java.nio.D irectByteBuffer.<init>(long, int): available 07:19:42.659 [main] DEBUG io.netty.util.internal.PlatformDependent - sun.misc.Un safe: available 07:19:42.660 [main] DEBUG io.netty.util.internal.PlatformDependent - -Dio.netty. tmpdir: /tmp (java.io.tmpdir) 07:19:42.660 [main] DEBUG io.netty.util.internal.PlatformDependent - -Dio.netty. bitMode: 64 (sun.arch.data.model) 07:19:42.663 [main] DEBUG io.netty.util.internal.PlatformDependent - -Dio.netty. maxDirectMemory: 251396096 bytes 07:19:42.663 [main] DEBUG io.netty.util.internal.PlatformDependent - -Dio.netty. uninitializedArrayAllocationThreshold: -1 07:19:42.664 [main] DEBUG io.netty.util.internal.CleanerJava6 - java.nio.ByteBuf fer.cleaner(): available 07:19:42.665 [main] DEBUG io.netty.util.internal.PlatformDependent - -Dio.netty. noPreferDirect: false 07:19:47.183 [main] INFO wowchat.WoWChat$ - Connecting to Discord... 07:19:47.815 [JDA RateLimit-Worker 1] DEBUG net.dv8tion.jda.internal.requests.Re quester - Received response with following cf-rays: [70461073ed937c70-BEG] 07:19:48.423 [JDA RateLimit-Worker 2] DEBUG net.dv8tion.jda.internal.requests.Re quester - Received response with following cf-rays: [704610768e227c70-BEG] 07:19:48.432 [main] INFO net.dv8tion.jda.api.JDA - Login Successful! 07:19:48.487 [main] DEBUG net.dv8tion.jda.api.utils.SessionControllerAdapter - C reating new worker handle for shard pool 0 07:19:48.487 [main] DEBUG net.dv8tion.jda.api.utils.SessionControllerAdapter - R unning worker 07:19:48.497 [ConcurrentSessionController-Worker-0] DEBUG net.dv8tion.jda.api.ut ils.SessionControllerAdapter - Running connect node for shard Shard [0 / 1] 07:19:48.834 [JDA MainWS-ReadThread] INFO net.dv8tion.jda.internal.requests.WebS ocketClient - Connected to WebSocket 07:19:48.834 [JDA MainWS-ReadThread] DEBUG net.dv8tion.jda.internal.requests.Web SocketClient - Connected with gateway intents: 1100001011 07:19:48.834 [JDA MainWS-ReadThread] DEBUG net.dv8tion.jda.internal.requests.Web SocketClient - Sending Identify-packet... 07:19:48.907 [JDA MainWS-ReadThread] DEBUG net.dv8tion.jda.internal.requests.Web SocketClient - Got HELLO packet (OP 10). Initializing keep-alive. 07:19:49.073 [JDA MainWS-ReadThread] DEBUG net.dv8tion.jda.internal.handle.Guild SetupController - Setting incomplete count to 1 07:19:49.073 [JDA MainWS-ReadThread] DEBUG net.dv8tion.jda.internal.handle.Guild SetupController - Starting 75 second timeout for 1 guilds 07:19:49.256 [JDA MainWS-ReadThread] INFO net.dv8tion.jda.api.JDA - Finished Loa ding! 07:19:49.348 [JDA MainWS-ReadThread] DEBUG io.netty.channel.MultithreadEventLoop Group - -Dio.netty.eventLoopThreads: 2 07:19:49.370 [JDA MainWS-ReadThread] DEBUG io.netty.util.internal.InternalThread LocalMap - -Dio.netty.threadLocalMap.stringBuilder.initialSize: 1024 07:19:49.371 [JDA MainWS-ReadThread] DEBUG io.netty.util.internal.InternalThread LocalMap - -Dio.netty.threadLocalMap.stringBuilder.maxSize: 4096 07:19:49.385 [JDA MainWS-ReadThread] DEBUG io.netty.channel.nio.NioEventLoop - - Dio.netty.noKeySetOptimization: false 07:19:49.385 [JDA MainWS-ReadThread] DEBUG io.netty.channel.nio.NioEventLoop - - Dio.netty.selectorAutoRebuildThreshold: 512 07:19:49.396 [JDA MainWS-ReadThread] DEBUG io.netty.util.internal.PlatformDepend ent - org.jctools-core.MpscChunkedArrayQueue: available 07:19:49.406 [JDA MainWS-ReadThread] INFO wowchat.realm.RealmConnector - Connect ing to realm server logon.warmane.com:3724 07:19:49.495 [JDA MainWS-ReadThread] DEBUG io.netty.channel.DefaultChannelId - - Dio.netty.processId: 24858 (auto-detected) 07:19:49.509 [JDA MainWS-ReadThread] DEBUG io.netty.util.NetUtil - -Djava.net.pr eferIPv4Stack: false 07:19:49.510 [JDA MainWS-ReadThread] DEBUG io.netty.util.NetUtil - -Djava.net.pr eferIPv6Addresses: false 07:19:49.514 [JDA MainWS-ReadThread] DEBUG io.netty.util.NetUtilInitializations - Loopback interface: lo (lo, 0:0:0:0:0:0:0:1%lo) 07:19:49.515 [JDA MainWS-ReadThread] DEBUG io.netty.util.NetUtil - /proc/sys/net /core/somaxconn: 128 07:19:49.516 [JDA MainWS-ReadThread] DEBUG io.netty.channel.DefaultChannelId - - Dio.netty.machineId: 00:16:3e:ff:fe:06:52:b0 (auto-detected) 07:19:49.568 [JDA MainWS-ReadThread] DEBUG io.netty.util.ResourceLeakDetector - -Dio.netty.leakDetection.level: simple 07:19:49.568 [JDA MainWS-ReadThread] DEBUG io.netty.util.ResourceLeakDetector - -Dio.netty.leakDetection.targetRecords: 4 07:19:49.634 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.numHeapArenas: 2 07:19:49.634 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.numDirectArenas: 2 07:19:49.634 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.pageSize: 8192 07:19:49.634 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.maxOrder: 11 07:19:49.634 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.chunkSize: 16777216 07:19:49.634 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.smallCacheSize: 256 07:19:49.634 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.normalCacheSize: 64 07:19:49.635 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.maxCachedBufferCapacity: 32768 07:19:49.635 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.cacheTrimInterval: 8192 07:19:49.635 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.cacheTrimIntervalMillis: 0 07:19:49.635 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.useCacheForAllThreads: true 07:19:49.635 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.PooledByteBufAllocato r - -Dio.netty.allocator.maxCachedByteBuffersPerChunk: 1023 07:19:49.716 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.ByteBufUtil - -Dio.ne tty.allocator.type: pooled 07:19:49.716 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.ByteBufUtil - -Dio.ne tty.threadLocalDirectBufferSize: 0 07:19:49.716 [JDA MainWS-ReadThread] DEBUG io.netty.buffer.ByteBufUtil - -Dio.ne tty.maxThreadLocalCharBufferSize: 16384 07:19:49.766 [JDA MainWS-ReadThread] DEBUG net.dv8tion.jda.internal.handle.Guild SetupController - Finished setup for guild 966078485846167562 firing cached even ts 0 07:20:17.549 [JDA RateLimit-Worker 1] DEBUG net.dv8tion.jda.internal.requests.RateLimiter - Removed 2 expired buckets 07:20:25.547 [nioEventLoopGroup-2-1] INFO wowchat.realm.RealmPacketHandlerTBC - Connected! Sending account login information... 07:20:25.566 [nioEventLoopGroup-2-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.maxCapacityPerThread: 4096 07:20:25.566 [nioEventLoopGroup-2-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.ratio: 8 07:20:25.566 [nioEventLoopGroup-2-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.chunkSize: 32 07:20:25.566 [nioEventLoopGroup-2-1] DEBUG io.netty.util.Recycler - -Dio.netty.recycler.blocking: false 07:20:25.578 [nioEventLoopGroup-2-1] DEBUG io.netty.buffer.AbstractByteBuf - -Dio.netty.buffer.checkAccessible: true 07:20:25.578 [nioEventLoopGroup-2-1] DEBUG io.netty.buffer.AbstractByteBuf - -Dio.netty.buffer.checkBounds: true 07:20:25.580 [nioEventLoopGroup-2-1] DEBUG io.netty.util.ResourceLeakDetectorFactory - Loaded default ResourceLeakDetector: io.netty.util.ResourceLeakDetector@2192631a 07:20:25.602 [nioEventLoopGroup-2-1] DEBUG wowchat.realm.RealmPacketEncoder - SEND REALM PACKET: 0000 - 08 27 00 57 6F 57 00 03 03 05 34 30 36 38 78 00 58 53 4F 00 53 55 6E 65 00 00 00 00 7F 00 00 01 09 52 45 4E 44 50 4F 57 45 52 07:20:25.704 [nioEventLoopGroup-2-1] DEBUG wowchat.realm.RealmPacketDecoder - RECV REALM PACKET: 0000 - 00 00 56 1D 86 78 F8 09 FF D6 A1 D9 AC 83 E6 A7 E3 8E FC 02 30 A3 E1 1D 7A CC 46 02 9E FC A1 BD A1 38 01 07 20 B7 9B 3E 2A 87 82 3C AB 8F 5E BF BF 8E B1 01 08 53 50 06 29 8B 5B AD BD 5B 53 E1 89 5E 64 4B 89 43 BF 2E B5 07 AB 4A 57 E0 D4 AE 07 7D 6E 8E C8 FC 46 0E 58 7C 4D C6 E9 60 E5 9E BB B5 CE E1 A3 BA A3 1E 99 A0 0B 21 57 FC 37 3F B3 69 CD D2 F1 00 07:20:25.742 [nioEventLoopGroup-2-1] DEBUG wowchat.realm.RealmPacketEncoder - SEND REALM PACKET: 0001 - 0C E4 0E F4 85 7E CF F0 D4 AF F1 4A F3 98 68 DD BA 28 72 73 8A 9D E7 FC EF D8 8A A0 FC 6A 2E 7C 5E 97 26 13 0A 5B 1D FA 21 37 A4 49 BC 56 FE 01 F4 F3 71 2C 7C 13 21 A3 5A F8 FD A4 0D FF 88 91 D4 2A D8 4A 2B 02 E5 C5 00 00 07:20:25.778 [nioEventLoopGroup-2-1] DEBUG wowchat.realm.RealmPacketDecoder - RECV REALM PACKET: 0001 - 09 07:20:25.778 [nioEventLoopGroup-2-1] ERROR wowchat.realm.RealmPacketHandlerTBC - Invalid game version for this server!
The text was updated successfully, but these errors were encountered: