teamspeak-linux-docker-images icon indicating copy to clipboard operation
teamspeak-linux-docker-images copied to clipboard

Error "failed to download revocation list"

Open tomtrix opened this issue 4 years ago • 3 comments

Hy guys,

I tried to setup several versions of this container at my Ubuntu 20.04 LTS and CentOS 7 servers with docker and podman since yesterday. Basically everything works fine incept of the myTeamSpeak connection.

The server log contains following line all the time: 2020-12-31 15:35:19.970290|INFO|ServerLibPriv| |failed to download revocation list - count: 1

At my client (version 3.5.6) I get following errors on my server only: <16:40:34> Der TeamSpeak Server konnte Ihre myTeamSpeak ID nicht validieren. Nicht alle myTeamSpeak Services sind verfügbar <16:40:34> Neu verbinden könnte das Problem lösen. <16:40:35> myTeamSpeak ID is invalid

Debugging already done:

  • Connection to "teamspeak.com" and subdomains with every port is possible (outgoing traffic isn't blocked and no proxy in use) /var/ts3server # wget https://ts3services.teamspeak.com:443 Connecting to ts3services.teamspeak.com:443 (104.22.27.164:443) wget: server returned error: HTTP/1.1 403 Forbidden
  • system time is correct (CET) Thu 31 Dec 2020 04:47:19 PM CET
  • time at the container is correct (CET): Thu Dec 31 16:47:29 CET 2020
  • Test run at two fresh VPS without any services and disabled firewall (hosting providers Contabo and Netcup)

Are your systems, that provide the revocation list, down or is this a bug of the container?

Greetings and have a good start in 2021, Tom.

tomtrix avatar Dec 31 '20 15:12 tomtrix

I have the same Problem! I have tried many:

  • Install ts3 in docker -> wsl2 -> windows

  • directly in windows

  • directly in ubuntu

  • remove all settings

Firewall is okay, last year its working on the same machine and i double check the manual it looks like this issue is not server related? Some new settings ts5 related?

Delido avatar Jan 03 '21 11:01 Delido

Hello,

I have the same issue I have used the --network="host" and it started. Not the best solution but until there's a solution still workaround.

Regards, Marc

TMarc avatar Apr 19 '21 17:04 TMarc