You can't connect to a server? // Can not connect to the server

[makiatto]

@LeonMarcelHD Can you please stop merging every issue on this topic into this thread. I even complained about this in my original post, which still got merged. This thread is a mess and impossible to follow for troubleshooting.

If there is a finite amount of possible causes for this, make a support article and reply to new threads with that + the post mentioning the regional capacity. That way, if someone fixes their issue with one of your team’s suggestions, the thread gets closed, rather than further clogging up this topic.

If their issue is outside of the suggested troubleshooting, they can actually get help/feedback instead of their case getting lost in this topic.

Right now, this thread is an incomprehensible mess that combines people troubleshooting self-hosted and official communities. It makes sense to at least separate those two into different topics since the same troubleshooting is not applicable to both.

[makiatto]

Worth noting TS is getting an unexpected number of signups at the moment, so server capacity might be the culprit of this. I’m also having trouble with the AM region

Communities Region Capacity | Feb 2026

We’ve seen an incredible surge of new users joining TeamSpeak and subscribing to communities. As a result, hosting capacity has been reached in many regions, especially in the United States. We’re actively working on expanding availability across additional regions. We’ll keep you updated as capacity expands. Thank you.

[LeonMarcelHD]

@TS.ChrisR

Troubleshooting for TeamSpeak Communitys

• If you are using a Community, it might take a bit until the server is started and all network changes are made before you are able to connect. Based on the demand of servers that are created this may take a few minutes or even a few hours. We apologize in the meantime for the inconvenience.
• If you still have issues when connecting, you may try suspending and creating a new one.
• Sometimes it is helpful when you select a different server location.
• If you still can not connect the Community, please reach out to [email protected], they are able to restart the server, or perform refunds if you are unsatisfied with the current situation.

---

The original post are troubleshooting steps to do when a connection fails, we even provide details on what to do if they are waiting on a community to start up.

We also published an announcement that creation may take some time / our servers are at max capacity and that some regions may not be available. This topic is globally pinned and should help any user that lands here.

Communities Region Capacity | Feb 2026

We’ve seen an incredible surge of new users joining TeamSpeak and subscribing to communities. As a result, hosting capacity has been reached in many regions, especially in the United States. We’re actively working on expanding availability across additional regions. We’ll keep you updated as capacity expands. Thank you.

---

Merging all of those posts is the only viable solution, with such an influx of users which we are currently experiencing.

In terms of moderation capacities we are also at our limit. Here in the forum we’ve seen day to day traffic 5-7x the amount we’re used to. Our support team has also an immense amount of new tickets that need to be reviewed/replied to.

---

Thank you for your patience as we scale to meet the growing demand!

For all of you that are currently waiting for their server to start up:

We also have plenty of Official TeamSpeak Community Servers, hosted by us and free for anyone to use, with screensharing available.

NA: https://tmspk.gg/Zqz1It54
EU: https://tmspk.gg/XBvZG6TH
APAC: https://tmspk.gg/ob4QJQHM
SA: https://tmspk.gg/biWngDIa
EMEA: https://tmspk.gg/Xp8POVY7

[OutOfPosition]

I created my own community to replace discord but i cant claim it. The link works but i get a ERROR every time i try to join it in the app. google told me to wait for some time but its over an hour ago and nothing changed.

[JunWasAlreadyTaken]

same region too

[tamerotamer]

Hello,

I purchased a TeamSpeak Community (Teams).

Claiming the community redirects to TeamSpeak 6 but fails with
“failed connection initialization”.

how can i fix this?

same here…

[Orchida]

Okay but like, we paid money to get our own server. If we wanted to use Official servers than we would be doing just that.

but now instead of a real explanation we just get to grasp at troubleshooting on what should be a click and done process. Meanwhile our clocks for the subscriptions are already ticking and its just being chalked down to basically whatever.

I get that a new influx of people can always bring issues space wise, but its a bit annoying not to tell users about to buy a server / community that they just wont be able to access it even after its paid for and myteamspeak gives them the heads up.

[makiatto]

Please warn/prevent users from buying a community subscription while the capacity issue is being resolved. I also sincerely hope you intend to compensate the downtime that your users are paying for by offsetting the subscription end dates appropriately.

I fully understand you are being overwhelmed by the amount of new users, but transparency is key right now in order to secure long term customers instead of losing them the second they come through your door.

The main problem is people are able to buy subscriptions with no indication that they can’t actually use the product right away. THEN, after they run into errors, they come to the forum and learn about the issue, and that there is no clear timeline for it being resolved. All of this looks really bad for TS, unfortunately. Staggering / restricting new community subscriptions while you increase capacity is the most sensible course of action imo.

