starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #1806] teamspeak automatic licence acceptance fail #1415

New issue

Closed

opened 2026-02-27 02:56:57 +03:00 by kerem · 14 comments

kerem commented

2026-02-27 02:56:57 +03:00

Owner

Originally created by @naxIO on GitHub (Feb 15, 2018).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1806

Originally assigned to: @UltimateByte on GitHub.

Every time Teamspeak updates its licence, it enforces clients and servers to agree to it, otherwise the server or client wont start.

I just found my TS broken with an entire log file directory full of accept_license_error logs.

In order to resolve this issue, a file called .ts3server_license_acceptedneeds to be present in the TS3 root directory. We should think about adding that automatically, additionally pass a parameter for auto-accept new licences automatically or not (if you want to read it first.)

I post in this repository because it seems that remarks in the server config repository are ignored / not read at all.

Originally created by @naxIO on GitHub (Feb 15, 2018). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1806 Originally assigned to: @UltimateByte on GitHub. Every time Teamspeak updates its licence, it enforces clients and servers to agree to it, otherwise the server or client wont start. I just found my TS broken with an entire log file directory full of accept_license_error logs. In order to resolve this issue, a file called ``` .ts3server_license_accepted```needs to be present in the TS3 root directory. We should think about adding that automatically, additionally pass a parameter for auto-accept new licences automatically or not (if you want to read it first.) I post in this repository because it seems that remarks in the server config repository are ignored / not read at all.

kerem

2026-02-27 02:56:57 +03:00

closed this issue
added the
type: bug

type: feature

outcome: issue resolved

game: Teamspeak 3
labels

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@SB97 commented on GitHub (Feb 15, 2018):

This problem is also present on the first install

Getting privilege key
=================================
IMPORANT! Save these details for later.
Starting the TeamSpeak 3 server
Please set the environment variable TS3SERVER_LICENSE to "accept" in order to accept the license agreement.
Alternatively, create a file named ".ts3server_license_accepted" in the working directory or start the server with the command 
line parameter "license_accepted=1".
To view the license agreement set TS3SERVER_LICENSE to "view" in order to print the license to the console.
Alternatively view the file "LICENSE" in your favorite text viewer yourself.
TeamSpeak 3 server could not start
No server running (ts3server.pid is missing)
    fetching fix.sh...OK

@SB97 commented on GitHub (Feb 15, 2018): This problem is also present on the first install ``` Getting privilege key ================================= IMPORANT! Save these details for later. Starting the TeamSpeak 3 server Please set the environment variable TS3SERVER_LICENSE to "accept" in order to accept the license agreement. Alternatively, create a file named ".ts3server_license_accepted" in the working directory or start the server with the command line parameter "license_accepted=1". To view the license agreement set TS3SERVER_LICENSE to "view" in order to print the license to the console. Alternatively view the file "LICENSE" in your favorite text viewer yourself. TeamSpeak 3 server could not start No server running (ts3server.pid is missing) fetching fix.sh...OK ```

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@UltimateByte commented on GitHub (Feb 16, 2018):

Is this a new thing? Never experiences that issue.

@UltimateByte commented on GitHub (Feb 16, 2018): Is this a new thing? Never experiences that issue.

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@SB97 commented on GitHub (Feb 16, 2018):

never had it bevore... but just yesterday i wanted to set up a new TS3 Server and it happend

https://forum.teamspeak.com/threads/134874-TeamSpeak-3-Server-3-1-0-released
found the problem...

**Important:**
You will have to accept the server license agreement before being allowed to use the server. See doc/server_quickstart.txt in the server download or this FAQ for information on how to do that. If you attempt to start the server without accepting the license you will get an error log file created with instructions as well. On Linux systems this information will also be printed to console. The license can be found in the LICENSE file or license.txt (depending on platform).

@SB97 commented on GitHub (Feb 16, 2018): never had it bevore... but just yesterday i wanted to set up a new TS3 Server and it happend https://forum.teamspeak.com/threads/134874-TeamSpeak-3-Server-3-1-0-released found the problem... ``` **Important:** You will have to accept the server license agreement before being allowed to use the server. See doc/server_quickstart.txt in the server download or this FAQ for information on how to do that. If you attempt to start the server without accepting the license you will get an error log file created with instructions as well. On Linux systems this information will also be printed to console. The license can be found in the LICENSE file or license.txt (depending on platform). ```

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@UltimateByte commented on GitHub (Feb 16, 2018):

Well, now we perfectly understand the issue. Thanks.

@UltimateByte commented on GitHub (Feb 16, 2018): Well, now we perfectly understand the issue. Thanks.

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@gOOvER commented on GitHub (Feb 17, 2018):

https://support.teamspeakusa.com/index.php?/Knowledgebase/Article/View/344/16

@gOOvER commented on GitHub (Feb 17, 2018): https://support.teamspeakusa.com/index.php?/Knowledgebase/Article/View/344/16

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@UltimateByte commented on GitHub (Feb 20, 2018):

I PRed a fix. Fixes existing installs. Probably fixes new installs as well, but didn't test yet.

@UltimateByte commented on GitHub (Feb 20, 2018): I PRed a fix. Fixes existing installs. Probably fixes new installs as well, but didn't test yet.

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@SB97 commented on GitHub (Feb 21, 2018):

Probably fixes new installs as well, but didn't test yet.

If you tell me how i can test :)

@SB97 commented on GitHub (Feb 21, 2018): `Probably fixes new installs as well, but didn't test yet.` If you tell me how i can test :)

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@UltimateByte commented on GitHub (Feb 21, 2018):

You just need to change your ts3server script's github repository to : hotfix/teamspeak-180220
Then install. Would be awesome if you could test and feedback :)

@UltimateByte commented on GitHub (Feb 21, 2018): You just need to change your ts3server script's github repository to : hotfix/teamspeak-180220 Then install. Would be awesome if you could test and feedback :)

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@SB97 commented on GitHub (Feb 21, 2018):

you mean that bevore i install, i change the "master" in the script to "hotfix/teamspeak-180220" and than just ./ts3server install ?

@SB97 commented on GitHub (Feb 21, 2018): you mean that bevore i install, i change the "master" in the script to "hotfix/teamspeak-180220" and than just ./ts3server install ?

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@UltimateByte commented on GitHub (Feb 21, 2018):

yep, should work

@UltimateByte commented on GitHub (Feb 21, 2018): yep, should work

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@SB97 commented on GitHub (Feb 21, 2018):

tried it but didn´t get the hotfix repository...
https://gist.github.com/SB97/5b6a9e9be7a0485b98cbbb1c68e9ccac

will try again tomorow

@SB97 commented on GitHub (Feb 21, 2018): tried it but didn´t get the hotfix repository... https://gist.github.com/SB97/5b6a9e9be7a0485b98cbbb1c68e9ccac will try again tomorow

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@UltimateByte commented on GitHub (Feb 23, 2018):

After examinating the Travis test, it seems like the fix didn't work for new installs. I need to work on it a bit more.

@UltimateByte commented on GitHub (Feb 23, 2018): After examinating the Travis test, it seems like the fix didn't work for new installs. I need to work on it a bit more.

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@UltimateByte commented on GitHub (Feb 27, 2018):

Fixed.

@UltimateByte commented on GitHub (Feb 27, 2018): Fixed.

kerem commented

2026-02-27 02:56:58 +03:00

Author

Owner

@lock[bot] commented on GitHub (Mar 13, 2019):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Mar 13, 2019): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:54:08 +03:00

[PR #1415] [CLOSED] Update install_server_files.sh #3333