Hello, last night blizzard server crashed, I had my mule parked in a game, when I woke up I was kicked from bnet and when I tried to connect back got cd-key in use by myself and later on disconnect. However I can play on my other cd-key with no problem.
This is just a report for blizzard to fix the issue in eu asap, they had same issue on east last week.
Thanks
6 Likes
Same ⦠anyway post here is a useless thing, they wonāt fix anything.
Just wait for the restriction expires. 
Cmon BLIZZ DO SOMETHING DAMN!!! Its same last 3 hours " Your CD key is used by YOU"
(i was in game last night at the crash also)
1 Like
Same thing here⦠Hey Blizzard!! Nice job! right when people os comming back to D2, waiting for the resurrected version, you come up with this kind of stuff⦠SMH.
I was playing early morning and the game crashed, Iāve not been able to log in since, at first it was stuck at finding fastest server to connect too. And now iām stuck with my CD Key is in use by Me⦠All I want to do is enjoy Diablo 2
Itās been like this for a very long time now.
I come back 2 weeks ago, first i get a stupid ip ban for use vpn (when 80/90% pop in the game are bots playing without problems) And now for another reason, i cant play because my cdkey is on useā¦
This going like 24h ban cd key, if not more⦠We will see ^^,
Trash acting from support, they just dont care about us.
Ty blizz for destroy my hype, maybe as legit player when you release d2r i can start play d2lodā¦
Incredible.
Canāt play either⦠stuck at checking versions. Maybe the server is down, i am 100% legit and donāt use any vpn or bot.
Donāt understand.
Any word on a fix? Stuck at āConnecting to the fastest serverā
Same issue here on Mac OS 10.12.6 (16G2136) and 10.14.6 (18G8022).
Last succesful connection was August the 6th.
Now it wonāt continue further than āconnecting to battle.netā āChecking versionsā
Been playing 20 years as well, and Iām a superuser at Mac, so thereās NO error at my end.
Please fix this issue ASAP, as I need to log in to my accouns before they expire!
Hey,
I am stuck since yesterday morning on checking versions.
I have reinstalled D2 et D2LOD. I donāt use VPN or any Hacks so i donāt understand.
I did what Blizzard recommend but nothing happen.
Are the servers working ?
Any idea anyone ?
Thanks !
same for me. Iām on Apple and canāt find a download to reinstall.
Ofc the servers are working, this is not for use vpn or hacks.
You was playing when servers go down right?? For the game we still inside, thats the reason we cant join.
But blizzard seems dont do nothing to fix.
Same issue here on Mac OS 10.12.6 (16G2136) and 10.14.6 (18G8022).
Last succesful connection was August the 6th.
Now it stalls at āconnecting to battle.netā āChecking versionsā
On Friday 6 iāve played last time. Saturday and sunday morning unable to connect.
Iāve played this game for 20 years so i donāt think is my fault.
Iām On Apple iMac running 10.14.6. Tried to find a download for mac but it seems donāt exist anymore. tried to download pc version for bootcamp or wine and the installer ask for a 26 digit key. Iāve here my copy of d2 and is 16 digit key, so donāt work.
I never used bots so, which is your problem?
ps: found the 26 digit key but the windows installer is the 1.14b and battle.net donāt work.
pps: found a connection, only asia realm is on. other realms are down, hacker attack?
Same issue here on Mac OS 10.12.6 (16G2136) and 10.14.6 (18G8022).
Last succesful connection was August the 6th.
Now it wonāt continue further than āconnecting to battle.netā āChecking versionsā
Been playing 20 years as well, and Iām a superuser at Mac, so thereās NO error at my end.
Please fix this issue ASAP, as I need to log in to my accouns before they expire!
This can sometimes happen but it should automatically resolve itself within 24 hours those affected normally, if you check again soon.
If youāre still restricted then your restriction may have been applied for other behaviour, and you can find information here: https://support.blizzard.com/article/000264916
Usually for this kind of connection issue we would advise people to also make sure they follow the steps here first to try and fix it: https://support.blizzard.com/article/000163523