Not quite sure what you're disagreeing with. I'm going to assume the part of it not being server-side?
I mean, you're free to disagree if that's it, but that doesn't change the reality that error 132 is a catch-all for a wide range of client-side issues. It happens quite often, and has always been solved on the player's end because of that. What you see as "several people withing a few days" is in fact pretty common same ****, different day stuff. It's even mentioned in the FAQ because of how often it happens for some add-on configuration or cached file to get corrupted. But if you want more, there's the simple fact that if something had changed on the server, the same would have to happen to every players, not just a choice dozen.
Anyway, this guy seems to have found a new solution that worked for him. Maybe it will for you as well, no idea.
https://forum.warmane.com/showthread...=1#post3214276