[Orchida]

This exactly

[LeonMarcelHD]

We’re extremely short on staff during the weekend, even if someone is working. We have a handful (literally a handful) of developers, and if they are not available, our options are limited. General staff doesn’t have access to add a custom banner that displays on myTS.

We can’t do much more than post here, pin the post globally, or post on X.
We always aim to satisfy our users. If someone is not happy with the service, they can request a refund or partial compensation as mentioned above.

@TS.ChrisR

If you still can not connect the Community, please reach out to [email protected], they are able to restart the server, or perform refunds if you are unsatisfied with the current situation.

---

The timeline is to have it fixed as soon as possible when the developers are back in the office. Since they are not here to provide an ETA, we basically don’t know.

[makiatto]

Thank you for the reply. Tech issues on the weekend are indeed rough. I wish you guys the best of luck in responding to this surge of users.

[BigBossJuice]

i got a server (yearly) and i come to connect to it for me and my friends. and im getting ‘failed to establish connection’ im not sure if i should proceed for a refund ? or help with this fix please ??

[TS_Dennis]

Thank you for your patience while we investigated the issue.

We’ve identified the root cause, and the problem should now be resolved for the ams3 region.

If you’re still experiencing any issues, please let us know here and we’ll be happy to assist further.

[Syphora]

AMS3, started the community yesterday, it is still not claimable. Thank you very much in advbance.

[SpiritGas]

New to TS and this community has been ‘starting’ for like 48 hours.

I am not on firefox

[LeonMarcelHD]

Please reach out to [email protected], they are able to restart the server since it will probably never spawn with 48h passes since starting.

[thataliencat]

I just bought a community from the official teamspeak, but when i try to go claim it, i get and error saying it failed to establish connection to teamspeak server with the reason that it could not resolve hostname.
Not sure whats happening.

nvm, it worked, it was updating but wasnt showing

[thedevjade]

I have a layered setup on a ovhcloud dedicated server, I have proxmox with a vm for pelican panel that has teamspeak 6 hosted on it, currently I can connect to it from my own computer. However, my friends cannot connect to it. I cannot figure it out

here are logs

pelican@blacksiteteamspeak ~ Server marked as running…
:/home/container$ ./tsserver --filetransfer-port 30033 --query-http-port 10080 --query-ssh-port 10022 --default-voice-port 9987 --query-admin-password blacksitealphapass55020 --query-log-commands --query-ssh-enable
2026-02-19 06:49:59.179305|INFO |ServerLibPriv | |TeamSpeak Server v6.0.0-beta8 (2026-01-22 10:21:30)
2026-02-19 06:49:59.179417|INFO |ServerLibPriv | |SystemInformation: Linux 6.8.0-100-generic #100-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 13 16:40:06 UTC 2026 x86_64 Binary: 64bit
2026-02-19 06:49:59.179615|INFO | | |checking database integrity (may take a while)
2026-02-19 06:49:59.182347|INFO |ServerLibPriv | |updated server query admin password
2026-02-19 06:49:59.185211|WARNING |Accounting | |Unable to open /home/container/licensekey.dat
2026-02-19 06:49:59.185258|INFO |Accounting | |Licensing Information
2026-02-19 06:49:59.185266|INFO |Accounting | |licensed to : TeamSpeak Systems GmbH
2026-02-19 06:49:59.185272|INFO |Accounting | |type : No License
2026-02-19 06:49:59.185282|INFO |Accounting | |starting date : Thu Jan 15 00:00:00 2026
2026-02-19 06:49:59.185291|INFO |Accounting | |ending date : Fri May 1 00:00:00 2026
2026-02-19 06:49:59.185299|INFO |Accounting | |max virtualservers: 1
2026-02-19 06:49:59.185306|INFO |Accounting | |max slots : 32
2026-02-19 06:49:59.239984|INFO | | |Precomputing puzzle, this may take some seconds…
2026-02-19 06:49:59.880599|INFO | | |Puzzle precompute time: 641
2026-02-19 06:49:59.880822|INFO |FileManager | |listening on 0.0.0.0:30033, [::]:30033
2026-02-19 06:49:59.881155|INFO |Query | |Using a query thread pool size of 2
2026-02-19 06:49:59.885401|INFO |VirtualServerBase|1 |listening on 0.0.0.0:9987, [::]:9987
2026-02-19 06:49:59.885721|INFO |Query | |listening for ssh query on 0.0.0.0:10022, [::]:10022
2026-02-19 06:49:59.885823|INFO |CIDRManager | |updated query_ip_allowlist ips: 127.0.0.1/32, ::1/128, 15.235.61.61/32,
2026-02-19 06:50:00.305737|INFO | | |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2026-02-19 06:50:03.010744|INFO |Query | |query from 1 15.235.61.61:50222 issued: login with account “serveradmin”(serveradmin)
2026-02-19 06:50:03.176351|INFO |Query | |query from 1 15.235.61.61:50222 issued: use -virtual port=9987 client_nickname=DiscordBot
2026-02-19 06:50:59.521119|INFO |Accounting | |Default license report sent successfully
2026-02-19 06:52:40.129690|DEVELOP |VirtualServer |1 |Found 0 server group assign entries for permission migration
2026-02-19 06:52:40.129989|INFO |VirtualServerBase|1 |client connected ‘PV2 Alyx “Solvane” Vance’(id:3) using a myTeamSpeak ID (AR6q514Rrj3aSmqBCSnTHl+D76KUSzDJmjATviofNROO) from 67.161.70.184:50566

