Forum

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Server 3.1-3.2 do not load default license

So today my server messed up. Once people disconnected and went to reconnect no one could reconnect. I restarted the server and went to start it again. I get the error "|CRITICAL|Accounting | |Failed loading default license file!" which in the log says

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.

Which I already have the file in there and everything is set to accept. After this I tried starting it with ./ts3server_minimal_runscript.sh to see more details. Which I saw it tried to do this first "|WARNING |Accounting | |Unable to open licensekey.dat, falling back to limited functionality".

After that I get the first error with not being able to load the default license file.

Last edited by dante696; September 1st, 2018 at 11:59 AM.
Reason: merged

I have not made any changes to the install and haven't even touched pfSense in a while, this happened randomly about half an hour ago. I tried google searching that license error and got no results. Log says "Unable to open licensekey.dat" as well. Not sure how to fix because I've never had a licensekey.dat file and have no idea why my server is suddenly trying and failing to load it.

Updating to 3.3.1 appears to have fixed the issue. I don't know why my server would suddenly and randomly take itself offline and refuse to come back online due to a license issue. Can anyone from tech support explain why this happened and how to keep it from happening in the future? I was maybe 1 version behind on the server and I'm not exactly thrilled that my server, without my touching it, can decide to stop working over a license issue.

Unable to start Teamspeak3-Server

Hello.

Today I tried to start my Teamspeak 3 Server again after rebooting because nobody could connect to my server even though there were clients online. This error came up when i tried to start the server after shutting it down:

Server 3.1-3.2 do not load default license

I have never had a license so I'm not sure why this issues suddenly started. After viewing a log from a month ago it appears a default license is created with an expiration date. How do I remove/replace this "default license". Again, I have no need for anything other than the free 32 slot version of the server. Latest log and a log from over a month ago are attached via jpg image.

Attached Images

Last edited by dante696; September 1st, 2018 at 11:27 AM.
Reason: merged

Error creating ephemeral license: EXPIRED

Hi, since 2 hours i getting this error message and i can't find anything about it: Error creating ephemeral license: EXPIRED
I'm running the latest teamspeak server on debian 8.1 linux root server. The Server stoppet working, then i updated to the latest version. Since then i cant start it anymore.
when i start it i get this message:
2018-09-01 02:03:17.583750|CRITICAL|VirtualSvrMgr | |Could not start file manager 258 no network port available

Updating to 3.3.1 appears to have fixed the issue. I don't know why my server would suddenly and randomly take itself offline and refuse to come back online due to a license issue. Can anyone from tech support explain why this happened and how to keep it from happening in the future? I was maybe 1 version behind on the server and I'm not exactly thrilled that my server, without my touching it, can decide to stop working over a license issue.

This happened to me, too, using server 3.2.0. I noticed these lines in the log from when I started the server on July 22: