Cannot log into any realm WOW51900328

Same here, everyone else in my guild is online though.
Windows user.

I am one of those cases where trying to connect on linux won’t work but dual booted to windows and it works fine. So I guess it is blizz blocking packets from linux or that look like is coming from linux, which blacklisted a whole lot of users who have been playing using this OS. I gotta say, this is a crappy solution to a DDOS attack… Just blocking all packets from everyone using linux OS!!! There are a lot of real people who play the game from linux, we are not all evil…

This issue is happening cos theirs ddos protection system banned ipv4 addresses or specific packets, many of which is related to real wow players, so someone can log in, someone can’t, i assume …

Actually i think this is ip addresses, cos traceroute not working for me too

Manjaro Linux, playing via Lutris. Same problem: “Logging in to game server” hangs for 2mins and then it shows that I’m disconnected (WOW51900328)

I’m not sure that’s the case. People have reported changing MAC-adress and changing IP (through VPN) has yielded no results.

If Blizzard were running a blacklist on their end you would expect using VPN and or changing MAC would allow you to get in again.

EDIT: didn’t see you mentioning “specific packets” yes this would still be possible, as linux users most likely rely on gnutls for TLS-encryption. Which would be different in Windows. However Windows users have problems too, so it is unclear what they are actually blocking.

Ok i managed to get it working via ipv6 tunnel. (tunnelbroker)

For ubuntu 18, use this script (with your tunnelbroker data)
$ nmcli connection add
type ip-tunnel ifname he-sit
mode sit remote 216.66.86.114 –
ipv4.method disabled ipv6.method manual
ipv6.address 2001:470:6c:dd3::2/64
ipv6.gateway 2001:470:6c:dd3::1

1 Like

Maybe this is the case, i’ve tried vpn yesterday, another IP also from my ISP, and got no results. But how can they filter linux traffic? traceroute does not send any specific linux packets, but still don’t work for me on blizz servers

Can’t connect either (WOW51900328), Archlinux/Lutris
I tried the router reset method, didn’t work. I assume it’s supposed to work by assigning me a new IP, which my provider doesn’t do.
Playing Path of Exile instead

Anyway, i think this case is much simpler, they just banned a lot of ip addresses and subnetworks, i don’t think they have more complicated ddos-protection then that.

This is definitely not the case, because I can log in from Mac, while not from Linux. Same IP both of them.

They didn’t block ip addresses, I can play from windows with the same ip address as when I try to play from linux which doesnt work.

I looked at US forums and pretty much everyone who is complaining there who can’t play are trying to play from linux with a few windows users also affected. It might be that those windows users are behind a linux router or whatever that identify them as linux users and they get blocked that way…

1 Like

Ok, seems very logic, but how then they filter linux packets? Because traceroute program for example send simple requests, which are the same on windows too e.g. udp probe packets to check icmp ttl on hosts, and i am still not getting any trace to their servers, just hardware block

They obviously figured out a way…

My ISP supports IPv6, checking “Enable IPv6 when available” in the Network settings fixed it for me!

Deep packet inspection. When playing via wine, GnuTLS utils are being used - and TLS handshake is unique in this case. (this is from reddit thread)

Problem seems to be back again. Last night problem was gone eventually and I could play normal. Now it doesn’t work anymore. Can’t log in to any servers sigh…
I am windows user, using 4G mobile internet router…

Thanks a lot for this, it fixed it for me too. Just registered on tunnelbroker, set it up as explained on the Arch wiki (google it), set WoW to use ipv6 in the options and it works!

Thank you! This seems to have solved it for me as well…!!!

Same issue. Using a IPv6 tunnel with tunnelbroker did not resolve the problem. :frowning:

I use Windows 10 but have the same problem.

4 Likes