Apoc
Well-Known Member
- Joined
- Jan 16, 2010
- Messages
- 2,790
- Reaction score
- 94
For those of you receiving "Authentication Failed" over and over, this isn't a bug in the application!
First things first, lets make sure that HB/GB actually can contact the servers (yes, this may sound kind of weird, but as the fixes show below; the issue isn't the software itself.)
Log into http://hb.buddyauth.com or http://gb.buddyauth.com from your web browser. (Depending on which bot you're trying to log into)
Can you log in? (Even if it says AUTH BAD, or NOT PAID, then this means you can login [please see other posts on how to resolve AUTH BAD/NOT PAID messages. This is not a thread for them!])
If you cannot log in, you may still want to try the steps below; however, chances are that something is being blocked between you, and our servers.
If you can log in however, then we have already narrowed down the issue!
Chances are, at this point, that you have a firewall, or anti-virus blocking communication from Honorbuddy.exe or Gatherbuddy.exe. This can be anything from just Windows' built in firewall, to your internet security suite.
You need to add an exception into your firewall or anti-virus, to allow HB/GB to connect to the web. Sorry, but I can't help you do this, as every firewall is different. Please Google on how to add an exception to your specific AV/Firewall.
For those more technically inclined, you may perform the following steps to see if there are actually issues connecting to our web servers:
Open up a command prompt and run the following command (replace HB with GB if you're using GB):
If the traceroute doesn't 'die out' then the issue is with your firewall/AV settings.
You can also run
I've added the exceptions to my firewall/anti-virus, but I still can't authenticate, why?
Chances are, you've missed something somewhere, or you may have a router/modem that inspects traffic. Please add an exception in there as well. (Note: This is really only as a last resort. If you don't know what you're doing, please don't modify your router/modem settings!)
Sometimes when I authenticate, it will fail, but sometimes it will go through right away. Why?
Due to DDoS filtering, some traffic is dropped as a side-effect. This is an unfortunate necessity, and there really isn't much that can be done. If you know that you can authenticate most of the time, just try again.
I'll probably be adding more to this, and cleaning it up once I'm more awake, and not quite as busy!
First things first, lets make sure that HB/GB actually can contact the servers (yes, this may sound kind of weird, but as the fixes show below; the issue isn't the software itself.)
Log into http://hb.buddyauth.com or http://gb.buddyauth.com from your web browser. (Depending on which bot you're trying to log into)
Can you log in? (Even if it says AUTH BAD, or NOT PAID, then this means you can login [please see other posts on how to resolve AUTH BAD/NOT PAID messages. This is not a thread for them!])
If you cannot log in, you may still want to try the steps below; however, chances are that something is being blocked between you, and our servers.
If you can log in however, then we have already narrowed down the issue!
Chances are, at this point, that you have a firewall, or anti-virus blocking communication from Honorbuddy.exe or Gatherbuddy.exe. This can be anything from just Windows' built in firewall, to your internet security suite.
You need to add an exception into your firewall or anti-virus, to allow HB/GB to connect to the web. Sorry, but I can't help you do this, as every firewall is different. Please Google on how to add an exception to your specific AV/Firewall.
For those more technically inclined, you may perform the following steps to see if there are actually issues connecting to our web servers:
Open up a command prompt and run the following command (replace HB with GB if you're using GB):
Code:
tracert hb.buddyauth.comIf the traceroute doesn't 'die out' then the issue is with your firewall/AV settings.
You can also run
Code:
ping hb.buddyauth.comI've added the exceptions to my firewall/anti-virus, but I still can't authenticate, why?
Chances are, you've missed something somewhere, or you may have a router/modem that inspects traffic. Please add an exception in there as well. (Note: This is really only as a last resort. If you don't know what you're doing, please don't modify your router/modem settings!)
Sometimes when I authenticate, it will fail, but sometimes it will go through right away. Why?
Due to DDoS filtering, some traffic is dropped as a side-effect. This is an unfortunate necessity, and there really isn't much that can be done. If you know that you can authenticate most of the time, just try again.
I'll probably be adding more to this, and cleaning it up once I'm more awake, and not quite as busy!
