ZombieTwiglet

I hadn’t thought of that, putting the external address works. How very strange.

Debian 6
PHP 5.3.17-1~dotdeb.0 with Suhosin-Patch
Lighttpd 1.4.28-2
TS3 x64 3.0.6.1
WordPress 3.4.2
Webviewer 1.2.1

Self hosted, can connect to TS3 via telnet (from localhost and externally) using the same details.

Just enabled debugging and error reporting and this is the dump:

Warning: fsockopen(): unable to connect to tcp://localhost:10011 (Connection refused) in /var/www/blah/public_html/wp-content/plugins/devmx-teamspeak3-webviewer/lib/devmx/Transmission/TCP.php on line 106 Fatal error: Uncaught exception 'RuntimeException' with message 'Cannot connect: Establishing failed with code 111and message Connection refused' in /var/www/blah/public_html/wp-content/plugins/devmx-teamspeak3-webviewer/lib/devmx/Teamspeak3/Query/QueryTransport.php:114 Stack trace: #0 /var/www/blah/public_html/wp-content/plugins/devmx-teamspeak3-webviewer/lib/devmx/TSWebViewer/TSWebViewer.php(98): devmx\Teamspeak3\Query\QueryTransport->connect() #1 /var/www/blah/public_html/wp-content/plugins/devmx-teamspeak3-webviewer/lib/devmx/TSWebViewer/TSWebViewer.php(185): devmx\TSWebViewer\TSWebViewer->establishConnection() #2 /var/www/blah/public_html/wp-content/plugins/devmx-teamspeak3-webviewer/lib/devmx/Wordpress/TSViewer/TSViewer.php(247): devmx\TSWebViewer\TSWebViewer->renderServer(Object(devmx\TSWebViewer\RenderOptions)) #3 /var/www/blah/public_html/wp-content/plugins/devmx-teamspeak3-webviewer/lib/devmx/Wordpress/TSViewer/TSViewer.php(193): devmx\Wordpress\TSViewe in /var/www/blah/public_html/wp-content/plugins/devmx-teamspeak3-webviewer/lib/devmx/Teamspeak3/Query/QueryTransport.php on line 114

From what I can see 111 is connection refused, however it works fine over telnet as I mentioned.

Config in use is:

ID 	Configname 	Serveradress 	Serverport 	Queryport 	Username 	Custom icons download 	Country icons 	Caching enabled 	Caching time
	1 	CarmaCraft 	localhost 	9987 	10011 	serveradmin 	Yes 	No 	Yes 	180

Hope that helps!

I’m getting exactly the same issue.

WordPress 3.4.2