What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Authentication failed, failed, failed, failed, failed, failed...

Status
Not open for further replies.
Bossland said:
It seems that with all effort put into fixing the issue, the issue gets only bigger.

And even if i say, that i am sorry, it would not really matter, because what happens is totally irresponsable. And should have never happened. But it did.

The other problem is that we are very limited with developers and times that the developers can spend on the Nav and Auth issues. And if it was easy to find more, i would have done that.

You will see the auth bugging at least few more days, do not hope that it gets better over the weekend, there is no one here to fix it over the weekend.

If you do not want to be stressed, restarting your Bot twice a hour for the next few days, please stop it. And wait until, if ever, we come with an reliable solution for that issue.
Click to expand...

Scary but seems that Blizzard may be getting close
 
@Bosslands comment

I understand that you guys got few developers though I think that you should prioritize this issue.
Is there really something that needs a more urgent fix at the moment in the buddy bots community?

Edit:

Please disable the authentication server until it's fixed. Let us bot unlimited on the keys, why not?

The only bad thing for the buddy team is that people can share their keys, though that would not work as soon as you enable the auth servers again!

Maybe you would still need to authenticate the keys but give them unlimited sessions. satisfy your customers! :/
 
Last edited:
[17:33:08.427 N] Demonbuddy v1.0.1094.279 started
[17:33:09.698 N] Logging in...
[17:33:10.199 N] Authentication failed!
[17:33:12.895 N] Logging in...
[17:33:13.166 N] Authentication failed!
[17:33:13.869 N] Logging in...
[17:33:17.141 N] Authentication failed!
[17:33:17.592 N] Logging in...
[17:33:17.872 N] Authentication failed!
[17:33:18.314 N] Logging in...
[17:33:18.599 N] Authentication failed!
[17:33:18.968 N] Logging in...
[17:33:19.242 N] Authentication failed!
[17:33:19.593 N] Logging in...
[17:33:19.865 N] Authentication failed!
[17:33:20.242 N] Logging in...
[17:33:20.515 N] Authentication failed!
[17:33:20.879 N] Logging in...
[17:33:21.149 N] Authentication failed!
[17:33:21.630 N] Logging in...
[17:33:24.908 N] Authentication failed!
[17:33:26.643 N] Logging in...
[17:33:26.915 N] Authentication failed!
[17:33:27.331 N] Logging in...
[17:33:27.606 N] Authentication failed!
[17:33:27.806 N] Logging in...
[17:33:28.075 N] Authentication failed!
[17:33:28.448 N] Logging in...
[17:33:28.734 N] Authentication failed!
[17:33:29.043 N] Logging in...
[17:33:29.330 N] Authentication failed!
[17:33:29.672 N] Logging in...
 
[14:59:35.676 N] Logging in...
[14:59:35.908 N] Authentication failed!
[14:59:36.860 N] Logging in...
[14:59:37.087 N] Authentication failed!
[14:59:37.980 N] Logging in...
[14:59:38.208 N] Authentication failed!
[14:59:38.926 N] Logging in...
[14:59:39.156 N] Authentication failed!
[14:59:39.774 N] Logging in...
[14:59:40.024 N] Authentication failed!
[14:59:40.608 N] Logging in...
[14:59:43.835 N] Authentication failed!
[14:59:44.659 N] Logging in...
[14:59:44.887 N] Authentication failed!
[14:59:45.559 N] Logging in...
[14:59:45.785 N] Authentication failed!
[14:59:46.342 N] Logging in...
[14:59:46.568 N] Authentication failed!
[14:59:47.159 N] Logging in...
[14:59:47.385 N] Authentication failed!
[14:59:47.992 N] Logging in...
[14:59:48.223 N] Authentication failed!
[14:59:48.792 N] Logging in...
[14:59:49.021 N] Authentication failed!
[14:59:49.586 N] Logging in...
[14:59:49.812 N] Authentication failed!
[14:59:50.370 N] Logging in...
[15:00:09.442 N] Authentication failed!
 
whats weird is that it was working great yesterday but my 2nd bot kept crashing diablo 3 (any one else experience this?). I wake up and i can't log in (auth failed) the 2nd one, but my first bot is still running?! I'm afriad if i stop it, it'll give me a auth failed also, so i'm going to let it run as long as it can
 
harleystcool said:
whats weird is that it was working great yesterday but my 2nd bot kept crashing diablo 3 (any one else experience this?). I wake up and i can't log in (auth failed) the 2nd one, but my first bot is still running?! I'm afriad if i stop it, it'll give me a auth failed also, so i'm going to let it run as long as it can
Click to expand...

Same thing here, I have one bot that errored out over night, and is getting the "failed" message, but the other is running. Going to leave it running as long as I can.
 
:3 It was working great this morning, but now I haven't been able to log in for the past 6 hours... I've had auto mouse clicker click on the login button for over 11000 times, every 2 seconds it clicks the login button. My login attempts log is over 300mb big at the moment.. :(
 
thampz said:
:3 It was working great this morning, but now I haven't been able to log in for the past 6 hours... I've had auto mouse clicker click on the login button for over 11000 times, every 2 seconds it clicks the login button. My login attempts log is over 300mb big at the moment.. :(
Click to expand...

Personally i would say with over 2300 views on this one post means that a lot of people are having this issue. Hopefully someone who runs this thing will wake up soon and say OH SHIT! Better try and fix this quick..
 
hairymexican said:
Personally i would say with over 2300 views on this one post means that a lot of people are having this issue. Hopefully someone who runs this thing will wake up soon and say OH SHIT! Better try and fix this quick..
Click to expand...
I'm not complaining but they said it wouldn't affect so much on the authentication if at all.. But I dno if its just me for not being able to log for nearly 6 hours straight..
 
What they could've done, is allow everyone to use hb and db for free (no auth servers), while they're fixing THEIR screw ups
 
Status
Not open for further replies.
Back
Top