Hangs at "Checking Versions" US West

Yeah I am still having issues, it was bearably the first few days but these last two days have been unbearable. Sometimes when I get past checking versions I end up at a “you were disconnected from battle.net. Please reconnect.” message at the character screen and then I have to go back to checking versions and I then finally get in after 15 minutes. Switching to a mule account is completely out of the question half the time. One of my other friends said he is having the same problem, and I have seen a few others complain on discord. Come on blizzard, this has been going on for awhile now and only deteriorating. Its not like I am banned or anything as I can eventually log in, but holy hell.

Hey Blizzard Employee, since your here addressing these issues, may you tap into my situation. Haven’t been able to log in for a few days now. Only thing I’m guilty of is going in and out of games quickly, fast lobbies. I had gotten off for the night, and in the morning, couldn’t get on anymore. Thrilled to play again, deterred by this situation. Any info on my situation would be GREATLY appreciated. Love D2, looking forward to getting on the grind again. Hopefully during my weekend.

if this continues for much longer, I’m going to begin to lose mules, and it will will be a very disappointing experience. I understand this game has a set of security measures that will not be changed, and also that you have no control over my problem, but if you’ll tell me how to “fix” it so I do not lose all of my items on my characters, it will keep me interested in the D2 classic for a bit longer till Resurrected. Which I anticipate will not have these problems.

Issue needs to be fixed

If you buy D2R, you are rewarding their bad behavior AND poor customer care.

I installed D2LOD last night, tried to log on to uswest. It needed to update, got to 90% downloading patch and froze. I closed d2, reopened, stuck at “checking Versions”.

I just tried again today, stuck at checking versions. I tried to connect to USEast, it downloaded and installed the patch, connected without issue.

Tried to connect to USWest and it let me. I am going to sit in a game for a few minutes now. log off, and try to log in again to see what happens.

I remember playing on bnet after the D2R alpha ended and had loads of problems with connecting to USWest.

I had the same issue with the update on USWest, which I documented far up this thread. I also got the update when I logged into USEast. But still could not join USWest (“Connecting…”, then “Checking Versions” hang).

Now seeing [object Object] as an error when I try to post a reply.

Did this still not get resolved? What’s going on, the “checking versions” and “looking fastest server” loop is still a thing.

Are they beta testing D2R on USWest? I hope this isn’t the case going forward. I plan on staying on classic and have no real desire to play D2R.

Surely, this hasn’t been forgotten? This started within the last 6 months. It’s very annoying to keeping having to hit “cancel” to finally be able to connect to the servers.

Hope is not lost.

The “Connecting…” and “Checking Versions” problems still exist.

IMO, if they fix “Checking Versions”, then the “Connecting…” problem will disappear. The system does not connect until it is handed over to a “Checking Versions” opening. After the system determines your version is current, it then passes the connection to the account selection system.

Just bought the game, but yea US West doesn’t work. Playing on East and keep rubber banding. Really dissapointed. Going to have to play offline instead… Dont buy D2 Classic or LOD this if plan on playing US West

Once a bulk of the current D2 player base shifts over to D2:R, I’m almost certain Battle.net play on the original game will become more stable and playable. There’s likely a lot of people who broke out and installed their old copies of D2 to brush the rust off/scratch the D2:R hype itch/prepare for the D2:R launch, perhaps more than Blizzard anticipated which may be overloading the original ~25 year old Battle.net platform.

Me personally, I’m taking a break from the last D2 ladder prior to the launch of D2:R. From the sound of the tattered state of the servers, it was a good decision. :stuck_out_tongue:

Le Bump. Bump. Bumpity bump bump bump.

And here we are in mid August and the problem is still happening. Funny thing, after spending a half hour getting into the game today I was in my first MF run when the warning came up that the server was shutting down in 10 minutes… sometimes you win, sometimes you don’t.

Hmmmm, not even the date is right on this forum. the date is Aug 12, not Aug 6 like the posting date shows.

Did it say how long the server will stay down for?

been able to login and out of accounts no problem now… hopefully they fixed it.

1 Like

It was down about two hours. Afterwards, I have seen no lag or wait times on USWest to get to the login screen. So, they SEEM to have fixed the problem AT LAST !! Let the playing begin…

1 Like

can you check my ip address for me?