On 12 March, after successfully playing the game for 27 hours (Steam on PC), I received the following error sequence when trying to connect:
“Queued for login - <1 minute left”
" Logging into Battle.net"
“Connecting to Diablo IV Services”
“Queued for login - <1 minute left”
“The lobby server is currently not available. Please double check your version (Code 397000).”
This appeared for the first time after travelling from Oklahoma, where I purchased the game, to my residence in Idaho. This issue has persisted. Blizzard support is unable to offer an answer and directed me to file a bug report.
Before getting into the history of all the troubleshooting steps I have tried, this may be the most important bit: I installed Diablo IV onto a second PC that had previously never had the game installed, and the error sequence is also present on this fresh installation - so the installation-specific troubleshooting steps below were probably in vain.
Troubleshooting attempted:
- Uninstalled and re-installed the game (numerous times)
- Flushed related files from the AppData folder during above efforts
- Uninstalled and re-installed Steam
- Flushed the DNS cache
- Used wired and wireless connections on different ISPs
- Disabled all background applications
- Verified the integrity of all installed files (“All 5237 files successfully validated”)
- Rebooted countless times of course
- Unlinked my battle.net account from my Steam account. Of note, when I did attempt to re-login to battle.net when starting Diablo IV, I observed this:
In the game, when presented with the six-digit code, I selected the button to open the browser
I logged in with my Battle.bet credentials into the browser page
I submitted the code
I received this error: “400: The challenge was created with unsupported parameters and can not be displayed”
After closing the browser, exiting the game and restarting, the account once again appears linked despite this error - I am not prompted to link again.
I also unlinked and attempted to link using the presented QR code with a phone - same result
And as mentioned, performed a fresh install on a different machine only to see the same issue immediately on first attempt to boot the game.
Details of my attempts to resolve this with Blizzard support are available in tickets:
US104058518
US104141207
My theory is that this may be related to a regional issue with battle.net, as the issue immediately manifested when I transitioned to Idaho from Oklahoma.
EDIT***********
When I returned to the region where I purchased the game, it suddenly worked. It worked on VPN as well (with exit nodes in multiple other regions). On returning home, the error was present again. However, if I hop on VPN, I can play. I appear to have been locked out of my home region.