Hey,
after a long time, its now time to announce the closed alpha testing phase of the TeaSpeak Web client!
As many of you know, I'm already working over a few months on the Web Client, and I'm very proud the whole project, and it's first big advantage: The WebClient!
Caused by the fact, that nothing is perfect, when it's get released, i start with a closed alpha test phase.
How could i setup my own TeaSpeak server with web compatibility?
Well this is a little bit harder, caused by the reason that you need a valid SSL certificate.
A more detailed manual could you find here: <a url>
I can't connect to my own server!
Well this is a common problem.
Cause to the security policy of web rtc, you can just access the microphone when the side is secure (https).
This also includes all connections like web sockets, so they have to be ssl encrypted as well.
Cause most browsers does not allow self signed certificate, and block any connect attempts, you can't connect.
We'll you're now asking how you could fix this,and I tell you this is more simple that you thought.
You just have to connect to the remote address (and port!) via https, accept the certificate and you will be able to access the server. Another solution is to create a valid ssl certificate (e.g. With Letsencrypt) and register it in your TeaSpeak server.
Where can I report a bug?
Its nearly the same system, like you report a bug for the TeaSpeak server.
Just create an issue under the TeaSpeak-Web Github project (https://github.com/TeaSpeak/TeaSpeak-Web)
What is already implemented within the WebClient?
According to the fact, that the TeaSpeak-Web client is a very new project, it hasn't so much futures, but the basics are already implemented.
Here is a list of the already implemented futures of the Web-Client:
- Connect to any TeaSpeak server
- Use a Tea*Speak identity or just verify over this forum
- Channel create, edit and modify
- Server, Channel and Client icons
- Voice communication (Opus Voice & Music only)
- Push to talk
- Voice activity detection
- Always active
- Channel tree view & Detailed entry information view
- Basic chat system (no empties and sometimes really wired format)
And at least: Screenshots!
*** EDIT ****
The Web-Client is now open souce.
after a long time, its now time to announce the closed alpha testing phase of the TeaSpeak Web client!
As many of you know, I'm already working over a few months on the Web Client, and I'm very proud the whole project, and it's first big advantage: The WebClient!
Caused by the fact, that nothing is perfect, when it's get released, i start with a closed alpha test phase.
How could i setup my own TeaSpeak server with web compatibility?
Well this is a little bit harder, caused by the reason that you need a valid SSL certificate.
A more detailed manual could you find here: <a url>
I can't connect to my own server!
Well this is a common problem.
Cause to the security policy of web rtc, you can just access the microphone when the side is secure (https).
This also includes all connections like web sockets, so they have to be ssl encrypted as well.
Cause most browsers does not allow self signed certificate, and block any connect attempts, you can't connect.
We'll you're now asking how you could fix this,and I tell you this is more simple that you thought.
You just have to connect to the remote address (and port!) via https, accept the certificate and you will be able to access the server. Another solution is to create a valid ssl certificate (e.g. With Letsencrypt) and register it in your TeaSpeak server.
Where can I report a bug?
Its nearly the same system, like you report a bug for the TeaSpeak server.
Just create an issue under the TeaSpeak-Web Github project (https://github.com/TeaSpeak/TeaSpeak-Web)
What is already implemented within the WebClient?
According to the fact, that the TeaSpeak-Web client is a very new project, it hasn't so much futures, but the basics are already implemented.
Here is a list of the already implemented futures of the Web-Client:
- Connect to any TeaSpeak server
- Use a Tea*Speak identity or just verify over this forum
- Channel create, edit and modify
- Server, Channel and Client icons
- Voice communication (Opus Voice & Music only)
- Push to talk
- Voice activity detection
- Always active
- Channel tree view & Detailed entry information view
- Basic chat system (no empties and sometimes really wired format)
And at least: Screenshots!
*** EDIT ****
The Web-Client is now open souce.
Last edited:
