Forum

Results 1 to 3 of 3
  1. #1
    Join Date
    July 2013
    Posts
    6

    Problem: Connecting to Teamspeak 3 server on Ubuntu VPS

    I'm having an issue with my teamspeak server, I'm a beginner to linux and vps, but I am computer saavy enough to follow through. I have tried many tutorials online to getting the server to start up or connect to it.

    I have reinstalled my VPS to latest 64-bit Ubuntu, clean slate. Logged as root using putty, added a new user as root, log in as said user, downloaded the correct file manually using WINscp into "myusername" directory, extract files, move files to a different in "myusername". Ran the "./ts3server_minimal_script.sh createinifile=1" command in putty, then edited the inifile with all my info (listed below), edited the start script file to contain "inifile=ts3server.ini" within command parameters line. I have done all this and then start the teamspeak server. What have I done wrong that it's not working?

    Most recent log lists only:

    2013-07-17 15:41:53.899482|INFO |VirtualServer | 1| listening on 96.47.239.137:9987

    but I recieve this on the teamspeak client:

    <11:42:49> Trying to connect to server on 96.47.239.137
    <11:42:55> Failed to connect to server
    <12:24:10> Trying to connect to server on 96.47.239.137
    <12:24:17> Failed to connect to server

    Here is my ini file:

    machine_id=
    default_voice_port=9987
    voice_ip=96.47.239.137
    licensepath=
    filetransfer_port=30033
    filetransfer_ip=96.47.239.137
    query_port=10011
    query_ip=96.47.239.137
    query_ip_whitelist=query_ip_whitelist.txt
    query_ip_blacklist=query_ip_blacklist.txt
    dbplugin=ts3db_sqlite3
    dbpluginparameter=
    dbsqlpath=sql/
    dbsqlcreatepath=create_sqlite/
    dbconnections=10
    logpath=logs
    logquerycommands=0
    dbclientkeepdays=30
    logappend=0

    One more from the terminal:

    [email protected]:~/apps/ts3$ netstat -ant | grep LISTEN
    tcp 0 0 96.47.239.137:30033 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
    tcp 0 0 96.47.239.137:10011 0.0.0.0:* LISTEN
    tcp6 0 0 :::22 :::* LISTEN

    Anything else you need, I can provide, thanks in advanced!
    Last edited by Cook13s; July 17th, 2013 at 08:11 PM.

  2. #2
    Join Date
    October 2010
    Location
    Warsaw / Poland
    Posts
    296
    Check if server is in fact running by command netstat -anu | grep "9987"

    If it does I'd take a look if you don't have any router or other firewall filtering UDP packets.

  3. #3
    Join Date
    July 2013
    Posts
    6

    Question

    Quote Originally Posted by ARCHI View Post
    Check if server is in fact running by command netstat -anu | grep "9987"

    If it does I'd take a look if you don't have any router or other firewall filtering UDP packets.
    Actually, that's what it was the provider stated they were blocking some ports by default, I already emailed them and they have opened the ports. Also, I thought I had replied to this thread about my issue already being resolved, my post disappeared or something.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Replies: 2
    Last Post: July 18th, 2011, 08:44 PM
  2. Replies: 2
    Last Post: June 24th, 2011, 09:22 PM

Posting Permissions

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