I've disabled Cloudflare and started using Let's Encrypt

BNETDocs is no longer using Cloudflare for any purpose other than DNS right now, and SSL/TLS has been switched from expired Comodo certificates to Let's Encrypt with automatic renewal.

I felt that this was a better solution due to Cloudflare's security issue last week. With Cloudflare no longer sitting as a middleman, Cloudflare was no longer the edge SSL/TLS, so Let's Encrypt has taken its place.

With Cloudflare DNS only and Let's Encrypt in place, so far things have been steady. This change happened earlier this week and I forgot to announce it. There haven't been any monitoring alerts that have come in since the change, and no one's noticed the difference as far as I've seen, which is a good thing.


USWest Scheduled Maintenance

Blizzard will be performing maintenance to the USWest Classic servers on Friday, March 3, 2017 from 8:00AM to 12:00PM PST.


The following games will be down during this maintenance:

  • Diablo
  • Diablo II
  • Diablo II: Lord of Destruction
  • Starcraft
  • Starcraft: Brood War
  • Warcraft II: Edition
  • Warcraft III: Reign of Chaos
  • Warcraft III: The Frozen Throne

Additionally, the USWest servers are displaying the following EID_ERROR message upon entry to any channel in preparation for this maintenance:

[Server Broadcast] Server maintenance Friday 0800 PST (

| Edited:  Caaaaarrrrlll
BNETDocs and Cloudflare's Memory Leak (#Cloudbleed)

Between September 22, 2016 and February 21, 2017, Cloudflare leaked memory due to a parser bug in three of their features: Automatic HTTP Rewrites, Server-Side Excludes, and Email Obfuscation. A Google security researcher discovered the bug on February 17 and began cooperating with Cloudflare to mitigate and patch the bug.

As of February 21, a patch had been put in place, and on February 24, Cloudflare announced their postmortem on their blog.

BNETDocs uses Cloudflare for their CDN feature and a few other purposes, and due to this, we recommend anyone who has an account here change their password immediately. It's possible that random visitors to this site or others hosted on Cloudflare could have leaked BNETDocs session data and/or password between the time period listed earlier.

The good news is, due to how BNETDocs stores passwords, reusing your password may not be an issue; BNETDocs will reset your seed and hash even if the password is the same as before. Bad news is, most people reuse passwords on other sites, so you should probably use a different password anyway.

- BNETDocs Staff

| Edited:  Caaaaarrrrlll Scheduled Maintenance

Blizzard will be performing maintenance to all Classic regions on Tuesday, February 14, 2017.


Blizzard will be updating the servers to address the @ symbol and its related bugs. Blizzard wishes to emphasize the following notes:

  1. No accounts were harmed during iterations on this subject.
  2. Symbols will once again be available for name creation.
  3. Any cross game profile will appear as #<realm> instead of @<realm> so that they can be handled properly by chat and friend functions*.
  4. Happy Valentine's Day. Blizzard loves you.

*Use the version of the name you see in chat to invoke chat functions.

Region Maintenance Window
USEast, USWest 9:00-10:00 AM PST
Asia 1:00-2:00 PM PST
Europe 3:00-4:00 PM PST

All classic games will be down during this maintenance period.

Editor's note: Blizzard has begun announcing this maintenance across all classic servers via the EID_ERROR chat event with the following message sent upon entering any channel:

[Server Broadcast] Server Restart at 0900 PST (1200 EST) (

In addition, banning in channels is currently broken across all games regardless if they have the @ symbol.

| Edited:  Caaaaarrrrlll
Classic Illy account update

As of this posting, Blizzard has re-enabled the creation of illy accounts on all 4 realms of Classic, with exception to the @ symbol.

The @ symbol has been disabled due to issues with channel banning specifically:

We mistakenly reactivated the ability to create account names with "@". Such names cannot be banned from channels and present other problems for the community.

See Blizzard's original announcement for more info.

Looks like the solution that Blizzard has moved forward with is as follows:

  • Accounts with @ symbols have been deleted and cannot be created.
  • Accounts with "illegal" symbols, with exception to @, remain intact.
  • Accounts with "illegal" symbols, with exception to @, can still be created. For instance, I just created the accounts (((Carl)))@USEast and {Carl}@USEast.

Update Feb 10, 2017: Blizzard has not actually deleted accounts with @ symbols in their name and will be preserving accounts created with them. More info in Clásico's post.


Carl Bennett | |

| Edited:  Caaaaarrrrlll

< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 >