Unable to join channel. You have joined the maximum number of this type of channel.
3 Likes
I get a similar message occasionally when playing with my VPN enabled. If I exit, disable my VPN, then restart it doesn’t give me the error.
Update: I’ve been getting these now WITHOUT my VPN enabled. And, yes, I did the IPCONFIG, etc. It’s sporadic, sometimes it won’t happen, other times it’ll happen 2-3 times in a row.
I left the game normally, no rifts, etc. left hanging. This is a new problem with D3. Well, new to me at least.
I got the same thing earlier today. Twice in a row. So, I decided to quit the game and do some computer maintenance.
I’m not sure what “cured” it, but this is what I did:
- Quit D3 and ran Scan and Repair from the App. (No repairs needed).
- Did the ipconfig /release, ipconfig /renew, ipconfig /flushdns routine to refresh my network configuration.
- Turned my modem off for 30 seconds and restarted.
- Ran chkdsk /f c:, chkdsk /f d:, chkdsk /f e:, and chkdsk /f f:.
- Restarted my computer to run scan and repair on all my drives.
I’m not sure if I needed to do all this. Or just what I did to correct the problem. But, when I restarted D3, it ran just fine.
Oh, and I was playing on the Americas Region, non-Season. (Not in Season). I was not running a VPN.
Both times it happened to me, I was trying to push Greater Rifts and got in over my head. I returned to town. Since I could not close the Rift and did not want to wait for the timer to expire, I decided to Leave Game. The “crash” would happen when the game tried to put me back on the Menu.
2 Likes
You are aware that you can close GRs now, when you are in a single player game?
No need to leave game.
Same here. eroor 10017 + strange behavior with stats defense when I get into game.
1 Like
same here. error 10017. I have to log in several times before I can play. just happened recently
I tried that the first time. All that happened was Orek introduced himself and started to tell me about the Rifts. (Maybe I should have waited until he finished his dialog?)
1 Like
You probably have to let him talk before the option becomes available.
1 Like
I’ve been getting that Max Channels error recently, as well.
It happened again. This time, all I did was ran the Desktop App and started D3. I didn’t even get to the Game Menu before I got this:
Followed by this:
I have been playing on the Asia server on and off most of the day, and I have not see this once, but I just logged in to the Americas server, and I get the same thing.
I am pretty sure this is a server issue, and they need to fix it on their end. I guess this just means waiting…
2 Likes
Yeah I was on Asia server earlier too and didn’t get it. But just got it now trying to get back on NA.
2 Likes
I tested a few things when trying to log into the Americas server, and found the following:
- When I start the game from the Battle.net app when it is running as a limited user, I get Error 10017.
- When I start the game from the Battle.net app when it is running as Administrator, I get no error.
- When the Battle.net app is already running (either as Limited or Administrator), and I manually launch the game (either as Limited or Administrator) using the -launch command line, I do not get any error.
In case you are wondering, I use this shortcut to launch the game:
C:\Windows\System32\runas.exe /savecred /user:DIII "C:\Program Files (x86)\Diablo III\x64\Diablo III64.exe -launch".
You can also shift-right-click “Diablo III64.exe” and select “run as different user”, if you already have a limited user account set up on your computer.
You would think that if this were a widespread issue, there would be more people coming here to report it. Are you also running the game as a limited user?
No, I don’t have a limited user account.
You mean with the Battle.net app running as Administrator? I did 5x launching the game from battle.net running with regular privileges, and 5x launching the game from battle.net running as administrator.
I got 10017 5/5 times running battle.net with regular privileges, and 2/5 times running battle.net as administrator. Definitely seemed less frequent running as administrator, but it still happened.
1 Like
Yes.
I did not test multiple times to see if I got different outcomes. I will test a bit more, and edit this post in a few minutes.
Edit:
- I tested 10 times as a limited user, and got the error 5/10 times.
- I tested 10 times as administrator, and got the error 8/10 times.
So, it seem to be unrelated to game permissions, after all…
However, after logging into the Americas server, and then logging in to the Asia server I have gotten this error twice now on the Asia server. It does not cause and issues and the dialog just goes away after clicking “Ok”.
1 Like
Yeah I am dealing with this issue too. 
My clan and communities are also slow to join/populate when I first launch the game, even when the error does not occur.
Okay, now this is even weirder. I’m getting 10017 on my main account (TinneOnnMuin#1187) on NA server. But I also have another account with a D3 license (TinneSolo#1978), and I do not seem to be getting the 10017 error at all on that account.
Maybe it’s something that’s specific to certain accounts, that’s why there aren’t widespread reports?
If it was something with DNS, or with the game files, you’d think I’d get it on both accounts. The fact that I don’t get it on my alt account suggests it may be something server-related that is somehow affecting specific accounts?
Possible. I am getting it on all 3 of my accounts, though.
Mine were each purchased several years apart, so there should not be anything in common with them other than having my name attached to them.
Same problem here. At first I was able to log in and played with friends, now I can’t even get in.
Happened to me yesterday but worked itself out after about an hour.
Edit: I just tried to log into the PTR. Plugged in password and everything. Also swapped to asia server, logged in, joined communities.
I’m now able to log into american servers, but still dont have clan or communities.