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

"You are not authorized to connect to this server"

Shakam

Shakam

Member
Joined
Jan 15, 2010
Messages
274
Reaction score
0
Hello, since a couple of hours i ve been not able to connect to the auth-servers. i didnt changed anything in the password-phrase, so i really dont have an idea whats going wrong there.

im running two bots with areolog and swizz ip. allways went great for me :)

Anyone got a idea whats causing it?

thanks
 
Here is another log
[15:57:36.501 N] Logging in...
[15:57:37.235 N] You are not authorized to connect to this server.
[15:57:37.298 N] Authentication failed!
[15:57:37.298 N] Logging in...
[15:57:38.611 N] Authentication failed!
[15:57:38.611 N] Logging in...
[15:57:57.615 N] Authentication failed!
[15:57:57.615 N] Logging in...
[15:57:58.255 N] Attached to Diablo III with pid: 9920
[15:57:58.271 N] Flashing window
[15:57:58.771 D] Executable Path: C:\dbmonk\Demonbuddy.exe
[15:57:58.771 D] OS Architecture: AMD64
[15:57:58.771 D] OS: Windows 7 64-bit
[15:57:58.771 D] OS Language: German (Germany)
[15:57:58.818 D] Reloading AssemblyLoader<Zeta.CommonBot.ICombat> - Initializing
[15:58:01.130 N] Current bot set to Order Bot
[15:58:01.130 N] Loaded profile [A3 - Inferno]Champion-Hunting 1.3.6 BigRed - Rakkis Crossing South
[15:58:01.209 D] Reloading AssemblyLoader<Zeta.CommonBot.ICombat> - RoutineManager.Reload !THROTTLED!
[15:58:01.209 D] Routines were reloaded. New routine list:
[15:58:01.209 D] Belphegor All-in-One v1.0.1162.284
[15:58:01.224 D] Generic v0.0.0.0
[15:58:01.224 D] GilesPlugin v0.0.0.0
[15:58:01.224 N] Chose GilesPlugin as your combat routine.
[15:58:01.224 D] Forcing profile reload.
Click to expand...
 
so looks like you are logged now?
 
nope, still not working, i tryed it now on a seconds pc, also not working there
 
logged in.

it looks like at least in the log you posted that you managed to log into demonbuddy fine.
 
Yea, they been known for having Auth issues lately, even when they say it's fixed now, it'll happen again... and again... and again... Been going on for couple of weeks now =(

Nothing you can do if you didn't change anything, so it's their end. Other than that, only thing is just try again later.

Here's a good example, yours failed for no reason, and it works on it's own without you doing anything:

[15:57:36.501 N] Logging in...
[15:57:37.235 N] You are not authorized to connect to this server.
[15:57:37.298 N] Authentication failed!
[15:57:37.298 N] Logging in...
[15:57:38.611 N] Authentication failed!
[15:57:38.611 N] Logging in...
[15:57:57.615 N] Authentication failed!
[15:57:57.615 N] Logging in...
[15:57:58.255 N] Attached to Diablo III with pid: 9920

Sometimes mine gets Authentication failed! 5 minutes long before it successfully logs in. Guess their system is buggy.
 
okay, this log is from earlier, i was tryring to show that it first started at this time
when it started it logged in after a lot of trys

now, it?s still not possible to log in
 
zippysticks said:
Yea, they been known for having Auth issues lately, even when they say it's fixed now, it'll happen again... and again... and again... Been going on for couple of weeks now =(

Nothing you can do if you didn't change anything, so it's their end. Other than that, only thing is just try again later.

Here's a good example:

[15:57:36.501 N] Logging in...
[15:57:37.235 N] You are not authorized to connect to this server.
[15:57:37.298 N] Authentication failed!
[15:57:37.298 N] Logging in...
[15:57:38.611 N] Authentication failed!
[15:57:38.611 N] Logging in...
[15:57:57.615 N] Authentication failed!
[15:57:57.615 N] Logging in...
[15:57:58.255 N] Attached to Diablo III with pid: 9920

Sometimes mine gets Authentication failed! 5 minutes long before it successfully logs in. Guess their system is buggy.
Click to expand...

areolog trys to log in for 14 hours now
 
I don't use areolog so not sure about that part or how that setup works. Maybe try logging in manually without any third party software's.
 
zippysticks said:
I don't use areolog so not sure about that part or how that setup works. Maybe try logging in manually without any third party software's.
Click to expand...
^^This.
ditch Arelog, and run Demonbuddy manually. also log into buddyauth and make sure the key listed matches the one your trying to login as.
 
CodenameG said:
^^This.
ditch Arelog, and run Demonbuddy manually. also log into buddyauth and make sure the key listed matches the one your trying to login as.
Click to expand...
The key matches!
Ich trying to login manually for 7 min. now... very strange... ;(
 
Shakam said:
The key matches!
Ich trying to login manually for 7 min. now... very strange... ;(
Click to expand...

Try changing your ip. One time i miss-wrote the key into my auto-relogger, and it spammed the the wrong key over and over trying to connect. Then eventually their system flagged my IP and blocked it from me connecting to it. Took me awhile to realized that I wrote in the wrong key by 1 digit and then it took me awhile to realize that my IP was flagged from connecting to their servers at all. So once I fixed the key, and changed my IP, everything was good to go.
 
add an exception on your firewall and your antivirus for DB and let me know
 
It must be something at your site, i wasn?t at the machine when this happened the first time. i mentioned it hours later via team viewer. whats else can we do to fix it?
 
could you please give me a new key or something... i need a little progress here... ive got bot addiction
 
You must log in or register to reply here.
Back
Top