Our server techs have been investigating an issue with Teamspeak 3 servers over the past week and have found a fix to avoid exploitation of a bug in the previous version we were using. There will be approximately a five (5) minute outage while the techs upgrade TS3 servers to the newest version and upgrade our locations to avoid this. :)
Australian locations will be updated at 2PM EST (so if you're on an Australian server and saw a hiccup, that's why).
European locations will be updated at 10PM EST.
North American locations will be upgraded tomorrow morning (I don't have a definite time yet).
This should resolve the issue some users have been experiencing with the query port of their TS3 servers being wonky, as well.
Are you getting an error when you try to use the widget? They were working properly again as of this post.
Have you added these permissions to the server? http://guildlaunch.uservoice.com/knowledgebase/articles/437834-why-won-t-the-ts3-widget-show-my-ts3-server-inform
this is my forum mutiny-inoch.guildlaunch.com/ I have my TS3 there and my friends ventrilo there. TS3 worked for about 10 minutes today then quit. 99.3% of the time it is always down. my ts3 info is mutiny-inoch.typefrag.com:9265.
As I stated today it was up total 19 minutes then gone again
It's not that it isn't a priority, I've just been having some difficulty recreating it and it's off-hours support (I monitor the forums on nights and weekends as well, but I'm not on as often).
What happens when you use the IP address instead of the hostname for the server?
Our new guild site of hallowed swtorhost com is also experiencing this issue. We double checked the settings for remote query, they were already added for previous site and works. We tried IP as well as hostname in the Teamspeak3 widget. Any help would be greatly appreciated.
We get our teamspeak server from typefrag directly. It also went back to not working. As tech professional I suggested percussive maintenance. We know this is a game and sometimes things happen :) We are certainly not in a panic about it, at this point I am just really curious as to why its happening. I'll see if it works around the same time it did before, try and see any pattern in when it decides to show up and when it says it can't connect.