urgent help needed. my server will not boot as of today
2025-09-02 15:41:18.304030|CRITICAL|Accounting | |The default license has expired. Please use the latest server version.
using latest beta 6 and already re-generated files - Whats the issue with teamspeak??? Is their callback server not working and we’re not getting service?
Hey - my server was running 24/ since the beta released with no issues.
But as of today I got the message that my folks can’t enter the server anymore - I tried rebooting tre container, regenerating the files but the server always exits with:
2025-09-02 15:53:40.583283|INFO |ServerLibPriv | |SystemInformation: Linux 6.8.0-63-generic #66-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 13 20:25:30 UTC 2025 x86_64 Binary: 64bit
2025-09-02 15:53:40.583613|INFO | | |checking database integrity (may take a while)
2025-09-02 15:53:40.590677|WARNING |Accounting | |Unable to open /var/tsserver/licensekey.dat
2025-09-02 15:53:40.590739|CRITICAL|Accounting | |The default license has expired. Please use the latest server version.
I already use the latest available server files and it still ceises. Whats the issue? I heard teamspeak wants to phone home or ceise to work if it can’t reach teamspeaks licence check server. Is this the problem??
No its not any IP issues or anything network related - server is reachable and has been all the time
Are you sure you are using the lastest version (v6.0.0-beta6)?
If yes the please post the full server log.
i regenerated files using beta6 explitly and it works now. the “latest” menu choice only updates me to beta5 which explains the issue
Hi i just noticed my ts 6 server is down and instantly exits during startup (installed via docker) starting up a new one with latest image results in the same issue. I guess this is due to the license, is there any way to update it manually for the old server? Also i for some reason cannot start new servers with latest beta 
Is there any way to debug? I just know docker exec into bash but as the server instantly exits thats not possible i think
If you start the container non-detached, e.g. docker compose up (without the -d) you will get the container log directly printed to your console, so you can hopefully see why it’s not starting.
didnt use compose
just checked via docker logs, its the license that has expired 
Well, then you can just do the same with docker run. Simply leave out the -d and all the input/output will be mapped to your console.
For the license pulling the latest image should be enough. Just run a docker image pull teamspeaksystems/teamspeak6-server:latest and then the run command again.
ah i found my issue, when i tried starting another one using ts6-server:latest… it didnt pull the new one for some reason. 
Thank you for your help 
I am running the latest beta version with docker compose in a Proxmox LXC. I am using the example-compose-sqlite.yaml (which I renamed to docker-compose.yaml) and when I launch the server using
docker compose -f docker-compose.yaml up -d
the server gets stuck in a reboot loop. I am using “docker ps” to see the status of the container.
I thought it might be because there was no /var/tsserver directory, so I made it myself. This did not work. In the past I just launched the server as an executable, but I want this to be persistent.
docker compose pull
then
docker compose up -d
Always check the container logs using docker compose logs or docker compose logs <service_name> (in this case docker compose logs teamspeak) first. Pretty sure it’s related to the license, so just update your container as @Gamer92000 has already described.
btw: You can remove the docker- suffix from your file, so plain compose.yml, compose-override.yml is enough because compose is a docker plugin since v2.
