.769 Won't Login - Unable to check for an update

Prior to the release of WoW 6.1 i was using HB .763 because any version higher of HB would not login always giving me the error:

Honorbuddy was unable to check for an update.
Honorbuddy will not be able to update automatically.
Logging in...

I deleted the host file, verified same key listed on buddyauth with no spaces, cycled the router, have all the preq's installed and no applications interfering with HB. Like I said, until Tuesday .763 worked fine but any version above .763 would always give this error including .769.

This is all the log file says. It is the same information reported from every version since .763:

[02:15:08.504 N] Honorbuddy v2.5.12998.769 started.
[02:15:08.884 Q] Honorbuddy was unable to check for an update.
Honorbuddy will not be able to update automatically.
[02:15:08.884 D] System.ArgumentException: Version string portion was too short or too long.
at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)
at System.Version.TryParseVersion(String version, VersionResult& result)
at System.Version.Parse(String input)
at System.Version..ctor(String version)
at Honorbuddy.MainWindow.CheckForUpdate()
[02:15:10.601 N] Logging in...

Any help would be greatly appreciated.

 

if you would, please post a full log as an attachment so we can see whats going on.
[Guide] How to attach your log [Kick]

 

It won't completely log in but here is the log file. Also as previously stated I have verified my key on Buddyauth and was working perfect on Monday. That same key has worked flawless on every version to .763, later versions past .763 produced the same information posted in the log files so was the reason why I stuck with .763 because any other version after it wouldn't work.

 

Here is the log file for .763 that I just logged in with for comparison which has always worked. I know it's not valid for WoW 6.1 release but it does log in fine. Here is that log file.

 

stop giving me old logs. the ONLY version you should be even trying to use is 769 and up.

are you able to get to Home Page - Buddy Auth Portal ?

 

Yes I logged in earlier just to verify my key and the key matches what I always enter to log in to HB. My first post was only the 769 logs. I just wanted you to see that it logs in fine to 763 except for it not being compatiable with WoW 6.1

 

are you sure your not running anything like a software firewall or any other application that might be blocking honorbuddy's access to the internet?

 

My .763 log I attached above shows that it logged in just fine last night but the log for .769 I attached above doesn't. Nothing has changed and no new added software or hardware and HB was running fine Monday, it just would not run any HB version higher than .763.

I do run antivirus and a firewall but I completely uninstalled everything. I also went into msconfig and removed all startup items, stopped all non-essential windows services, fresh hostfile, cycled router, flushed dns, logs into buddyauth fine and verified my key, can log into HB .763 just fine right now aside from it not being able to attach to WoW 6.1, HB .769 won't even log in to the point .763 does.

 

Yes, the post above yours states I flushed the DNS. HB 763 still logs in just fine - just now logged in. Yes it does not work with WoW 6.1 but it does log in. 769 doesn't even get to the point trying to attach to WoW.

Steps I've done:

Fresh Honorbuddy from scratch
Flushed DNS,
New Host File
Cycled Router
No services or applications running that are not non-essential Windows.
No firewall or antivirus running or installed (removed for testing)
Logged into Buddyauth and verified key and no spaces
Ran the installation Wizard
Have nothing running in msconfig
Tried DX9 and DX 11
WoW running in 32-bit
I can't set log file level to diagnostic because it won't get that far to select it.

 

update to the lastest version of honorbuddy please.

 

It is still doing the same thing with .770 - .763 still logs in fine though. I'm more than happy to have you look at it in Teamviewer so you can see .763 works but any version higher won't.

New Steps I tried:

1. Completely formatted and rebuilt the computer.
2. Only installed the Operating System, WoW and HB.
3. .770 will not log in
4. .763 logs in just fine but obviously won't attach to WoW 6.1.

I understand .763 is outdated and will not attach to WoW because it is now 6.1 but it does log in. - .769 and .770 will not log in and even try to attach to WoW.

I'm located Central USA.

 

Here is a new log file for .770 with just Windows, WoW and HB on a fresh Windows installation.

 

Okay, I have ruled the issue to the Belkin N300 router because HB .770 will connect if it is plugged directly into the cable modem and not the Belkin. I went into the Belkin and setup UDP and TCP ports to 5031 but still won't work. As usual, the old outdated .763 and prior versions connects just fine through the Belkin so I guess code changed for authentication from .763 forward.

Everything but HB works through the router

 

Tried everything. HB has never had an issue since 2012 running on this router and even .763 has no issues logging in to authenticate - only .769 and higher it does this. Even adding TCP and UDP ports 5031 doesn't help.

Why does it work with .768 and below just fine but versions higher it doesn't? Was something new added that's jamming up certain routers?

 

we dont support older versions. right now its not working because of the router and thats where the issue is.

 

Yes I understand you don't support older versions (couple weeks old) but the point remains that it worked fine and still works file authenticating and loggin in with .768 and below right this second. When you came out with .769 and above it stopped working so obviously it's not my router and something you changed in buddyauth or the authentication code that is causing the router to not authenticate or it wouldn't work on a 2-week old version.

How can it be my router when it authenticates right now? This isn't just my router - a lot of people are experiencing this same issue and we have all gone through every single step asked of us to no avail.

 

your the only one having this issue. the issue is with your setup, your router. not the bot.

 

I'm far from being the only one - been following the forums and responding to PM's from other users experiencing the same issue.