1 | Allocated new voice client connection at 0x7fed481817c0 1 | Creating VoiceClient instance at 0x7fed48187810 teastart.sh start, trying to connect via TS3 client, and checking the logs, I get more information (IP replaced with 70.70.70.70, sever IP replaced with 99.99.99.99): teastart_minimal.sh and connecting via TS3 client, I only get this (IP replaced with 70.70.70.70): With or without enabling experimental_31 and restarting the server, I cannot join the TeaSpeak server. Once installing SSL certificates, I tried to log in to the server using my TS3 Win7 client (version 3.2.1) with no success. By generating my own certificates, I was then able to connect via the webclient, but with no permissions as the webclient does not support the entry of a Admin Token.
#WIN 7 64 TEAMSPEAK CLIENT DOWNLOAD WINDOWS 7#
Without doing the SSL keychain changes, I was not able to join my own TeaSpeak server using either the webclient or my TeamSpeak3 Windows 7 client. Interestingly, "not being able to bind to 9987" doesn't seem to mean anything, as the server still starts on that port. This happens if I check the logs after running. Additionally, if I stop the server and edit the default_port in config.yml, the port does not change. I tried this on both a brand new ubuntu installation of 16.04 and 18.04, which means that it's not possible that this port is already in use. 1 | Failed to bind to :::9987 (98 => Address already in use)
Make sure to replace with your own domain name!Īfter these commands, the server starts up with the "normal" logs except for one part: Use these for TeaSpeak by editing config.yml and replacing the two instances of certs/query_certificate.pem with /etc/letsencrypt/live//fullchain.pem and certs/default_privatekey.pem with /etc/letsencrypt/live//privkey.pem. The private key: /etc/letsencrypt/live//privkey.pem The public key: /etc/letsencrypt/live//fullchain.pem Once you've obtained the SSL certificates by running through the certbot installer, they will be available at these locations: The certbot command will require you to enter some information manually.
I run my own DNS server but you could do this from DNS providers like DigitalOcean or GoDaddy, too. in the last command should be replaced with the domain name you have configured in your DNS.
#WIN 7 64 TEAMSPEAK CLIENT DOWNLOAD INSTALL#
Sudo apt-get install python-certbot-apache Sudo add-apt-repository ppa:certbot/certbot Sudo apt-get install software-properties-common