Jump to content
binhex

[Support] binhex - TeamSpeak

125 posts in this topic Last Reply

Recommended Posts

Overview: Support for Docker image arch-teamspeak in the binhex repo.

Application: TeamSpeak - https://www.teamspeak.com/teamspeak3

Docker Hub: https://hub.docker.com/r/binhex/arch-teamspeak/

GitHub: https://github.com/binhex/arch-teamspeak

Documentationhttps://github.com/binhex/documentation

 

If you appreciate my work, then please consider buying me a beer  :D

 

btn_donate_SM.gif

 

For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

Edited by binhex

Share this post


Link to post

Tips I'd like to share:

 

1) the default network type is "host",  make sure you select "bridge" if you are doing port forwarding,  as in screenshot below:

 

MbyKv5t.png

 

These are the listening ports

Default voice port (UDP): 9987

Default filetransfer port (TCP): 30033

Default serverquery port (TCP): 10011

 

 

2)  If you used your privilege key once and want to generate another one,  you need to telnet to the serverquery port 10011

 

Telnet to your Unraid with Putty

Your Host IP:10011

 

You should see the prompt 

TS3
Welcome to the TeamSpeak 3 ServerQuery interface, type "help" for a list of commands and "help <command>" for information on a specific command.

 

 

at the prompt, login with username/password,  to find out the login info,  you need to view "supervisord.log" inside your teamspeak config folder  (you specified this volume mapping during the initial docker setup)

 

------------------------------------------------------------------
                      I M P O R T A N T                           
------------------------------------------------------------------
               Server Query Admin Account created                 
         loginname= "serveradmin", password= "xxxxxxxx"
------------------------------------------------------------------

 

 

To login:

login serveradmin <password>

 

Find out the virtual server ID of the server:

serverlist

 

to generate the privilege key:

use sid=1  (selects the virtual server)

tokenadd tokentype=0 tokenid1=2 tokenid2=0  (Create a new token)

 

 

This is what it looks like:

TS3
Welcome to the TeamSpeak 3 ServerQuery interface, type "help" for a list of commands and "help <command>" for information on a specific command.
login serveradmin password
error id=0 msg=ok
serverlist
virtualserver_id=1 virtualserver_port=9987 virtualserver_status=online virtualserver_clientsonline...
use sid=1
error id=0 msg=ok
tokenadd tokentype=0 tokenid1=2 tokenid2=0
token=[this is your newly generated privilege key string]
error id=0 msg=ok

 

 

Refer to Teamspeak SeverQuery manual here:

http://media.teamspeak.com/ts3_literature/TeamSpeak%203%20Server%20Query%20Manual.pdf

 

 

 

 

 

Share this post


Link to post

After I upgraded today, Teamspeak is not startign anymore. The log is empty, only saying "Exited (127)"  Is there anything I can do?

Share this post


Link to post

After I upgraded today, Teamspeak is not startign anymore. The log is empty, only saying "Exited (127)"  Is there anything I can do?

 

i know what this is, little oversight on my part, wait 30 mins then pull the image down again and you should be ok

Share this post


Link to post

Me three... it no longer starts (Exit 127)

 

The Deluge docker from BinHex was also doing the same thing after an update, but after a few more updates (forced and one update that became available) it now works.

 

So I suspect it's being fixed... hopefully.

Share this post


Link to post

Me three... it no longer starts (Exit 127)

 

The Deluge docker from BinHex was also doing the same thing after an update, but after a few more updates (forced and one update that became available) it now works.

 

So I suspect it's being fixed... hopefully.

 

the fix is in place on github, just waiting for docker hub to build, its being VERY slow today, queued for over an hour and still not kicked off yet, hopefully will be done soon.

Share this post


Link to post

Me three... it no longer starts (Exit 127)

 

The Deluge docker from BinHex was also doing the same thing after an update, but after a few more updates (forced and one update that became available) it now works.

 

So I suspect it's being fixed... hopefully.

 

Update showed up on unraid docker page and has been applied.  She worky now :)

 

Thanks.

Share this post


Link to post

where is ts installed so i can add my licensekey ?

 

there are a couple of locations for TS, namely /usr/share/teamspeak3-server/ and /var/lib/teamspeak3-server/ i have no idea where the licence file goes though as im running un licenced, if you can tell me where abouts it should go then i can either attempt to configure this via command line or symlink it over from /config.

Share this post


Link to post

the licensekey needs to be in the same folder as the .exe

 

ok ive made a small alteration, can you try downloading the latest docker image and then put your licence file in the hosts path for the /config volume mapping, let me know how you get on.

Share this post


Link to post

Have I configured TS3 wrong on my server?

Channels/server properties are reset whenever I update the docker or if I restart server.

No issues using other binhex dockers though... it's quite inconvenient.

Share this post


Link to post

Have I configured TS3 wrong on my server?

Channels/server properties are reset whenever I update the docker or if I restart server.

No issues using other binhex dockers though... it's quite inconvenient.

 

are you setting the channels to permanent via the teamspeak client?, they are NOT permanent by default. ive just done a quick test and can successfully create a new channel, mark as perm, and restart the container, reconnect and see the channel i created.

Share this post


Link to post

Have I configured TS3 wrong on my server?

Channels/server properties are reset whenever I update the docker or if I restart server.

No issues using other binhex dockers though... it's quite inconvenient.

 

are you setting the channels to permanent via the teamspeak client?, they are NOT permanent by default. ive just done a quick test and can successfully create a new channel, mark as perm, and restart the container, reconnect and see the channel i created.

 

Yeah the channels are permanent.

I have to re-enter the private key every time I restart/update things to reclaim server admin. Not sure what I'm doing wrong because your sonarr, sab, plex and couchpotato docker clients are all working perfectly.

Share this post


Link to post

have my server up and running just wondering how do i find out the ip for accessing the server from outside the home network?

Share this post


Link to post

You need to portforward the right port with the ip unraid use.

To check your public ip, just search "what is my ip" on Google.

Share this post


Link to post

You need to portforward the right port with the ip unraid use.

To check your public ip, just search "what is my ip" on Google.

 

So when I have my ip what should i type into my connect tab in teamspeak.

 

I have no problems with connections over my home network but just putting in my ip:9987 to connect doesnt work.

Share this post


Link to post

You need to portforward the right port with the ip unraid use.

To check your public ip, just search "what is my ip" on Google.

 

So when I have my ip what should i type into my connect tab in teamspeak.

 

I have no problems with connections over my home network but just putting in my ip:9987 to connect doesnt work.

You need to port forward some ports on your router. This are the ports

http://forum.teamspeak.com/threads/46486-Teamspeak-3-Server-Ports?p=200519#post200519

Share this post


Link to post

You need to portforward the right port with the ip unraid use.

To check your public ip, just search "what is my ip" on Google.

 

So when I have my ip what should i type into my connect tab in teamspeak.

 

I have no problems with connections over my home network but just putting in my ip:9987 to connect doesnt work.

 

All the relevant ports have already been forwarded.

You need to port forward some ports on your router. This are the ports

http://forum.teamspeak.com/threads/46486-Teamspeak-3-Server-Ports?p=200519#post200519

Share this post


Link to post

awesome! working great. Is there a place where i can put 'query_ip_whitelist.txt' ? because when i put it in the config folder, it doesn't work...

 

I need this file to prevent flood bans...

 

Would be awesome if this could be implemented some how.

 

thanks!!

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.