Really they still haven’t fixed this?
2 Likes
and here we are - does anyone know what they have said about this? Stability of the servers, login problems, now this… hmmmmm
Still having this problem after DAYS.
2 Likes
Well, for an alternative option at this moment, you guys can join T15 public games. It only doesn’t work on T16 public games.
3 Likes
I tried T13 and got the error but T15 does work!
1 Like
Yeah same issue on t16 but other difficulties work.
Error code 24004, Can’t join any public game on any difficulty. Getting the same error code. Can’t play solo there’s a crazy amount of lag.
Having the same issue. Not just Bounties but rift, GR also
Cant join any type of public game. I can create one, but no one appears to be able to join. This is the 3rd day in a row. Is this some kind of tactic to get to reduce sever load so Diablo IV runs better?
ok day 3 now still no fix. still radio silence from devs so at this point I dont know what to do. Whoever is in charge of d3 needs to be replaced though
I’m just here to see if there’s any news about the fix. As said by others, its been 3 days and I still can’t join games. Getting kind of bored playing solo. Now I have had at least one friend who was able to join my game, but I couldn’t join his (or public games).
Right after posting this I was able to get into a public game. Joined a second one to verify. So for me, I’m seeing the issue resolved.
Another update. The public games I can join are greater rifts and bounties, but not regular rift games.
Battlenet launcher loads up.
I can load into menu, but code 3006 over and over.
I only saw 3 ppl in clan playing.
At this time of day there is always 15 or more playing.
Something is wrong with Blizzard telephony.
1 Like
It’s ok. Blizzard is obviously just a small indie company. It’s not like this game is one of the top 10 selling games of all time, requires you to play online, and than breaks to a point where I can’t play it correctly for over 3 days with near radio silence on the issues. It only generated over 2 billion dollars in sales. Surely they just can’t afford the overhead.
For the next two or three weeks (until both D4 beta weekends are over), I would suggest not making any public games at all. There appears to be an unforeseen consequence prior to the D4 beta going into effect that affects the D3 servers ability to create public games on any difficulty. This is especially true of difficulties past T5 and is impossible at T16 and GRs past 70. I have suggested that new servers be bought to handle both D3 and D4 (and potentially D2R), but it takes time to do that. At this time, this would be a stress test of the D3 servers now and the D4 beta servers on both weekends to assess whether those servers would be needed.
I always try to err on the side of being prepped in case these situations come to light. I won’t say ‘I told you so’, but I have a knack of sensing various things and proving they are true. It doesn’t happen very often, so don’t criticize my methods. The franchise is fairly important to me, so I tend to be a bit more sensitive to it.
As far as connection issues, always make sure your connection is stable. If it’s just Battle.net games having issues, remember that they are gearing up for a major event. Refer to my post above for a potential workaround. The servers this month are going to be under tremendous load and strain issues while the beta is happening and being prepped.
T15 works. Was running bounties and GRs with pugs all day yesterday there.
1 Like
It seems only public games are affected by this error code. Code 1 would be both public AND private games, correct? The reason T16 is failing at this point has to do with how many are doing T16. It has to be an overload issue with the hundred of thousands requests for T16 public games at this juncture. Try going private on these requests and see what happens.
That explanation is absurd on its face. Servers worked fine last week during the initial launch of the season. You actually expect us to believe that use has suddenly spiked in week 2? Come on.