[Main Thread] Error 24004 - Cant join public bounties or T16

So can use T15 just fine. And game says 123 active in T16, but I can’t connect.

Who are these 123 people, and why are they allowed in T16?

same issue here. cant join t16 public bounties

1 Like

blizzard could give a **** about this community…imagine having this happen and trying to hype your next game at the same time…Sure looking forward to this bs in D4…all other servers are working fine…but NA has public games down for over a day now

Just remember something I read yesterday when connection problems started.

So just now I again tried starting the battlenet client “run as administrator” and now I can magically join T16 games.

Thanks for the info.

i cant join any t16 content, t15 is fine. Is there any fix to this problem???

1 Like

Starting battle.net as admin did not work for me, nor running the game as admin. Reinstalling the game also did not fix the issue. A work around would be nice in the meantime Blizzard.

1 Like

its been 12 hours since your post and no update on a game breaking bug?

1 Like

Getting this error/code since yesterday 24004. Any updates on a fix?
Thx

1 Like

error 24004. If look in internet - this error was even at 2021 - i think, if you want to fix it - you already did it. can create game second time! but nothing change - why you take care of gamers so bad? 100% i will newer buy from you any game - because i see quality of your service.

1 Like

T15 works fine. Been doing GR pugs there all day.

It’s been a whole day since this issue started on my end. Any progress?

Not gonna lie, this is kinda rough service coming from a AAA studio like Blizzard. A rather late “we’re aware of the issue” followed by silence doesn’t exactly inspire confidence.

4 Likes

This error code 24004 started for me last night… I swap back and forth between Public normal Rifts, then I do my GRs, then I do public bounties (like everyone else does). The error code started on all bounty games, but I could still join normal public normal rift games. Now its error code 24004 for both public T16 bounties and normal rifts… Its is a pretty a pretty terrible experience for a multiplayer game.

2 Likes

starting to think people need to go start spam @blizzardcs on twitter since its a ghost town here

2 Likes

Since this small indie dev team is having a time getting this fixed, I’ve just been doing Key Warden T16 (since it let me join a public one of those) and we’ve just been doing bounties in it. Not a great work around, but better than nothing I suppose.

2 Likes

Day 2 of 24004 error.

For a company trying to sell me a new game (D4) the effort to fix the error and sell me the new game seems be on life support.

3 Likes

We really need a fix for this ASAP, it is greatly hindering my progress.

3 Likes

same here and do not get response from Diablo technicians

2 Likes

Is there any ETA on this? Any Dev’s / Blizzard Customer Support response on this matter?

2 Likes

Can’t believe this is an ongoing problem and no one is getting a update on the Blizzard Desktop application. Had to dig through forums just to know this is impacting all players across the game.

2 Likes

Look like error code 24004 was happened for Old ID player , my friend join me with new ID is ok , don’t have this issue.
Should I Create new ID and buy Diablo 3 again ??