Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 7 of 7
  1. #1
    Join Date
    October 2018
    Posts
    4

    Disconnects with regular server (because of a missing license)

    Hi, i would like to know if this is a normal behaviour (because of a missing license) to have some disconnects every day?
    Or if this is a technical problem. The disconnects take a couple of minutes, then the people can reconnect. The message is, that the server has been shutdown.

  2. #2
    Join Date
    June 2008
    Posts
    18,513
    There is something suspicious going on with the server when you see such message.
    Contact the server owner/host to get this solved.
    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?

  3. #3
    Join Date
    October 2018
    Posts
    4
    I am the server owner.

    Code:
    2018-10-13 19:56:26.969418|INFO    |              |   |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
    2018-10-13 20:01:50.908583|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:01:50.908711|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:01:52.026170|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:01:52.026294|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:01:54.031119|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:01:54.031289|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:11:50.924094|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:11:50.924246|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:11:52.025970|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:11:52.026073|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:11:54.029149|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:11:54.029257|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:21:50.964003|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:21:50.964130|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:21:52.065910|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:21:52.066045|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:21:54.071374|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:21:54.071516|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:31:51.024773|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:31:51.024930|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:31:53.029314|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:31:53.029555|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:31:55.032718|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:31:55.032860|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:41:51.041539|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:41:51.041855|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:41:53.046054|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:41:53.046171|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:41:55.049736|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:41:55.049883|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:51:51.113554|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:51:51.113907|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:51:53.017288|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:51:53.017397|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:51:55.022140|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 20:51:55.022248|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 21:01:51.219403|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 21:01:51.219543|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 21:01:53.023486|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 21:01:53.023599|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    2018-10-13 21:01:55.027921|ERROR   |              |   |TS3ANetwork::Send failed error: 1
    so *something* is trying to get somewhere what is probably beeing blocked.

    I followed these documentation https://www.teamspeak.de/support/ant...s%2Fa%2F1.html for my iptables script. "eingehen" means incoming, "ausgehend" means outgoing.

    So my iptables look like this:
    Code:
    Chain INPUT (policy DROP)
    target     prot opt source               destination
    DROP       all  --  anywhere             anywhere             state INVALID
    f2b-sshd   tcp  --  anywhere             anywhere             multiport dports 5434
    f2b-sshd   tcp  --  anywhere             anywhere             multiport dports 5434
    ACCEPT     udp  --  anywhere             anywhere             udp dpt:9987 /* incoming audio for ts3 */
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:30033 /* incoming filetransfer for ts3 */
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:10011 /* serverquery for ts3 */
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:41144 /* tsdns for ts3 */
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:5434 /* SSH */
    ACCEPT     all  --  anywhere             anywhere
    ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:https /* HTTPS */
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:http /* HTTP */
    ACCEPT     icmp --  anywhere             anywhere             state NEW
    
    Chain FORWARD (policy DROP)
    target     prot opt source               destination
    DROP       all  --  anywhere             anywhere             state INVALID
    
    Chain OUTPUT (policy DROP)
    target     prot opt source               destination
    DROP       all  --  anywhere             anywhere             state INVALID
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:5434 /* SSH */
    ACCEPT     all  --  anywhere             anywhere
    ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:http /* HTTP */
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:https /* HTTPS */
    ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:http state NEW
    ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:domain state NEW
    ACCEPT     udp  --  anywhere             anywhere             udp dpt:domain state NEW
               udp  --  anywhere             anywhere             udp dpt:2010 /* weblist for ts3 */
               tcp  --  anywhere             anywhere             tcp dpt:2008 /* accounting for ts3 */
    
    Chain f2b-sshd (2 references)
    target     prot opt source               destination
    RETURN     all  --  anywhere             anywhere
    RETURN     all  --  anywhere             anywhere
    I know its not perfect (e.g. i could ignore the FORWARD invalid drop because everything is dropped), but it should work.
    Is there something wrong with the port documentation on that page?

  4. #4
    Join Date
    June 2008
    Posts
    18,513
    Please do not use outdated How Tos.
    We have a FAQ for the needed Ports and domains that need to be reachable for the server.

    P.s. Don't worry about german in reports. Ich verstehe deren Inhalt ;D
    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?

  5. #5
    Join Date
    October 2018
    Posts
    4
    Oh thanks, so probably it was a problem with the iptables configuration. Will check that and apply the required changes.

    Just checked the rules, they seem ok to me.
    443 outgoing is allowed because the server also has an apache2 running on it.
    Is there any way to get more verbose information whats going on?

    telnet accounting.teamspeak.com 2008
    Trying 128.65.210.118...
    Connected to accounting.teamspeak.com.
    Escape character is '^]'.
    Last edited by someone99; October 16th, 2018 at 11:53 AM.

  6. #6
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,368
    accounting.teamspeak.com:2008 is not the appropriate accounting server for current versions of TeamSpeak. Accounting2 is done by simple HTTPS as explained in dante's link.

  7. #7
    Join Date
    October 2018
    Posts
    4
    did not read the notes, my bad.

    telnet accounting2.teamspeak.com 443
    Trying 104.20.74.196...
    Connected to accounting2.teamspeak.com.
    Escape character is '^]'.
    EHLO
    HTTP/1.1 400 Bad Request
    Server: cloudflare
    Date: Tue, 16 Oct 2018 17:53:04 GMT
    Content-Type: text/html
    Content-Length: 171
    Connection: close
    CF-RAY: -

    <html>
    <head><title>400 Bad Request</title></head>
    <body bgcolor="white">
    <center><h1>400 Bad Request</h1></center>
    <hr><center>cloudflare</center>
    </body>
    </html>
    Connection closed by foreign host.
    [email protected]:~$ telnet ts3services.teamspeak.com 443
    Trying 104.20.75.196...
    Connected to ts3services.teamspeak.com.
    Escape character is '^]'.
    EHLO
    HTTP/1.1 400 Bad Request
    Server: cloudflare
    Date: Tue, 16 Oct 2018 17:53:21 GMT
    Content-Type: text/html
    Content-Length: 171
    Connection: close
    CF-RAY: -

    <html>
    <head><title>400 Bad Request</title></head>
    <body bgcolor="white">
    <center><h1>400 Bad Request</h1></center>
    <hr><center>cloudflare</center>
    </body>
    </html>
    Connection closed by foreign host.
    maybe its a problem with cloudflare. some kind of blocking or such.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Regular Expressions mit HEX
    By Hackebein in forum Bug Reports [EN/DE]
    Replies: 2
    Last Post: November 10th, 2017, 09:05 PM
  2. Regular TS disconnects (several clients)
    By Archonicus in forum Client Support
    Replies: 0
    Last Post: June 16th, 2016, 01:29 PM
  3. Replies: 5
    Last Post: August 30th, 2014, 03:40 PM
  4. [Evaluation] How comes regular SA can set permission values over 75?
    By justincase in forum Suggestions and Feedback
    Replies: 14
    Last Post: July 12th, 2012, 08:20 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
  •