Notice to all users

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

Results 1 to 7 of 7
  1. #1
    Join Date
    April 2014

    Users timeout from server.

    I'm using 64bit Debian on AMD structure. I'm hosting TS3 server.
    • 8 GB ram
    • 200 Mb/s
    • Xeon with 4 cores
    • Whole machine is from late 2007.
    • TS3 server AMD 3.10.3

    And here is the problem:
    Everytime users who connect above 52nd user time out. For example:
    When there are 52 users and 10 connect after few seconds 10 random users on the server time out. I've upgraded it from 3.10.1 to 3.10.3 and still there is a problem.

    There isn't any overload on the server, usage at that moment is about 0,8% of processor and 300 MB ram. I have web server and ftp server there.
    There aren't any limits on switch or on a machine. I host it in serverroom, machine is on 24/7 restarted once a day.
    I was looking for an answer on other pages and couldn't fiugure out what's wrong. I'll be glad if someone will help me.

    I've done:
    • Checked server connection limits in sysctl.
    • Reinstalled TS3 server.
    • Set default options.
    • Checked user settings.
    • Looked for problem for 2 weeks.
    Last edited by Kruk939; April 2nd, 2014 at 05:13 PM.

  2. #2
    Join Date
    June 2011
    Doesn't sound like a TS problem. My VPS is much weaker and handles over 200 users.
    I wanted to say it was about the number of possible connections at the same time, but TS3 uses UDP, so there are no connections at all.

  3. #3
    Join Date
    September 2012
    Sounds like there might be a UDP Limitation somewhere in the network.
    When sending PMs please make sure to include a reference link to the thread in question in the body of your message.

  4. #4
    Join Date
    February 2012
    Perhaps you have a too restrictive iptables firewall set up on the machine. Could you post a "iptables -nvL"? This will output all current rules with the current counters.

  5. #5
    Join Date
    April 2014
    First there weren't any rules. And problem was still there. And after add some iptables also:
    Chain INPUT (policy ACCEPT 10793 packets, 696K bytes)
     pkts bytes target     prot opt in     out     source               destination         
      691 41468 ACCEPT     tcp  --  *      *             tcp dpt:10011 state NEW 
      170  8880 ACCEPT     tcp  --  *      *             tcp dpt:30033 state NEW 
        0     0 ACCEPT     tcp  --  *      *             tcp dpt:2008 state NEW 
        0     0 ACCEPT     udp  --  *      *             udp dpt:2010 state NEW 
    8240K  705M ACCEPT     all  --  eth0   *             state RELATED,ESTABLISHED 
      319 20609 ACCEPT     udp  --  *      *             udp dpt:9987 state NEW 
       52  4633 ACCEPT     udp  --  *      *             udp dpt:9887 state NEW 
        4   248 ACCEPT     udp  --  *      *             udp dpt:1337 state NEW 
      132 12768 ACCEPT     udp  --  *      *             udp dpt:4488 state NEW 
        0     0 ACCEPT     all  --  lo     *             
    Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
     pkts bytes target     prot opt in     out     source               destination         
    Chain OUTPUT (policy ACCEPT 18M packets, 3934M bytes)
     pkts bytes target     prot opt in     out     source               destination         
      160 14753 ACCEPT     tcp  --  *      *             tcp dpt:2008 
      479 20009 ACCEPT     udp  --  *      *             udp dpt:2010
    There isn't any limitations in UPD on server. Perhaps on switch, well I'll check it tomorrow.

  6. #6
    Join Date
    February 2012
    The firewall is probably not the issue with your TS3 connection problem. But you have an issue with your firewall: it has an incomplete ruleset. You allow every packet that arrives at your machine. You don't have any deny rule in your ruleset. Either you set policy DENY to deny everything that falls through the rules, or you add a DENY rule at the end of each chain to catch them explicitly.

    Setting policy DENY is a bit dangerous, because if you have a syntax error in your iptables configuration and perform a reload of the ruleset, the ruleset is not loaded but the DENY policy is active and blocks everything, including every remote ssh session you may habe open for remote configuration. Adding a DENY rule at the end of each chain and using policy ALLOW is a bit safer, since it "only" opens your firewall completely if there is a syntax error in the definition file. Usually, you correct that error immediately, reload the firewall rules and everything is fine again.

  7. #7
    Join Date
    December 2013
    1) UDP is stateless protocol.
    2) Try stopping your firewall and look at the situation. Most likely it will be normal after that.
    3) Firewall can be present not only on your machine especially. If problem continues, please ask your ISP to remove any UDP limitations (e.g. PPS/MBs to special port).
    4) Look for any strange messages in your TS log. Sometimes clients get dropped because of incorrectly configured system clock.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. I let timeout everyone on the server
    By WalkDown in forum Client Support
    Replies: 2
    Last Post: June 2nd, 2013, 10:39 PM
  2. Server Timeout/Crash
    By sonofdresa in forum Windows
    Replies: 2
    Last Post: December 22nd, 2009, 03:33 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