You requested this, so here’s how I resolved the issue. I’m not sure you’ll grasp or even read it, but here’s the process: I fixed the problem by going to my Neighbour’s house to borrow her GPU. I right-clicked the D2R icon, selected properties, opened the file location, and double-clicked on blz-log.txt. Then, I scrolled to the very end where it stated:
END: Presence Fields After Notification
5/28 00:58:24.901 [line.m_sourceName.c_str()/3] [:0]: TLS Handshake failed. Error code 2
5/28 00:58:38.153 [D2BackendServices/4] [<>:0]: D2BackendServices: error: 666 Error Source: 0 Error Value: 666 String: An issue occurred while communicating with the game servers. Please check that you are connected to the internet and try again.
I researched ‘TLS Handshake failed. Error code 2’ to understand what the error code was. The TLS handshake is an essential process at the start of every HTTPS connection. In this handshake, the client (typically the web browser) and the server (which hosts the website) authenticate each other and set the parameters for the encrypted connection. The following occurs during the TLS handshake:
- Authentication: The server validates its ownership of the asymmetric public/private key pair, confirming to the client that it is connecting to the legitimate entity.
I read further, but my focus was on Authentication.
Next, I researched the 666 error, and you’re going to love what it said. Check the link below for details.
(Failed To Authenticate)
The code in question acts as a safeguard for Blizzard by blocking outdated hardware. Any workaround for this code is likely to be disabled in the next patch. Deleting the ClientSdk is a potential solution, but it only works if you have multiple devices receiving the same 30-day notification. You must delete it from your computer’s internet settings. After deletion, restart the Battle.net app without launching any games, then check the other device where you wish to play Diablo 2: Resurrected. The message may disappear, though this is not guaranteed for all cases.
(bearing in mind that my files are not hidden)
ok after finding this out I went to the libcef.log
local disk > user > username > Appdata > local > Battle.net > logs,
then went to last libcef.log with today’s date scrolled thought the log to the last entry on opening D2R and this is what it said
[0528/005659.166:ERROR:gpu_init.cc(523)] Passthrough is not supported, GL is disabled, ANGLE is
all other logs say the same since 25 Feb 2024
After discovering this, I attempted to adjust the GL setting in the NVIDIA control panel’s Manage 3D settings, but the same error persisted. Needing a break, I decided to grab a beer or two. On my way, I encountered my neighbor, who suggested I try a different GPU. I hadn’t considered this; despite remembering I had built her a computer with a 3060 GPU and tested it before handing it over. It dawned on me that I had overlooked swapping out the GPU, which, as it turned out, resolved the issue for me.
It won’t work for everyone, but I hope that helps to clear things up for you.
Again, thanks for your help
To clarify, I researched my GPU, which I and others reading this post are aware of. I searched for the VRAM of the Gigabyte WindForce GTX 1050Ti 4GB, and the answer was clear. Then, I looked up the VRAM needed to run D2R and found my answer as follows:
Diablo 2 Resurrected System Requirements (Minimum)
- CPU: Intel Core i3-3250 / AMD FX-4350 or better
- RAM: 8 GB
- VIDEO CARD: NVIDIA GeForce GTX 660 2GB or AMD Radeon HD 7850
- DEDICATED VIDEO RAM: 2048 MB
- PIXEL SHADER: 5.0
- VERTEX SHADER: 5.0
- OS: Windows 10 64-bit
- FREE DISK SPACE: 30