Connection could not be initialized

Hey,
after having spent several hours getting a Teamspeak server to run on my vServer, I seem to have to report to a forum because I just can’t get anywhere.

My problem is relatively simple to explain: I set up a new Teamspeak server, which I connected to my Mariadb for the first time. Before I had done this, everyone could connect to the Ts. Only afterwards only those who have been connected before (can also be a great coincidence).

This means that the server is running, starts / stops properly, connects to the database without errors, but new users can´t connect.

I attached a couple of screens, which hopefully can help

Update: when a person connects with putty to the server, the person also can connect to the teamspeak afterwards. So it may hast to do with ssh keys? I don´t know anything about them, maybe someone can help but thats how everyone can join.

ts3db_mariadb.ini:
ts3db_mariadb.ini

ts3server.ini:

netstat:
netstat

ping over another network:
ping

teamspeak status:

first, simple question:

  • did u check the firewall?
  • required ports open?

Is the server activly refusing connections or do you host the teamspeak under a newly registered or changed domain? The problem might be, that the hostname can’t be resolved.

normally i am using a domain, but at the moment not because of testing.

For testing i allowed all ins and outs in ufw.
the port 9987 should be open as you can see at the netstat screenshot.
Or did i made a mistake?

Update: when a person connects with putty to the server, the person also can connect to the teamspeak afterwards. So it may hast to do with ssh keys? I don´t know anything about them, maybe someone can help but thats how everyone can join.

Did u also check the settings from host-panel? because it looks rly like a port-issue.

ssh keys has nothing to do with ts, you should be able to access all ts servers without accessing to ssh, in fact 99% of people who access a server don’t have ssh access

I don´t have any host-panel so there can´t be an issue.
Do you know another way to check if the port really is the problem?

Okay, i just wanted to mention that i works afterwards, i thought maybe this could help you finding a solution.

if you have the server on a vps or similar and not locally on your pc, which I think it is, ask your hosting support if you have any limitation on the ports

1 Like

Okay i do that

2 Likes