Your Post and Thread was moved or someone guided you to this thread because you did not provide enough details to help here.
We want to help but can't help, when our information only are like "I can not hear anyone" or "it does not work" or "I can't connect" or "client does crash"
We don't want to guess for every user who reports up to 0 details.
We need more information from you!
Always report (and please report as much as you can!):
- What client version is running?
- Offer us a Client log!
Logs can be found under %appdata%\TS3client\logs.
The current log can be viewed under Tools -> Client log.- What sound card and/or headset do you use?
- What operation system is running?
- Are all important OS updates installed?
- Are latest drivers (Sound Card, Network Card, USB devices, Graphics Card etc.) installed?
- Did it work before?
- What have you tried?
Your client has crashed (or does not start on Windows)?
Client 3.0.17 and newer automatically reports the crashdump to the developers.
There is nothing you need to do here.
You can do
- Install the latest client version from http://www.teamspeak.com/downloads
- Deactivate your custom plugins under Tools -> Options > Addons -> Plugins.
--> New in 3.1 start your client with parameter -safemode to make sure plugins aren't loaded.- Install latest Windows, Linux, OS X updates.
- Install latest drivers for graphics card and soundcard and mouse/keyboard
- Start your client with one of the following parameters:
--force-opengl-desktop
--force-opengl-soft
--force-opengl-angle- Make sure you are using a supported CPU with SSE2 feature enabled to run the client.
- Try the 32 or 64 bit client from http://www.teamspeak.com/downloads
You still want to report to us that your client is crashing?
Then please deliver us at least a crash report and some information about your client version and your system.
- Crash reports can be found under %appdata%/TS3client/crashdumps
- You can send us your system information by generating a DxDiag.txt.
Press Windows + R -> type dxdiag -> Press Save all information -> Attach the DxDiag.txt in your post.
You can't hear or talk? Your Device is disabled on server?
- What device do you use and are your drivers up to date?
- Please tell us your capture or playback settings.
- Check your default Capture and Playback devices
Especially for Windows 8.1 and newer > Check your default Communication devices.- Try to select your device directly and not default under Tools > Options > Playback or Capture.
- Is there a capture or playback profile set in your bookmark?
Please check your settings under Bookmarks > Manage Bookmarks > Click on "Go Advanced"- On Windows 10 after updating to version 1803 it is required that access to your microphone is enabled.
These 2 settings must be enabled:
- Microphone access for this device
- Allow apps to access your microphone
The settings can be found under Settings -> Privacy -> Microphone (left side)
You can also press Windows key + R and type in ms-settings:privacy-microphone to reach that setting.- Have you tried to send something with Push-To-Talk/Continuous Transmissions enabled?
- Is the slider in your capture profile set to high? Test and move it in the local test mode.
- Are you sure, that you channel isn't moderated and or you have enough talk power to speak in it?
- Check that the channel isn't in silence mode. This happens when a lot users (differs from server server to server via server setting) are in channel.
- Did your turn down the volume? Open Tools -> Options -> Playback and turn the Voice Volume Adjustment slider up.
- Is the client muted in the Windows volume mixer? Do a right-click on the speaker icon in your tray and then select Open Mixer to check this
You can't connect to a server?
- Make sure, that your server is not offline. Yes this happens sometimes.
In that case ask a buddy to connect to the server or contact your server host/the admin.- Try to connect to our test server first. Please try both links under this text for testing.
Click to connect to the DNS address or Click to connect to the IP address
- Are you sure, you did not block the client in your firewall?
- If it fails, check your firewall settings, maybe you have blocked the client or your disallowed UDP traffic through your router or firewall.
- If you can reach the server, ask their server provider for network problems or maybe your or their provider blocked your country.
- Make sure ,that the server host has opened port 9987 for UDP traffic
- Make sure your ISP allows voice programs which need UDP at all.
- When connecting to a computer in own network always use the LAN IP of that computer. Same counts for mobile clients when you are connected in WLAN.
- Hint: The client does not need any port forwarding. You only need to be able to connect via UDP to servers.
Also read this Thread for more possible fixes:
"Failed to connect to server" - Troubleshooting & Solutions
Additional connection problems in mobile client (Android and iOS)
Follow all steps above first!
- Use WLan when mobile connection is blocked from your mobile service provider or has a bad quality or an high ping.
- Check your connection quality in 3G/4G/WLAN network.
- Check your ping to target server.
- Allow the client to connect if you have a antivirus or firewall installed
You can't connect to a server after client update 3.1?
- The reason is an invalid SRV /TSDNS SRV record on target Domain (The address you are trying to connect to). The host did not add at least one A and/or AAAA SRV record on target Domain.
Client 3.0.x did ignore this wrong configuration, but client 3.1 can't ignore it any longer due RFC2782.- Only the server host can fix this.
Source:
- Much network related code has been improved when implementing IPv6 support. As a result the TeamSpeak Client now rejects most invalid SRV records. While some invalid SRV records were previously accepted and would work, this is no longer the case. Please see RFC2782 for proper SRV records.
- Additionally, TSDNS servers are now required to return IP address(es). This was always the only supported configuration (and the only intended one), however old clients also accepted domain name strings which the new client will not anymore as a result of improving the network code while implementing IPv6.
Most notable misconfiguration that previously may have worked, but will not work / be accepted by client 3.1.0 and newer:
- SRV records that have an IP address as target (Invalid as per the RFC)
- TSDNS servers returning strings that are not an IP address (never officially supported, now rejected).
When receiving a warning regarding an unsupported configuration upon connect it means that the domain you're connecting to is missing an SRV record.
You can connect to a server, but get disconnected after ~18 seconds/after minutes?
We call this a timeout and this is a network problem there can be several reasons:
- Your ping or packet loss to that server is to high.
- Your firewall or security center does block the traffic to that server. Maybe your settings need to a change here?
- Your router detects the traffic as spam or as an attack. Please check that there is nothing like this running.
- You could try to disable such settings for testing or set your LAN Ip to DMZ (Remove DMZ after testing!!!!)
- Maybe your W-Lan connection is not that good? Try a Lan cable instead for testing.
- The servers ping or packet loss is for your connection is to high.
- The server does have more then 1 IP and the hoster did nothing yet, to bind one of his IP's to his server.
It can work without the IP binding and it can be random, that a user can connect or gets disconnected after 18 seconds.
Sometimes a user can connect but is stuck in the lobby and the client does not react to for any user interaction.
Please try to connect to our test server first. Please try both links under this text for testing.
Click to connect to the DNS address or Click to connect to the IP address
You have problem with your hotkey or hotkeys?
Please tell us what keyboard, mouse, joystick and gamepad you are using.
Tell us your current hotkey system from TeamSpeak (find it under "Tools > Options > Hotkey").
- Are you using software for your input device? (In that case try to deliver your profiles)
- Is there a capture or playback profile set in your bookmark?
Please check your settings under Bookmarks > Manage Bookmarks > Click on "Go Advanced"
Your CPU does use ~30% and more?
Please try to disable our Echo reduction and Echo cancellation under Tools > Options > Capture
Also make sure, that your sound driver is up to date!
Overwolf bug reports, problems or help
Overwolf is an own product and developed by the Overwolf Team.
To get in touch with the Overwolf developers, please visit http://forums.overwolf.com/.
Supported Games > http://www.overwolf.com/Supported-Games