September 21, 20169 yr Pushed a fix for ipv6, however because unraid is not our only install base and it's not fair to burden our other users with disabling ipv6 because unraid doesn't support it, we have made a separate branch on our dockerhub specifically for unraid. edit your template and if the repository field looks like this. you're good to go, if not, edit it to match. best bet for users experiencing issues with cycling log, is to delete existing config and repull the image using the unraid tag. Thanks for the quick fix - it's working now using the new branch
September 25, 20169 yr OK, I'm new to Teamspeak, but not new to Dockers or UNRAID. Just trying to set up a Teamspeak server for my son. Anyhow.. I've attached my config screen. Under deployed ports, it shows PLEXPY which is another container I have installed and working fine. But the TEAMSPEAK shows up in RED. I'm assuming that's a bad thing. Do I need to define the ports? and if so which are the common ports to use for TEAMSPEAK? Thanks Mike
September 25, 20169 yr You can only assign one application per port, if I were you I'd stop the plexpy container and then edit it and change 8181 on the host side to something else and then use TS3 on all the default ports.
September 25, 20169 yr Does Teamspeak use 8181? I think it's just showing what's already in use. After some tinkering, I now have the config page for the container looking like this (I preferred the old container config page look and feel better btw) Also, here are some logs 2016-09-25 19:22:04.239009|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.0.13.4 (2016-08-29 12:39:04) 2016-09-25 19:22:04.239273|INFO |ServerLibPriv | |SystemInformation: Linux 4.4.19-unRAID #1 SMP PREEMPT Fri Aug 26 09:47:56 PDT 2016 x86_64 Binary: 64bit 2016-09-25 19:22:04.239333|INFO |ServerLibPriv | |Using hardware aes 2016-09-25 19:22:04.240141|INFO |DatabaseQuery | |dbPlugin name: SQLite3 plugin, Version 3, ©TeamSpeak Systems GmbH 2016-09-25 19:22:04.240227|INFO |DatabaseQuery | |dbPlugin version: 3.11.1 2016-09-25 19:22:04.240628|INFO |DatabaseQuery | |checking database integrity (may take a while) 2016-09-25 19:22:04.257260|WARNING |Accounting | |Unable to find valid license key, falling back to limited functionality 2016-09-25 19:22:04.696362|INFO | | |Puzzle precompute time: 424 2016-09-25 19:22:04.697314|ERROR |FileManager | |bind failed on :::30033; reason: Address family not supported by protocol 2016-09-25 19:22:04.697376|CRITICAL|VirtualSvrMgr | |Could not start file manager 258 no network port available Here's what my config screen looks like now after some tinkering.. The reason the TEAMSPEAK one is red, is that it's the current config I'm looking at.. when i look at Plexpy's config, it shows as read, and teamspeak is black, so I think that's ok.
September 25, 20169 yr Also, i am still confused on where to find the "Use the command line log to get the privilege" Mike
September 25, 20169 yr It looks like you changed the container port along with the host port (hard to tell because maybe you only changed the name). The app still needs to communicate on (what it thinks is 8181). Always leave container ports alone and only change the host port. Then the outside world communicates with the app via the host port, but as far as the app is concerned is still talking on 8181
September 25, 20169 yr It looks like you changed the container port along with the host port (hard to tell because maybe you only changed the name). The app still needs to communicate on (what it thinks is 8181). Always leave container ports alone and only change the host port. Then the outside world communicates with the app via the host port, but as far as the app is concerned is still talking on 8181 Let me get this straight. I had Plexpy installed and working, it defaults to using port 8181. I installed Teamspeak3 using the same Docker image. What your seeing is just what ports the docker had assigned. When I first installed Teamspeak3, it didn't show any ports being assigned, so I attempted to assign them. I don't see any documentation that shows Teamspeak3 using port 8181 by default anywhere, but I may have missed something. Is that a regular port for Teamspeak3? I will either remove Plexpy or create a new docker if that's the case. Do I need to just start a clean docker image and only install Teamspeak3 on that image? I have ran several dockers on the same image before, I didn't think I needed to do that. Thanks Mike p.s. on my first install attempt, I didn't change anything. (my first screenshot), that's just the way it installed. My second screenshot shows what I attempted to ADD, I haven't changed anything.
September 25, 20169 yr You don't need to... There's a multitude of docker apps that all use the same ports. The way that it works is that you assign a unique host port to each of them, and let them still go on their merry way thinking that they're communicating along what they think they are (in this case 8181) EG: I've got cops installed. It wants to communicate via port 80. Port 80 conflicts with unRaid, so I set the host port to 803. cops still thinks its talking on 80 even though in reality its talking on 803 cAdvisor and dolphin both want to communicate via 8080. I've got one of them set the host port to 8081. Its all by design, and is a great feature of docker being able to resolve port conflicts without modifying the app itself.
September 25, 20169 yr Although, since TS3 runs in host mode, there is no reason to ever allocate any ports for it at all as its going to pick and choose what it wants. Do what CHBMB wants and change the host port on PlexPy to resolve the conflict.
September 25, 20169 yr Ok, Just so you know, I've been working with port mappings and the such for nearly 15 years. I understand the concept, and know how they work and why they are necessary. What you are saying isn't making sense to me, but like you said, just do what CHBMB says. Well, reconfiguring plexpy's port mapping from 8181 to say 8381 doesn't change the port that Plexpy is actually using inside the container, which then requires further modifications, which I wasn't ready to committ to, so I just uninstalled it completely, and uninstalled and removed all the folders for TEAMSPEAK, and rebooted the server. So now, I only have TEAMSPEAK, and it's still ACTING exactly like it was before when I had plexpy running. Here are the logs, the current screen shot, on a FRESH install. The key error below to me is that it says 30033 is not an address supported by this protocol. I'm runing UNRAID 6.2 FINAL. 2016-09-25 20:02:45.527683|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.0.13.4 (2016-08-29 12:39:04) 2016-09-25 20:02:45.527851|INFO |ServerLibPriv | |SystemInformation: Linux 4.4.19-unRAID #1 SMP PREEMPT Fri Aug 26 09:47:56 PDT 2016 x86_64 Binary: 64bit 2016-09-25 20:02:45.527902|INFO |ServerLibPriv | |Using hardware aes 2016-09-25 20:02:45.528882|INFO |DatabaseQuery | |dbPlugin name: SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH 2016-09-25 20:02:45.528954|INFO |DatabaseQuery | |dbPlugin version: 3.11.1 2016-09-25 20:02:45.529543|INFO |DatabaseQuery | |checking database integrity (may take a while) 2016-09-25 20:02:45.544595|INFO |SQL | |db_CreateTables() tables created 2016-09-25 20:02:45.568498|WARNING |Accounting | |Unable to find valid license key, falling back to limited functionality 2016-09-25 20:02:45.970693|INFO | | |Puzzle precompute time: 387 2016-09-25 20:02:45.971751|ERROR |FileManager | |bind failed on :::30033; reason: Address family not supported by protocol 2016-09-25 20:02:45.971816|CRITICAL|VirtualSvrMgr | |Could not start file manager 258 no network port available
September 25, 20169 yr Ok, Just so you know, I've been working with port mappings and the such for nearly 15 years. I understand the concept, and know how they work and why they are necessary. What you are saying isn't making sense to me, but like you said, just do what CHBMB says. Well, reconfiguring plexpy's port mapping from 8181 to say 8381 doesn't change the port that Plexpy is actually using inside the container, which then requires further modifications, which I wasn't ready to committ to, so I just uninstalled it completely, and uninstalled and removed all the folders for TEAMSPEAK, and rebooted the server. So now, I only have TEAMSPEAK, and it's still ACTING exactly like it was before when I had plexpy running. Here are the logs, the current screen shot, on a FRESH install. The key error below to me is that it says 30033 is not an address supported by this protocol. I'm runing UNRAID 6.2 FINAL. 2016-09-25 20:02:45.527683|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.0.13.4 (2016-08-29 12:39:04) 2016-09-25 20:02:45.527851|INFO |ServerLibPriv | |SystemInformation: Linux 4.4.19-unRAID #1 SMP PREEMPT Fri Aug 26 09:47:56 PDT 2016 x86_64 Binary: 64bit 2016-09-25 20:02:45.527902|INFO |ServerLibPriv | |Using hardware aes 2016-09-25 20:02:45.528882|INFO |DatabaseQuery | |dbPlugin name: SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH 2016-09-25 20:02:45.528954|INFO |DatabaseQuery | |dbPlugin version: 3.11.1 2016-09-25 20:02:45.529543|INFO |DatabaseQuery | |checking database integrity (may take a while) 2016-09-25 20:02:45.544595|INFO |SQL | |db_CreateTables() tables created 2016-09-25 20:02:45.568498|WARNING |Accounting | |Unable to find valid license key, falling back to limited functionality 2016-09-25 20:02:45.970693|INFO | | |Puzzle precompute time: 387 2016-09-25 20:02:45.971751|ERROR |FileManager | |bind failed on :::30033; reason: Address family not supported by protocol 2016-09-25 20:02:45.971816|CRITICAL|VirtualSvrMgr | |Could not start file manager 258 no network port available pull the latest version of teamspeak3. clearing any appdata for it, making sure you clear the container and image when selecting delete for the teamspeak docker. this issue was resolved in a recent update and is connected with unraid not supporting ipv6 and the version of teamspeak we use updating their config file to use ipv6 as well as ipv4 by default.
September 25, 20169 yr The version I'm running says the IPV6 issue was already corrected: 21.09.2016: Fix problem introduced with latest gsm update and unraid refusal to support ipv6 18.09.2016: Corrected long standing error with network configuration. 13.08.2016: Rebase to ubuntu xenial. 10.09.2015: Inital release I'm using the new Community Applications plugin to manage the App, so I'd prefer not to go away from that. Mike p.s. thanks for all the help from everyone. I'll get there.
September 25, 20169 yr The version I'm running says the IPV6 issue was already corrected: 21.09.2016: Fix problem introduced with latest gsm update and unraid refusal to support ipv6 18.09.2016: Corrected long standing error with network configuration. 13.08.2016: Rebase to ubuntu xenial. 10.09.2015: Inital release I'm using the new Community Applications plugin to manage the App, so I'd prefer not to go away from that. Mike p.s. thanks for all the help from everyone. I'll get there. that's just the changelog, doesn't neccesarily mean you have the latest version. go to the docker tab and click check for updates at the bottom of the page. but you'll have to clear appdata anyways, so it's easiest to do it manually, it doesn't affect anything managed by CA.
September 25, 20169 yr Do what CHBMB wants Glad to see you're finally learning... i've never done what you want and can't condone that kind of advice to anyone, lol.
September 25, 20169 yr Well, reconfiguring plexpy's port mapping from 8181 to say 8381 doesn't change the port that Plexpy is actually using inside the container, which then requires further modifications, which I wasn't ready to committ to, Docker is different to whatever context you're used to port mapping in, as I mentioned before you ONLY change the host port, never the container port,
October 26, 20169 yr Wow you guys are really condescending. I just performed some testing running the latest version of the Linuxserver.io docker container and Indeed your container does not work properly in Unraid 6, doesn't matter if you run in Bridged or Host mode. I've done some testing and it's in fact broken. It's still trying to bind ports to an ipv6 address. 2016-10-26 21:07:39.826425|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.0.13.5 (2016-10-24 11:53:53) 2016-10-26 21:07:39.826525|INFO |ServerLibPriv | |SystemInformation: Linux 4.1.18-unRAID #1 SMP PREEMPT Thu Mar 3 13:08:41 PST 2016 x86_64 Binary: 64bit 2016-10-26 21:07:39.827242|INFO |DatabaseQuery | |dbPlugin name: SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH 2016-10-26 21:07:39.827280|INFO |DatabaseQuery | |dbPlugin version: 3.11.1 2016-10-26 21:07:39.827448|INFO |DatabaseQuery | |checking database integrity (may take a while) 2016-10-26 21:07:39.835827|WARNING |Accounting | |Unable to find valid license key, falling back to limited functionality 2016-10-26 21:07:41.018240|INFO | | |Puzzle precompute time: 638 2016-10-26 21:07:41.019646|ERROR |FileManager | |bind failed on :::30033; reason: Address family not supported by protocol 2016-10-26 21:07:41.019681|CRITICAL|VirtualSvrMgr | |Could not start file manager 258 no network port available 21.09.16: Ipv6 fix for unraid, make separate tag for unraid, other users shouldn't have to suffer because unraid doesn't support ipv6 How do we force the tag, or rather how do we force the docker to run the Unraid 6 version? Your documentation does not specify.
October 26, 20169 yr Add :unraid after the repository so it looks like the below. linuxserver/gsm-ts3:unraid
October 26, 20169 yr How do we force the tag, or rather how do we force the docker to run the Unraid 6 version? Your documentation does not specify. Click edit on the Teamspeak docker and change the Repository to: linuxserver/gsm-ts3:unraid It works fine in both host mode and bridged mode. If you want bridged mode forward these ports: UDP 9987 TCP 10011 TCP 30033 TCP 41114
October 27, 20169 yr How do we force the tag, or rather how do we force the docker to run the Unraid 6 version? Your documentation does not specify. Click edit on the Teamspeak docker and change the Repository to: linuxserver/gsm-ts3:unraid It works fine in both host mode and bridged mode. If you want bridged mode forward these ports: UDP 9987 TCP 10011 TCP 30033 TCP 41114 Thanks for that, I'm still getting an error though. I made sure I checked for updates as well. 2016-10-27 03:24:31.861993|ERROR |FileManager | |bind failed on :::30033; reason: Address family not supported by protocol 2016-10-27 03:24:31.862028|CRITICAL|VirtualSvrMgr | |Could not start file manager 258 no network port available This is the output from; docker logs -f <container-id> tail: cannot open 'ts3server_2016-10-27__03_39_00.063439_0.log' for reading: No such file or directory tail: cannot open 'ts3server_2016-10-27__03_38_56.159691_0.log' for reading: No such file or directory [ OK ] Starting ts3-server: TeamSpeak 3 Server tail: cannot open 'ts3server_2016-10-27__03_39_03.973868_0.log' for reading: No such file or directory tail: cannot open 'ts3server_2016-10-27__03_39_00.063439_0.log' for reading: No such file or directory [ OK ] Starting ts3-server: TeamSpeak 3 Server tail: cannot open 'ts3server_2016-10-27__03_39_07.875871_0.log' for reading: No such file or directory tail: cannot open 'ts3server_2016-10-27__03_39_03.973868_0.log' for reading: No such file or directory [ OK ] Starting ts3-server: TeamSpeak 3 Server tail: cannot open 'ts3server_2016-10-27__03_39_11.777463_0.log' for reading: No such file or directory tail: cannot open 'ts3server_2016-10-27__03_39_07.875871_0.log' for reading: No such file or directory Those files exist in the docker logs directory and have the read attribute set. What my configuration looks like. Thoughts?
October 27, 20169 yr How do we force the tag, or rather how do we force the docker to run the Unraid 6 version? Your documentation does not specify. Click edit on the Teamspeak docker and change the Repository to: linuxserver/gsm-ts3:unraid It works fine in both host mode and bridged mode. If you want bridged mode forward these ports: UDP 9987 TCP 10011 TCP 30033 TCP 41114 Thanks for that, I'm still getting an error though. I made sure I checked for updates as well. 2016-10-27 03:24:31.861993|ERROR |FileManager | |bind failed on :::30033; reason: Address family not supported by protocol 2016-10-27 03:24:31.862028|CRITICAL|VirtualSvrMgr | |Could not start file manager 258 no network port available This is the output from; docker logs -f <container-id> tail: cannot open 'ts3server_2016-10-27__03_39_00.063439_0.log' for reading: No such file or directory tail: cannot open 'ts3server_2016-10-27__03_38_56.159691_0.log' for reading: No such file or directory [ OK ] Starting ts3-server: TeamSpeak 3 Server tail: cannot open 'ts3server_2016-10-27__03_39_03.973868_0.log' for reading: No such file or directory tail: cannot open 'ts3server_2016-10-27__03_39_00.063439_0.log' for reading: No such file or directory [ OK ] Starting ts3-server: TeamSpeak 3 Server tail: cannot open 'ts3server_2016-10-27__03_39_07.875871_0.log' for reading: No such file or directory tail: cannot open 'ts3server_2016-10-27__03_39_03.973868_0.log' for reading: No such file or directory [ OK ] Starting ts3-server: TeamSpeak 3 Server tail: cannot open 'ts3server_2016-10-27__03_39_11.777463_0.log' for reading: No such file or directory tail: cannot open 'ts3server_2016-10-27__03_39_07.875871_0.log' for reading: No such file or directory Those files exist in the docker logs directory and have the read attribute set. What my configuration looks like. Thoughts? Hmmm...give this a try: Instead of changing the repository path on the existing docker, remove the existing docker. Then click 'Add Container', choose the teamspeak3 template and change the repository path there before you click 'Apply'. That should definitely force it to install the correct version...I think Your port settings look fine. If it still doesn't work something might be wrong with the docker and your specific version of unRAID. What version are you running (looks like 6.0 or 6.1)? I'm using 6.2,
October 27, 20169 yr Hmmm...give this a try: Instead of changing the repository path on the existing docker, remove the existing docker. Then click 'Add Container', choose the teamspeak3 template and change the repository path there before you click 'Apply'. That should definitely force it to install the correct version...I think I already tried that, I even changed it in the XML template in dockerMan folder on the flash drive. Blew away the user template, removed the container and image and started from scratch several times.
October 27, 20169 yr Hmmm...give this a try: Instead of changing the repository path on the existing docker, remove the existing docker. Then click 'Add Container', choose the teamspeak3 template and change the repository path there before you click 'Apply'. That should definitely force it to install the correct version...I think I already tried that, I even changed it in the XML template in dockerMan folder on the flash drive. Blew away the user template, removed the container and image and started from scratch several times. Strange. I updated my last post with a question about your unRAID version. I'm using 6.2 and it looks like you're using either 6.0 or 6.1, so maybe it's an issue with one of those versions.
October 27, 20169 yr Hmmm...give this a try: Instead of changing the repository path on the existing docker, remove the existing docker. Then click 'Add Container', choose the teamspeak3 template and change the repository path there before you click 'Apply'. That should definitely force it to install the correct version...I think I already tried that, I even changed it in the XML template in dockerMan folder on the flash drive. Blew away the user template, removed the container and image and started from scratch several times. Strange. I updated my last post with a question about your unRAID version. I'm using 6.2 and it looks like you're using either 6.0 or 6.1, so maybe it's an issue with one of those versions. 6.19, I'll update shortly, see if that makes any difference.
Archived
This topic is now archived and is closed to further replies.