Danke für deine Antwort :)
Die spammen aber mein Log voll :(
Aber ich nehme dann Mal an das die stabil sind also lass ich das Mal laufen.
Evtl kriege ich das ja hin daß die woanders hin loggen oder ich schalte logging aus.
I run 1.4.3-beta-2 in docker
with the following options:
-Pgeneral.database.url=sqlite://database/TeaData.sqlite",\
"-Pweb.enabled=0",\
"-Pvoice.notifymute=0",\
"-Pvoice.protocol.experimental_31=1
[2019-11-16 17:45:44] [ERROR] 1 | Found varianzes within the server tick! This...
See into the Chat
the Problem is with a default Tea*Speak Certificate ( as far as i understand it)
Use Tea*Speak Client versoin < 3.2.0
so for example 3.1.8 as a work around
Waiting for about 30 min so that Weblist and License works.
After that restarting TeaSpeak-Client
But as soon as that happens the Server Crashes and fails to write crash dumps
thas in logs...
but it seems that it's a problem with Teaspeak after all
i tested it with
1.3.21-beta-4 => problem exists my ip shows up as 172.17.0.1
1.3.19-bet-3 => problem exists my ip shows up as 172.17.0.1
1.3.17-beta-1=>NO PROLBEM my ip shows up as my public ip
I use these Options to Start the binary...
The weird stuff is, that only happens if you use a Tea(m)Speak Client.
Connecting to the port via telnet, curl, wget, Web-Browser shows the correct IP.
But the problem didn't show up beforehand. Did you change anything between 1.3.18 and 1.3.19-beta-3 ?[that is around the time when it first...
Version: 1.3.21-beta-4
Using Docker with the default Network bridge and bridging Ports from Host to Container
Docker Network 172.17.0.0/16 all Connections now resolve to 172.17.0.1:XXXX
[2019-06-28 23:29:21] [INFO] 1 | Voice client 2/XXXXXXXXXXXXXXXXXX= (F4te) from 172.17.0.1:59061 joined...
Also kurz zusammengefasst:
Um Tea*Speak Client 3.2.3 zu unterstützen brauchst du eine lizenz.
Diese wird im protocol_key.txt abgelegt und in der config.yml mit experimental_31: 1 aktiviert (hierzu gibt es viele Anleitungen online, nur kurz suchen)
Und dann je nach lizenz geht es bis zu X slots.