I'm getting the same error (Posted on your site). However, I wanted to reply to this specifically.
I've tried it with TS unloaded completely, loaded, but not connected and connected. The same error happens each time.
I can get rid of the warning messages but I figured they'd be useful to diagnose connection issues. It would seem that this issue and others stem from the variance in TeamSpeak servers and how they're configured (i.e. self hosted / rented, for example). In this case, the warning messages work great for my TS setup but they're extremely flaky for a couple others. I need to come up with a better workflow for this as a result. If I fix a case for someone else, it breaks for another person. I'll think on it.Agreed, I've whitelisted my server as well. It's really the best way to go about things IMO. I've just learned to ignore the message, but I do agree it'd be nice to not even see it since there really isn't a problem with it.
I've pushed a small update to address two issues that cropped up that I could actually reproduce on hand. If you installed beta 7 already, you only need to upload the new files. Thank you guys for your patience. We'll get there!