Forum

Page 1 of 2 12 LastLast
Results 1 to 15 of 17
  1. #1
    Join Date
    February 2018
    Posts
    2

    Server 3.1 tells client that he is outdated

    Edit by mod
    Please scroll to post #5 for details and updates



    ----- original post below -----

    i've been connecting to this server fine for weeks and today i'm getting a message saying my client version is too old. when i hit yes to update another pop up comes up telling me i'm using the newest version. i hadn't updated kernel stuff but when i did it didn't seem to make a difference, here's the log:

    Code:
    2018-02-16 18:01:25.236954|INFO    |              |   |TeamSpeak 3 Client 3.1.8 (2018-01-22 09:50:07)
    2018-02-16 18:01:25.237031|INFO    |              |   |SystemInformation: Linux 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 Binary: 64bit
    2018-02-16 18:01:25.237060|INFO    |              |   |Using hardware aes
    2018-02-16 18:01:25.276364|DEBUG   |PulseAudio    |   |connected to pulse audio server - 
    2018-02-16 18:01:25.293897|INFO    |ClientUI      |   |OpenGL Info: LibGL, Vendor: Intel Open Source Technology Center, Renderer: Mesa DRI Intel(R) Ivybridge Mobile , Version: 3.0 Mesa 17.2.8
    2018-02-16 18:01:25.324925|INFO    |Addons        |   |Checking for addon updates...
    2018-02-16 18:01:25.352656|INFO    |Plugins       |   |Loading plugin: libclientquery_plugin_linux_amd64.so
    2018-02-16 18:01:25.356593|ERROR   |Query         |   |bind failed on 127.0.0.1:25639
    2018-02-16 18:01:25.456305|INFO    |Addon         |   |Addon up to date.
    2018-02-16 18:01:25.695557|INFO    |              |   |*** Time [MAINWINDOW]: 230
    2018-02-16 18:01:25.695644|INFO    |              |   |*** Time [INIT]: 231
    2018-02-16 18:01:25.695879|DEVELOP |ClientUI      |   |Notifications init: Soundpack path: /opt/TeamSp3/sound/default
    2018-02-16 18:01:25.699974|INFO    |ClientUI      |   |Failed to init text to speech engine
    2018-02-16 18:01:25.700076|INFO    |ClientUI      |   |Qt version: 5.6.1
    2018-02-16 18:01:25.700115|INFO    |ClientUI      |   |Using configuration location: /home/boss/.ts3client/settings.db
    2018-02-16 18:01:26.195836|INFO    |Bookmarks     |   |Collecting autoconnect bookmarks
    2018-02-16 18:01:26.196350|INFO    |ClientUI      |   |Last update check was: Fri Feb 16 11:04:01 2018
    2018-02-16 18:01:26.197046|INFO    |              |   |Statistics report: User previously denied participation
    2018-02-16 18:01:26.705731|INFO    |Newsticker    |   |Newsticker next check: Fri Feb 16 12:04:02 2018
    2018-02-16 18:01:37.019831|INFO    |ClientUI      |1  |Connect to server: ts.whalepool.io
    2018-02-16 18:01:37.054201|INFO    |ClientUI      |1  |Trying to resolve ts.whalepool.io
    2018-02-16 18:01:37.173012|INFO    |TSDNS         |   |SRV DNS resolve successful, "_ts3._udp.ts.whalepool.io" =(h: ts.whalepool.io p:50128)
    2018-02-16 18:01:37.174561|INFO    |TSDNS         |   |A/AAAA DNS resolve for possible TSDNS successful, "whalepool.io" =(h: 52.211.250.132 p:0)
    2018-02-16 18:01:37.175774|INFO    |TSDNS         |   |A/AAAA DNS resolve for possible TSDNS successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-16 18:01:37.175982|INFO    |TSDNS         |   |A/AAAA DNS resolve successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-16 18:01:37.188250|INFO    |TSDNS         |   |SRV DNS resolve unsuccessful, "_tsdns._tcp.whalepool.io" DNS server returned answer with no data
    2018-02-16 18:01:37.191217|INFO    |TSDNS         |   |A/AAAA DNS resolve successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-16 18:01:37.191311|INFO    |ClientUI      |1  |Lookup finished: ip=158.69.115.146 port=50128 query=ts.whalepool.io error=0
    2018-02-16 18:01:37.191366|INFO    |ClientUI      |1  |Resolve successful: 158.69.115.146:50128
    2018-02-16 18:01:37.191395|INFO    |ClientUI      |1  |Initiating connection: 158.69.115.146:50128
    2018-02-16 18:01:37.207438|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 158.69.115.146:41144
    2018-02-16 18:01:37.207573|INFO    |TSDNS         |   |No TSDNS found
    2018-02-16 18:01:37.279965|INFO    |PreProSpeex   |1  |Speex version: 1.2rc1
    2018-02-16 18:01:37.284124|INFO    |ClientUI      |1  |Connect status: Connecting
    2018-02-16 18:01:37.371473|INFO    |ClientUI      |1  |Connect status: Disconnected
    2018-02-16 18:01:39.175108|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 52.211.250.132:41144
    2018-02-16 18:01:39.175282|INFO    |TSDNS         |   |No TSDNS found
    2018-02-16 18:01:40.543547|INFO    |ClientUI      |1  |Failed to connect to server because client is too old
    2018-02-16 18:01:40.643686|INFO    |Update        |   |Checking for updates...
    2018-02-16 18:01:40.728073|INFO    |Update        |   |Check license: version=2, min_version=2, my_license_version=2, my_license_min_version=2
    2018-02-16 18:01:40.728189|INFO    |Update        |   |Check client version: 3.1.8 1516614607
    2018-02-16 18:01:40.728258|INFO    |Update        |   |Update check, my version: 1516614607, latest version: 1516614607
    i don't see any beta versions of the client available so i'm not sure what's going on, any ideas?
    Last edited by dante696; February 19th, 2018 at 11:17 AM.

  2. #2
    Join Date
    February 2018
    Posts
    1

    new ts3 version 3.1.8

    Hello everyone,
    i started my ts3 client and popped a message saying that it needs to be updated.
    hit the update but it says that i already have the latest version.
    now, problem is that i can't connect to any server. the same msg keeps popping up that i need to update client for this server.
    I uninstalled ts3 and reinstalled it from the official teamspeak server but still the same.
    That message keeps popping up " This server requires a newer client version "
    I'm running a ts3 server on Verygames ( if this help for any solution )
    Thanks for reading this post, hope i get a solution soon.

    ps : Already made a ticket for Verygames also.

  3. #3
    Join Date
    October 2016
    Location
    Berlin, Berlin, Germany
    Posts
    160

    Server 3.1 tells client is outdated

    Bei dem ersten Verbindungsversuch wird ein Return Code zurückgegeben das der Client geupdatet werden soll... obwohl ja die Clients über der 3.1.7+ sind.

    Versucht man aber das zweite mal zu Verbinden dann funktioniert es reibungslos, viele User haben sich darüber Beschwert und ich kann es auch
    bestätigen da ich auf iOS selber davon betroffen bin.

    An den client_min_X permissons liegt es nicht.
    Last edited by SossenSystems; February 17th, 2018 at 02:27 PM. Reason: merged, thread renamed

  4. #4
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,365
    Please show the server's client_min_x via telnet.

  5. #5
    Join Date
    June 2008
    Posts
    18,231
    Update 2 (20th Feb 2018)
    OVH got a reply with a solution.

    For anyone else who owns a server (not hosted on OVH) should contact their server provider
    and suggest to replace their DDoS protection for Teamspeak with our ts3init_linux_netfilter_module.

    This is a ready to use DDoS protection for the TeamSpeak server. Advantage it's maintained by us + we offer support.

    This is no bug in our server or client. Thread moved to server section.

    Update 1 (19th Feb 2018)
    It seems that OVH's DDoS protection blocks packets on connect.
    We are in contact with OVH and try to find a solution.

    You the user need to ignore the update request and in most cases you just need to connect a second or third time to the server.

    -------original post below---------

    Quote Originally Posted by numma_cway View Post
    Please show the server's client_min_x via telnet.
    We doubt that this is the issue.
    As mentioned in Server 3.1 thread: Something with firewall or other protection on server host caused this.

    I put that thread under evaluation to discuss this with our devs.
    There are to many reports in my opinion. Could be that all hosts use same protection or we have a problem. Unclear is why the client gets a wrong minimal version from server.
    Last edited by dante696; February 19th, 2018 at 10:33 AM.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  6. #6
    Join Date
    October 2016
    Location
    Berlin, Berlin, Germany
    Posts
    160
    Quote Originally Posted by numma_cway View Post
    Please show the server's client_min_x via telnet.
    Okay.
    Code:
    virtualserver_min_client_version=1445512488
    virtualserver_min_android_version=1427190433
    virtualserver_min_ios_version=1408613527
    I turned off my firewall several days ago.
    Otherwise, I use the OVH Game Firewall!

  7. #7
    Join Date
    February 2018
    Posts
    1

    This server needs a newer client version

    I've been dealing with this error since yesterday. I have updated already, reinstalled the program and still I have this error. Just asked my partner if he is dealing with this as well, and he told me that the server is running fine
    Last edited by dante696; February 17th, 2018 at 02:33 PM. Reason: merged

  8. #8
    Join Date
    June 2008
    Posts
    18,231
    Quote Originally Posted by SossenSystems View Post
    Otherwise, I use the OVH Game Firewall!
    OVH is one host where we could identify that the firewall or other protection cause this false message.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  9. #9
    Join Date
    February 2018
    Location
    Hamburg
    Posts
    13
    i have this issue too and we hosting our servers by ovh too... any solution?

  10. #10
    Join Date
    February 2018
    Posts
    2
    update:

    on the suggestion of the server admin i was able to conect after repeatedly trying to connect and hitting no to the update question. here's the log,

    Code:
    2018-02-17 06:07:44.158674|INFO    |PreProSpeex   |1  |Speex version: 1.2rc1
    2018-02-17 06:07:44.163316|INFO    |ClientUI      |1  |Connect status: Connecting
    2018-02-17 06:07:44.243960|INFO    |ClientUI      |1  |Connect status: Disconnected
    2018-02-17 06:07:46.067302|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 52.211.250.132:41144
    2018-02-17 06:07:46.067451|INFO    |TSDNS         |   |No TSDNS found
    2018-02-17 06:07:49.499864|INFO    |ClientUI      |1  |Failed to connect to server because client is too old
    2018-02-17 06:07:49.599997|INFO    |Update        |   |Checking for updates...
    2018-02-17 06:07:49.640216|INFO    |Update        |   |Check license: version=2, min_version=2, my_license_version=2, my_license_min_version=2
    2018-02-17 06:07:49.640305|INFO    |Update        |   |Check client version: 3.1.8 1516614607
    2018-02-17 06:07:49.640337|INFO    |Update        |   |Update check, my version: 1516614607, latest version: 1516614607
    [3185:3185:0217/003225.545310:ERROR:sync_control_vsync_provider.cc(62)] glXGetSyncValuesOML should not return TRUE with a media stream counter of 0.
    2018-02-17 06:37:39.269018|INFO    |Newsticker    |   |Newsticker next check: Sat Feb 17 00:37:38 2018
    2018-02-17 06:37:39.336815|INFO    |Newsticker    |   |Newsticker received for language en, expires on Sat Feb 17 01:07:39 2018, next check in 1800 seconds
    2018-02-17 07:07:39.268861|INFO    |Newsticker    |   |Newsticker next check: Sat Feb 17 01:07:39 2018
    2018-02-17 07:07:49.269097|INFO    |Newsticker    |   |Newsticker next check: Sat Feb 17 01:07:39 2018
    2018-02-17 07:07:49.353680|INFO    |Newsticker    |   |Newsticker received for language en, expires on Sat Feb 17 01:37:49 2018, next check in 1800 seconds
    2018-02-17 16:40:59.659316|INFO    |ClientUI      |1  |Connect to server: ts.whalepool.io
    2018-02-17 16:40:59.660046|INFO    |ClientUI      |1  |Trying to resolve ts.whalepool.io
    2018-02-17 16:40:59.786817|INFO    |TSDNS         |   |A/AAAA DNS resolve for possible TSDNS successful, "whalepool.io" =(h: 52.211.250.132 p:0)
    2018-02-17 16:40:59.796385|INFO    |TSDNS         |   |SRV DNS resolve unsuccessful, "_tsdns._tcp.whalepool.io" DNS server returned answer with no data
    2018-02-17 16:40:59.805412|INFO    |TSDNS         |   |SRV DNS resolve successful, "_ts3._udp.ts.whalepool.io" =(h: ts.whalepool.io p:50128)
    2018-02-17 16:40:59.805811|INFO    |TSDNS         |   |A/AAAA DNS resolve successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 16:40:59.806100|INFO    |TSDNS         |   |A/AAAA DNS resolve for possible TSDNS successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 16:40:59.815949|INFO    |TSDNS         |   |A/AAAA DNS resolve successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 16:40:59.816059|INFO    |ClientUI      |1  |Lookup finished: ip=158.69.115.146 port=50128 query=ts.whalepool.io error=0
    2018-02-17 16:40:59.816118|INFO    |ClientUI      |1  |Resolve successful: 158.69.115.146:50128
    2018-02-17 16:40:59.816151|INFO    |ClientUI      |1  |Initiating connection: 158.69.115.146:50128
    2018-02-17 16:40:59.837428|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 158.69.115.146:41144
    2018-02-17 16:40:59.837484|INFO    |TSDNS         |   |No TSDNS found
    2018-02-17 16:40:59.863438|INFO    |ClientUI      |1  |Connect status: Connecting
    2018-02-17 16:40:59.942232|INFO    |ClientUI      |1  |Connect status: Disconnected
    2018-02-17 16:41:01.788610|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 52.211.250.132:41144
    2018-02-17 16:41:01.788804|INFO    |TSDNS         |   |No TSDNS found
    2018-02-17 16:41:03.005041|INFO    |ClientUI      |1  |Failed to connect to server because client is too old
    2018-02-17 16:44:17.499496|INFO    |Newsticker    |   |Newsticker next check: Sat Feb 17 01:37:49 2018
    2018-02-17 16:44:17.558083|INFO    |Newsticker    |   |Newsticker received for language en, expires on Sat Feb 17 11:14:17 2018, next check in 1800 seconds
    [3093:3093:0217/105258.060831:ERROR:CONSOLE(6)] "Uncaught ReferenceError: gbar is not defined", source: https://clients5.google.com/pagead/drt/dn/ (6)
    2018-02-17 17:14:17.512005|INFO    |Newsticker    |   |Newsticker next check: Sat Feb 17 11:14:17 2018
    2018-02-17 17:14:27.499591|INFO    |Newsticker    |   |Newsticker next check: Sat Feb 17 11:14:17 2018
    2018-02-17 17:14:27.571093|INFO    |Newsticker    |   |Newsticker received for language en, expires on Sat Feb 17 11:44:27 2018, next check in 1800 seconds
    [3093:3126:0217/112500.902172:ERROR:service_manager.cc(157)] Connection InterfaceProviderSpec prevented service: content_renderer from binding interface: blink::mojom::ReportingServiceProxy exposed by: content_browser
    2018-02-17 17:25:51.212951|INFO    |ClientUI      |1  |Connect to server: ts.whalepool.io
    2018-02-17 17:25:51.222733|INFO    |ClientUI      |1  |Trying to resolve ts.whalepool.io
    2018-02-17 17:25:51.242429|INFO    |TSDNS         |   |A/AAAA DNS resolve for possible TSDNS successful, "whalepool.io" =(h: 52.211.250.132 p:0)
    2018-02-17 17:25:51.341003|INFO    |TSDNS         |   |A/AAAA DNS resolve successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 17:25:51.341705|INFO    |TSDNS         |   |A/AAAA DNS resolve for possible TSDNS successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 17:25:51.349785|INFO    |TSDNS         |   |SRV DNS resolve unsuccessful, "_tsdns._tcp.whalepool.io" DNS server returned answer with no data
    2018-02-17 17:25:51.352177|INFO    |TSDNS         |   |SRV DNS resolve successful, "_ts3._udp.ts.whalepool.io" =(h: ts.whalepool.io p:50128)
    2018-02-17 17:25:51.362085|INFO    |TSDNS         |   |A/AAAA DNS resolve successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 17:25:51.362333|INFO    |ClientUI      |1  |Lookup finished: ip=158.69.115.146 port=50128 query=ts.whalepool.io error=0
    2018-02-17 17:25:51.362478|INFO    |ClientUI      |1  |Resolve successful: 158.69.115.146:50128
    2018-02-17 17:25:51.362613|INFO    |ClientUI      |1  |Initiating connection: 158.69.115.146:50128
    2018-02-17 17:25:51.368640|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 158.69.115.146:41144
    2018-02-17 17:25:51.368761|INFO    |TSDNS         |   |No TSDNS found
    2018-02-17 17:25:51.421558|INFO    |ClientUI      |1  |Connect status: Connecting
    2018-02-17 17:25:51.501356|INFO    |ClientUI      |1  |Connect status: Disconnected
    2018-02-17 17:25:53.243675|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 52.211.250.132:41144
    2018-02-17 17:25:53.243854|INFO    |TSDNS         |   |No TSDNS found
    2018-02-17 17:25:55.276259|INFO    |ClientUI      |1  |Failed to connect to server because client is too old
    2018-02-17 17:44:26.684413|INFO    |Newsticker    |   |Newsticker next check: Sat Feb 17 11:44:27 2018
    2018-02-17 17:44:36.684449|INFO    |Newsticker    |   |Newsticker next check: Sat Feb 17 11:44:27 2018
    2018-02-17 17:44:36.751679|INFO    |Newsticker    |   |Newsticker received for language en, expires on Sat Feb 17 12:14:36 2018, next check in 1800 seconds
    2018-02-17 18:14:36.683439|INFO    |Newsticker    |   |Newsticker next check: Sat Feb 17 12:14:36 2018
    2018-02-17 18:14:46.685077|INFO    |Newsticker    |   |Newsticker next check: Sat Feb 17 12:14:36 2018
    2018-02-17 18:14:46.759176|INFO    |Newsticker    |   |Newsticker received for language en, expires on Sat Feb 17 12:44:46 2018, next check in 1800 seconds
    2018-02-17 18:37:14.933996|INFO    |ClientUI      |1  |Connect to server: ts.whalepool.io
    2018-02-17 18:37:14.935893|INFO    |ClientUI      |1  |Trying to resolve ts.whalepool.io
    2018-02-17 18:37:15.060321|INFO    |TSDNS         |   |SRV DNS resolve successful, "_ts3._udp.ts.whalepool.io" =(h: ts.whalepool.io p:50128)
    2018-02-17 18:37:15.065294|INFO    |TSDNS         |   |SRV DNS resolve unsuccessful, "_tsdns._tcp.whalepool.io" DNS server returned answer with no data
    2018-02-17 18:37:15.069643|INFO    |TSDNS         |   |A/AAAA DNS resolve successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 18:37:15.069876|INFO    |TSDNS         |   |A/AAAA DNS resolve for possible TSDNS successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 18:37:15.070139|INFO    |TSDNS         |   |A/AAAA DNS resolve for possible TSDNS successful, "whalepool.io" =(h: 52.211.250.132 p:0)
    2018-02-17 18:37:15.074965|INFO    |TSDNS         |   |A/AAAA DNS resolve successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 18:37:15.075243|INFO    |ClientUI      |1  |Lookup finished: ip=158.69.115.146 port=50128 query=ts.whalepool.io error=0
    2018-02-17 18:37:15.075383|INFO    |ClientUI      |1  |Resolve successful: 158.69.115.146:50128
    2018-02-17 18:37:15.075456|INFO    |ClientUI      |1  |Initiating connection: 158.69.115.146:50128
    2018-02-17 18:37:15.097144|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 158.69.115.146:41144
    2018-02-17 18:37:15.097222|INFO    |TSDNS         |   |No TSDNS found
    2018-02-17 18:37:15.153905|INFO    |ClientUI      |1  |Connect status: Connecting
    2018-02-17 18:37:15.242630|INFO    |ClientUI      |1  |Connect status: Disconnected
    2018-02-17 18:37:17.072323|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 52.211.250.132:41144
    2018-02-17 18:37:17.072473|INFO    |TSDNS         |   |No TSDNS found
    2018-02-17 18:37:17.098564|INFO    |ClientUI      |1  |Failed to connect to server because client is too old
    2018-02-17 18:37:19.787953|INFO    |ClientUI      |1  |Connect to server: ts.whalepool.io
    2018-02-17 18:37:19.789859|INFO    |ClientUI      |1  |Trying to resolve ts.whalepool.io
    2018-02-17 18:37:19.803022|INFO    |TSDNS         |   |A/AAAA DNS resolve successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 18:37:19.803865|INFO    |TSDNS         |   |A/AAAA DNS resolve for possible TSDNS successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 18:37:19.804114|INFO    |TSDNS         |   |A/AAAA DNS resolve for possible TSDNS successful, "whalepool.io" =(h: 52.211.250.132 p:0)
    2018-02-17 18:37:19.805066|INFO    |TSDNS         |   |SRV DNS resolve unsuccessful, "_tsdns._tcp.whalepool.io" DNS server returned answer with no data
    2018-02-17 18:37:19.807913|INFO    |TSDNS         |   |SRV DNS resolve successful, "_ts3._udp.ts.whalepool.io" =(h: ts.whalepool.io p:50128)
    2018-02-17 18:37:19.819484|INFO    |TSDNS         |   |A/AAAA DNS resolve successful, "ts.whalepool.io" =(h: 158.69.115.146 p:0)
    2018-02-17 18:37:19.819771|INFO    |ClientUI      |1  |Lookup finished: ip=158.69.115.146 port=50128 query=ts.whalepool.io error=0
    2018-02-17 18:37:19.819866|INFO    |ClientUI      |1  |Resolve successful: 158.69.115.146:50128
    2018-02-17 18:37:19.819925|INFO    |ClientUI      |1  |Initiating connection: 158.69.115.146:50128
    2018-02-17 18:37:19.831606|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 158.69.115.146:41144
    2018-02-17 18:37:19.831725|INFO    |TSDNS         |   |No TSDNS found
    2018-02-17 18:37:19.861901|INFO    |ClientUI      |1  |Connect status: Connecting
    2018-02-17 18:37:19.924796|DEVELOP |PktHandler    |   |Puzzle solve time: 8
    2018-02-17 18:37:20.585641|INFO    |ClientUI      |1  |Connect status: Connected
    2018-02-17 18:37:20.614220|INFO    |ClientUI      |1  |Connect status: Establishing connection
    2018-02-17 18:37:20.627275|INFO    |ClientUI      |1  |Connect status: Connection established
    2018-02-17 18:37:20.628172|INFO    |PermManager   |   |Requesting permissions from server
    2018-02-17 18:37:20.903198|INFO    |UIHelpers     |   |setClientVolumeModifier: 258 -8
    2018-02-17 18:37:20.967396|INFO    |UIHelpers     |   |setClientVolumeModifier: 172 -8
    2018-02-17 18:37:21.805870|INFO    |TSDNS         |   |TSDNS queried unsuccessfully 52.211.250.132:41144
    2018-02-17 18:37:21.806022|INFO    |TSDNS         |   |No TSDNS found

  11. #11
    Join Date
    June 2008
    Posts
    18,231
    Yep that helps. First connect try and packets gets blocked and now on second try nothing seems to be blocked.
    Now when you repeat that with different client IP, the same behavior will appear again or when you wait a while.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  12. #12
    Join Date
    October 2016
    Location
    Berlin, Berlin, Germany
    Posts
    160
    When will the development team look at the problem?

  13. #13
    Join Date
    June 2008
    Posts
    18,231
    We did already after first report during beta and other reports during stable.
    At this point we could not identify sth. else then host's protection.
    Last edited by dante696; February 18th, 2018 at 01:35 PM. Reason: words got cut off.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  14. #14
    Join Date
    October 2016
    Location
    Berlin, Berlin, Germany
    Posts
    160
    My TeamSpeak 3 server is running on Ubuntu 16.04 (x64).
    It could be that there is a problem with Ubuntu.
    That's why I wonder if servers with Debian and Co. also are affected.

  15. #15
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,365
    Read the thread! OVH was already identified as the issue here.

    BTW: Debian and Ubuntu are basically the same thing.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 1
    Last Post: December 19th, 2017, 08:33 AM
  2. Replies: 6
    Last Post: September 17th, 2012, 09:51 PM
  3. [Solved] Server is outdated with client Beta21
    By cokiemonster in forum Client Support
    Replies: 40
    Last Post: June 9th, 2011, 06:02 PM
  4. [Resolved] Server tells me icons are mising
    By Osiris52 in forum Windows
    Replies: 2
    Last Post: March 24th, 2011, 05:00 PM
  5. [Solved] Server is outdated with client Beta21
    By cokiemonster in forum General Questions
    Replies: 2
    Last Post: June 2nd, 2010, 10:23 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •