[Discussion] TeamSpeak Server 3.8.0 Beta

[numma_cway]

My tests proved that I can send 8150 characters as text with a ServerQuery bot (will that be the new limit? such an odd number, I'd expect something like 10000)

It is technically impossible to send a 10,000-character message. TeamSpeak commands are limited to 9203 bytes.

The limit is actually 8192 (which is not an odd/random number) single byte characters.
The client is still limited to 1024, since there was no update yet (other than the security fix in 3.2.5).

Note that the client incorrectly counts escaped query characters (e.g. space) as two bytes, while the servers counts them as one byte in terms of the limit of the single parameter. This also exists for other limits like channel descriptions and offline messages. Offline messages are even limited by 4096 characters no matter what type.
Calculating the limit correctly (by still taking into account the 9203 byte command limit) however isn't that easy.

[bulgarianpl]

|ERROR |DatabaseQuery | |db_exec() insert into temporary_passwords( server_id, temporary_password_hash, error: NOT NULL constraint failed: temporary_passwords.temporary_password_value

I can not set any temporary password.

[dante696]

This report opens a book full of questions for me.

• What operation system is this happening on?
• Are you sure that you did extract and overwrite all files for the update? If not this causes a faulty database and result like that one appear.
• Is the database a SQlite or MariaDB database? And if this is a MariaDB dataabse which version and on which operation system is it running?
• How do you set it (client or ServerQuery)?
• What do you set? (Password only or with channel or with description)?
• What do you set there? Any special char included?

Please try following:

1. Turn of the server and then make a backup of the database or rename the database.
2. Start the serve again and set a temporary password.
   ->> If that worked then something went wrong during the update (need the server log 0)
   
   ->> If that still did crash: then i suggest to download the server package again and then extracr overwrite the all existing files. Try again without that database

[bulgarianpl]

This report opens a book full of questions for me.

• What operation system is this happening on?
• Are you sure that you did extract and overwrite all files for the update? If not this causes a faulty database and result like that one appear.
• Is the database a SQlite or MariaDB database? And if this is a MariaDB dataabse which version and on which operation system is it running?
• How do you set it (client or ServerQuery)?
• What do you set? (Password only or with channel or with description)?
• What do you set there? Any special char included?

Please try following:

1. Turn of the server and then make a backup of the database or rename the database.
2. Start the serve again and set a temporary password.
   ->> If that worked then something went wrong during the update (need the server log 0)
   
   ->> If that still did crash: then i suggest to download the server package again and then extracr overwrite the all existing files. Try again without that database

I fixed it, i had to edit the sqlite database


https://i.imgur.com/yUtsren.png

[dante696]

I did retest the thing because your fix looks different from a server database where it is working.

What you found there seems to be a bug when you update the server. That worked during our tests but now it's broken.
It's fine when server had no database before or when MariaDB is in use.

I will report this to our developers and it will be fixed with stable release.

[nutellazpw-]

When will be released stable version ?

[Dorde]

When will be released stable version ?

(=== Server Release 3.8.0 20 May 2019)

Just read the beta changelog:
https://forum.teamspeak.com/threads/...ver-3-8-0-Beta

[Well_Skilled]

Hey. I just want to report that there is a problem with the badges on server version 3.8.0 beta and above. I can only see my own badges. I cannot see other clients badges.

[Dorde]

Hey. I just want to report that there is a problem with the badges on server version 3.8.0 beta and above. I can only see my own badges. I cannot see other clients badges.

You need to wait for client >=3.3.0 .

Btw the changelog says(https://forum.teamspeak.com/threads/...ver-3-8-0-Beta):

Important: Client badge information is now signed to prevent using fake data. Badges
in the old format will not be visible on this server. New clients with
support for signed badges will be available soon.

[X3r0X]

Hello,
the ts3server_startscript.sh is faulty in both releases.

COMMANDLINE_PARAMETERS="" #add any command line parameters you want to pass here

should be

ADDITIONAL_COMMANDLINE_PARAMETERS="" #add any command line parameters you want to pass here

Which ini file is being loaded as default or do I've to specifiy this in my startscript? (ts3server.ini)

Cheers

[dante696]

The issue was reported before and will fixed in beta 2 (possible release today).

No ini file is loaded by default. You can add the start parameter inifile=ts3server.ini if plan to use that ini file.

[X3r0X]

Thank you and sry for not seeing the discussion thread. Will continue to use the inifile parameter.

[Dragon34]

Hello it seems to me that the codex had to be permanently deleted on this version

b_channel_create_modify_with_codec_speex8
b_channel_create_modify_with_codec_speex16
b_channel_create_modify_with_codec_speex32
b_channel_create_modify_with_codec_celtmono48

• The permissions for ancient audio codecs Speex and CELT got removed.
  The codecs can not be set on channel anymore. Channels where the codec was set before still can be used.
  In future release we will drop these codecs completely.

[dante696]

Yes. This happened in version 3.7.0 already.
https://forum.teamspeak.com/threads/...3-Server-3-7-x


Edit after your edit
I have no idea any longer about what you try to tell us. You pasted the important part already.

[Dragon34]

Yes. This happened in version 3.7.0 already.
https://forum.teamspeak.com/threads/...3-Server-3-7-x


Edit after your edit
I have no idea any longer about what you try to tell us. You pasted the important part already.

I always see them