This is a megathread to collect all reports of issues with the myTS revocation list. Please refrain from creating new topics about this issue and use this thread instead.
It is possible that our revocation server is currently experiencing a brief downtime. If you are affected, please let us know by replying in this thread. Our team will then review the issue and work toward a resolution as soon as possible.
This is the error shown in the TS3 Client
The TeamSpeak server could not validate your myTeamSpeak ID. Some myTeamSpeak related services are not available.
Reconnecting might solve the issue. (it didn't)
myTeamSpeak ID is invalid
This is the error shown in the server logs.
failed to download revocation list - count: 4
rejecting myteamspeakid: revoke list out of date
client is connecting with a invalid or revoked myTeamSpeak ID
Before posting please check:
that you are using the latest TeamSpeak server version
with a mobile hotspot or ask a friend if they can reach out server
→ If it works there, your firewall, router, or ISP is blocking certificate servers
if you are using Docker your Container may not have the same network settings as the host machine. A simple fix could be to use one of these solutions.
Note: this can have the disadvantage that the Container is no longer running disconnected from the Host machine. Please use this with caution or make sure that it is safe to use on your setup.
My TS6 server has been blocking all client connections since April 15. Clients get “failed connection initialization” when trying to join. Everything was working fine until then and it suddenly broke without any action.
I’m running ts6 in Docker on a raspberry Pi 4 (using Box64 emulation).
The logs show :
ERROR |Accounting | |Failed to report default license - connection issue
INFO |ServerLibPriv | |failed to download revocation list
What I checked :
The container is running fine and has internet access (other https connections are working).
Port forwarding and Docker port mapping are correct
Restarting the container doesn’t help
Is anyone else seing this ? Any ideas what I could try, or could this be something that needs to be fixed on the TeamSpeak side?
I’m very certain, that this is a network issue on your end.
In the past we’ve had issues with different regions experiencing downtime while others don’t, but there is only your case we’re aware of now regarding this issue.