TCPDUMP

Summary

06:30:09.546585 pelican0 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:09.546589 veth675b4b3 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:09.546708 veth675b4b3 P IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:09.546708 pelican0 In IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:09.546718 ens18 Out IP ip62.ip-15-235-61.net.9987 > 67.161.70.184.59384: UDP, length 13 06:30:09.712607 ens18 In IP 67.161.70.184.59384 > ip62.ip-15-235-61.net.9987: UDP, length 13 06:30:09.712624 pelican0 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:09.712629 veth675b4b3 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:09.712741 veth675b4b3 P IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:09.712741 pelican0 In IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:09.712755 ens18 Out IP ip62.ip-15-235-61.net.9987 > 67.161.70.184.59384: UDP, length 13 06:30:09.888405 ens18 In IP 67.161.70.184.59384 > ip62.ip-15-235-61.net.9987: UDP, length 13 06:30:09.888433 pelican0 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:09.888438 veth675b4b3 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:09.888555 veth675b4b3 P IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:09.888555 pelican0 In IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:09.888579 ens18 Out IP ip62.ip-15-235-61.net.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.059187 ens18 In IP 67.161.70.184.59384 > ip62.ip-15-235-61.net.9987: UDP, length 13 06:30:10.059205 pelican0 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:10.059209 veth675b4b3 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:10.059323 veth675b4b3 P IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.059323 pelican0 In IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.059335 ens18 Out IP ip62.ip-15-235-61.net.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.241743 ens18 In IP 67.161.70.184.59384 > ip62.ip-15-235-61.net.9987: UDP, length 13 06:30:10.241758 pelican0 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:10.241762 veth675b4b3 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:10.241857 veth675b4b3 P IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.241857 pelican0 In IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.241866 ens18 Out IP ip62.ip-15-235-61.net.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.415345 ens18 In IP 67.161.70.184.59384 > ip62.ip-15-235-61.net.9987: UDP, length 13 06:30:10.415355 pelican0 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:10.415358 veth675b4b3 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:10.415462 veth675b4b3 P IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.415462 pelican0 In IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.415474 ens18 Out IP ip62.ip-15-235-61.net.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.590360 ens18 In IP 67.161.70.184.59384 > ip62.ip-15-235-61.net.9987: UDP, length 13 06:30:10.590388 pelican0 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:10.590393 veth675b4b3 Out IP 67.161.70.184.59384 > 172.18.0.3.9987: UDP, length 13 06:30:10.590535 veth675b4b3 P IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.590535 pelican0 In IP 172.18.0.3.9987 > 67.161.70.184.59384: UDP, length 13 06:30:10.590547 ens18 Out IP ip62.ip-15-235-61.net.9987 > 67.161.70.184.59384: UDP, length 13 ^C 342 packets captured 342 packets received by filter 0 packets dropped by kernel jade@pelican:~$

Port is confirmed open via nmap and tcpdump

1. Packets flow correctly through Pelican/Docker to container and back
2. Server logs show no connection attempt from other clients at all
3. Fresh myTeamSpeak accounts also fail
4. Only the first/host client can connect (and only me)
5. Error on client side: “failed connection initialization”

[Antiheroeh]

Hello!

I just suscribe a crew plan from TS6, I create a community but is stucked in Starting community and obviously I can connect to it, how many time takes the community to be up and available?

Thanks!

[fuckarasaka]

same. stucked in Starting community. need help ASAP.