JoshYoJoshYo
New Member
- Joined
- Aug 25, 2012
- Messages
- 1,212
- Reaction score
- 3
Not rubbing it in, just stating the facts about my system.
Are you doing ANY trading on the accounts that got locked (d2jsp, third party sites, etc)?
Account gets locked every time i reboot PC and/or reboot router.Solution needed.
- Thread starter dartex008
- Start date
Not rubbing it in, just stating the facts about my system.
Are you doing ANY trading on the accounts that got locked (d2jsp, third party sites, etc)?
nah Josh, I'm suffering this too, and I don't ever use external sites and always do everything supersafe. I even (please don't blame me) don't do 24/7 , lol.
Periodically change Mac iDs, Hardware Id, hell I just tried to format computer and clean install everything.
It happens whenever you have a Ip change, and it wasn't happening before.
I don't know, maybe it is just happening to manually flagged accounts and are saving our asses to be handed whenever they feel like banning, the fact is it is not happening to everybody or we would be seeing a lot more posts in bnet, that's for sure.
Maybe they started checking how many d3 instances are running through a certain Ip and then checking them/flagging them, it could be a damn bug on their side too.
Fact is it is happening, and its concerning. If it is not happening to you, cheers! Enjoy it while you can, 'cause believe me, you don't like waking up to a complete 15 account mess and spending over an hour to put them back on track....daily.
Question: is there anyone on Vm's and DIFFERENT IP'S suffering this too?(I mean, if you have vm's but all your computers/vm's go through the same router, they would have the same external ip unless you were using a ***** service like hotspot or whatever, right?)
We need to start trying to check what is causing this if we intend to solve it!
Well, my point is that if these permalocks does not happen to legit d3 players, it means that bliz detected you as a botter. You must think why it is happening but not about how to temporaly solve it. Because some day (after mainterance) bliz can "fix" it for you. And with current gold prices rebuild of any farm will be very difficult and very risky financially. Though I don't have a solvation for that problem, maybe you need to reinstall your win 1st.
ezpwnd
New Member
- Joined
- Jul 18, 2012
- Messages
- 950
- Reaction score
- 1
Well, as long as it's just a minority to whom this is happening to they won't give a shit. I made a thread about it and described why demonbuddy would need auth-support with objective reasoning. No flames, no shittalking, no "gieb feature plx dev"-thread but a rather mature feature request by a paying costumer. Actually some people were backing me up, +1 the request.
Thread got deleted without any reply from responsibles. I don't know what is more frustrating, the fact that we can't do shit about this or how the community is dealt with at times.
Thread got deleted without any reply from responsibles. I don't know what is more frustrating, the fact that we can't do shit about this or how the community is dealt with at times.
ezpwnd
New Member
- Joined
- Jul 18, 2012
- Messages
- 950
- Reaction score
- 1
I would also pay for some kind of auth-support. Right now all my accounts are just sitting idle not making me money
you already paid for a working bot, right?
there is a plugin by sinterklaas that can do the auth-thing. just that db doesn't support it. auth support is completely up to db-devs. plugin-developers can't do it with how db works atm. so feel free to make another "request"-thread, maybe you have more luck with it then i do.
Actually I'm not so sure it was purposelly deleted, it seems a lot of posts yesterday between 17 cet and 20 cet were erased by the system, like there was some kind of server rollback.
But I already asked if a mod could pop up and say: yes it was deleted or nopes we didn't delete it. Nobody did answer. I think the thread itself was great , constructive , good mannered and beneficial to every user, so it doesn't make sense to me it was simply deleted.
EDIT: So it is now happening to another friend that does not hold a farm but three bots only. He uses Yar like us though. The disease is spreading....
ezpwnd
New Member
- Joined
- Jul 18, 2012
- Messages
- 950
- Reaction score
- 1
It's good that it's spreading, at some point devs will have to pay attention to it.
I reset my password once again yesterday as I thought it MIGHT be related to the server-downtimes (emergency maintenance etc) that has happened to US. This happened again last night shortly after I reset my passwords, battle.net forums had some threads about disconnects/login problems. I noticed that my bots/yar wouldnt care about those server-fuckups and would just try to reconnect all the time. If I check the mails of locked accounts I see that YAR continuuosly tried to reconnect, I received alot of emails from blizz with the "acc locked due to suspicious activity" with a few minute-pattern.
So I took my US bots off last night to dodge those server-fuckups and put them back on today. All are still fine. So maybe this is what is triggering the locks. YAR consistently trying to reconnect when b.net-servers are laggy/fucked up. I know that YAR usually will prevent doing this but well, I saw it happening and took my accs offline a minute later.
Also, some strange thing happened last night. Another sign of how faulty the servers operate at times. When I logged in last night it would take like a minute after initial verification of login-data to actually put me to the default-screen of d3. When I finally reached it I was instantly invited to a party from the account I was logged in with, even though you obviously can't invite yourself. Just one of those strange things you witness at times, lal.
I reset my password once again yesterday as I thought it MIGHT be related to the server-downtimes (emergency maintenance etc) that has happened to US. This happened again last night shortly after I reset my passwords, battle.net forums had some threads about disconnects/login problems. I noticed that my bots/yar wouldnt care about those server-fuckups and would just try to reconnect all the time. If I check the mails of locked accounts I see that YAR continuuosly tried to reconnect, I received alot of emails from blizz with the "acc locked due to suspicious activity" with a few minute-pattern.
So I took my US bots off last night to dodge those server-fuckups and put them back on today. All are still fine. So maybe this is what is triggering the locks. YAR consistently trying to reconnect when b.net-servers are laggy/fucked up. I know that YAR usually will prevent doing this but well, I saw it happening and took my accs offline a minute later.
Also, some strange thing happened last night. Another sign of how faulty the servers operate at times. When I logged in last night it would take like a minute after initial verification of login-data to actually put me to the default-screen of d3. When I finally reached it I was instantly invited to a party from the account I was logged in with, even though you obviously can't invite yourself. Just one of those strange things you witness at times, lal.
Crown
New Member
- Joined
- Jan 15, 2010
- Messages
- 532
- Reaction score
- 1
why should the defs pay attention? it isnt a bot related thing. even if u login urself without the bot u have to resett ur passwort its something at blizz.
So far we can't conclude it isn't bot related crown. I've seen a couple posts in bnet regarding this, in support section, but we can't say they are not botters.
Two things are clear though: it is not happening to everybody, and it is starting to spread. If you have any more information, feel free to share it with us!
And we are trying to determine what the issue is, and try to find a solution. Authenticator support would be one, that would also help with the accounts' security. A lot of work was done by sinterklaas to create a plugin that would auto-authentify but he had some issues that were directly Db related. So, yeah Devs could and should pay attention to what could be a bigger issue down the road, and startworking on a wonderful addition to Demonbuddy.
http://www.thebuddyforum.com/demonbuddy-forum/plugins/63868-plugin-battle-net-authenticator.html
At least I think so...
Last edited:
dandinidan
New Member
- Joined
- Dec 14, 2012
- Messages
- 31
- Reaction score
- 0
I would like to share my experience on this subject as well. Just a small info about me: Running 14-15 bots in 2 diff computers. One running 8-9 and the other running 5-6. Running both EU and Us servers with same account. Usually have all US chars on one comp and EU on the other. I had a few account locks before but last week all my accounts got locked after a power outage at night.
First thing I did was calling my isp and getting a static ip. Most of my accounts were mine and so it was relatively easy to unlock them. Then I experimented with them for a while. After you unlock your account and login in either EU or US the other region still keeps locked. Now when you login to that you get the account locked message again and you are forwarded to account management page. After going back and forth between two computers and regions/accounts I managed to start botting with 2 of my accounts (4 chars) in 2 diff comps (2 EU vs 2 US). But it is too much of a hassle so I tried a different approach on accounts that had phones registered to my friends etc. After I unlocked the account and logged in with the first char (let's say in EU) I logged in with the other char (in US) "from the same computer" and I still got a message saying the account is locked "but" this time at least with the option of secret question. I entered the secret question and it is back to normal now.
So I guess Blizz not only locks the account due to logging from different ip's but also logging from different computer using the same ip. The solution for me was going static ip and using both EU and US version on the same computer. And yes I did go through more power outages and did not have any account locks yet. I hope this helps anyone with similar issues.
First thing I did was calling my isp and getting a static ip. Most of my accounts were mine and so it was relatively easy to unlock them. Then I experimented with them for a while. After you unlock your account and login in either EU or US the other region still keeps locked. Now when you login to that you get the account locked message again and you are forwarded to account management page. After going back and forth between two computers and regions/accounts I managed to start botting with 2 of my accounts (4 chars) in 2 diff comps (2 EU vs 2 US). But it is too much of a hassle so I tried a different approach on accounts that had phones registered to my friends etc. After I unlocked the account and logged in with the first char (let's say in EU) I logged in with the other char (in US) "from the same computer" and I still got a message saying the account is locked "but" this time at least with the option of secret question. I entered the secret question and it is back to normal now.
So I guess Blizz not only locks the account due to logging from different ip's but also logging from different computer using the same ip. The solution for me was going static ip and using both EU and US version on the same computer. And yes I did go through more power outages and did not have any account locks yet. I hope this helps anyone with similar issues.
quadrotony
New Member
- Joined
- Feb 14, 2013
- Messages
- 1,097
- Reaction score
- 1
This is not related quadro. Nothing to do with this problem. Plus, its US only.
reinstalling windows and using fresh client didnt help, for me at least. i also called support(diff ip, said i was an internet club owner and that many of my clients are having this issue with d3), he asked me to delete that folder in program data, but i already tried that and it didnt help either.
I have 4 comps runing bots atm.
Had em on 2 comps before this shit started happening.
And 1 of them had the issue. Every 2nd or 3rd day all accs would be locked up.
Than i removed some of the accounts from that comp, and moved em to other computers, laptops etx.
Now that computer is runing only 6 bots, it was 10+ before.
And again, those 6 accounts got locked yesterday. All other accounts are safe. None got locked, exepct those 6.
I have another comp with 4 bots on the same IP. And that one never had problems. Never locked up or anything.
Other comps are on different IPs again, never had the issue.
The bots i transfered from the comp being locked up, are at this point runing safe at another location, xvered after i unloced em 4-5 days ago. I atm have extra hardware as i was buying extra comps for botting, but as market is dying i didnt fill em with bots. Yet. Doing some crazy LANs tho, before the 1.0.9 hits. Even lazy to monitor existing bots atm, and its rly pain in the ass to unlock em constantly. So next step if those 6 get locked up would be to leave just 1-2 there, and xver all to new comp
But the point here is, it is happening only on the comps that were runing 6+ bots on. Maybe they detect the same IP and lock down for that rason. ISboxer can handle 4 accs per comp, and there no point in dong more. So if you loging 10+ accs from same comp, you are either botting on a machine designed for botting, or you stole bunch of accounts and logging on them. Either way, they should lock it
Or it was just random to hit me comp with most bots runing. I dunno. Will try to xver bots to other comp, and use that one for gaming in meantime
Had em on 2 comps before this shit started happening.
And 1 of them had the issue. Every 2nd or 3rd day all accs would be locked up.
Than i removed some of the accounts from that comp, and moved em to other computers, laptops etx.
Now that computer is runing only 6 bots, it was 10+ before.
And again, those 6 accounts got locked yesterday. All other accounts are safe. None got locked, exepct those 6.
I have another comp with 4 bots on the same IP. And that one never had problems. Never locked up or anything.
Other comps are on different IPs again, never had the issue.
The bots i transfered from the comp being locked up, are at this point runing safe at another location, xvered after i unloced em 4-5 days ago. I atm have extra hardware as i was buying extra comps for botting, but as market is dying i didnt fill em with bots. Yet. Doing some crazy LANs tho, before the 1.0.9 hits. Even lazy to monitor existing bots atm, and its rly pain in the ass to unlock em constantly. So next step if those 6 get locked up would be to leave just 1-2 there, and xver all to new comp
But the point here is, it is happening only on the comps that were runing 6+ bots on. Maybe they detect the same IP and lock down for that rason. ISboxer can handle 4 accs per comp, and there no point in dong more. So if you loging 10+ accs from same comp, you are either botting on a machine designed for botting, or you stole bunch of accounts and logging on them. Either way, they should lock it
Or it was just random to hit me comp with most bots runing. I dunno. Will try to xver bots to other comp, and use that one for gaming in meantime
Thanks for the info Tulka.
I already thought about them limiting the number of accounts per IP, but it would give them lots of trouble because of shared external IP's- students residences, Cybercafes, that kind of stuff comes to mind. If they actually managed to link a computer individual Identificator (mac ID , HDD id, System ID are examples but there are other possibilities) with the IP and proceeding from there it would make sense. It would make vm's and *****s necessary for avoiding future bans, if they ever manage to bring people back into the game. Which would, in the end, reduce the number of botters because of the technical dificulties of setting them properly. And that would be good for serious botters, since right now botting is so easy everybody just do that, sometimes I take a look at support section and I wonder how people with no computer knowledge at all can do botting nowadays. Come'on, you don't know what an Operating System is but you are botting? Sigh.
I formated the whole pc and reinstalled everything from scratch about 3 days ago, and so far the lockout did not happen again.