I set up Teamspeak server and other software as services using Microsoft's own tools years ago. Can't remember how I did it but try this link
...

It's a very long time since I created our SRV record, and I have questions about yours -

You seem to be setting it to unverschämt-frech.de rather than ts.unverschämt-frech.de

Why are you then...

If you have done this it looks like you haven't done it correctly

[[email protected] ~]# dig ts.unverschämt-frech.de


; <<>> DiG 9.11.5-P4-RedHat-9.11.5-4.P4.fc29 <<>> ts.unverschämt-frech.de
;;...

I've had a license for years, and for most of that time it was a 10 / 512, but it's my understanding at some point in the past they changed all NPLs to 2 / 512. That's why I was surprised at the...

Hi all,

Was just checking my Teamspeak logs because my NPL was due to expire tomorrow. Was surprised to find that it's already been renewed and with a ten virtual server limit instead of two
...

This is the official download page

https://www.teamspeak.com/en/downloads/#

I've no idea who teamspeak-services.com are

Why do you think having one server running all the time is not recommended? That's what servers do, run all the time

I'm sure I read somewhere on this forum (possibly posted by dante) that backupaccounting2 doesn't even exist, so why the server software is set to poll it I've no idea

p.s. no errors for a few...

Now been 24 hours, this thread is marked as Resolved so are any Teamspeak staff reading it?

Yep, giving a 502 Bad Gateway error

Last error at 09:36 GMT, so all good here, though I don't understand why some servers were being shut down frequently, I was getting the error for four days and never had one shutdown

How long have you been getting the error? I've been getting it for three days and still have a running server

I'm seeing this error as well, but it hasn't affected my server in any way. Show full logs, there might be something else causing your server shutdown

There might be no Teamspeak logs generated, but have you checked the Windows System and Application logs?

You mentioned Kaspersky, but is the standard Windows firewall running as well?

NPL has (I think) been 6 months for a very long time. Do what dante says in post #5, if your details still match the old license you'll have a new one in a few days

It was announced nearly a year ago

http://www.teamspeak.com/?page=newsarchive&ident=20140604

Nothing in there about opening the correct ports on your firewall (use search, this information is readily available)

What ticket system? This doesn't sound like a Teamspeak issue per se

Use the startup scripts as Dante696 states

But looking at your error I suspect you've upgraded from a Linux that was using init scripts to one that now uses Systemd

Plenty of information in the...

The license should be readable in a text editor, if it isn't it's probably corrupt and needs to be downloaded again

Have you checked your logs to see that the license was accepted / usable?

1) Are you sure you're looking at the WAN IP in your router?

2) This is just a guess (because I've read about it somewhere) but it's slightly possible your broadband is on a natted connection,...

So where did you get your WAN IP from?

You should be able to ge the correct one from here https://www.whatismyip.com/

Scratch the above (I think), perhaps your router is sending the wrong IP to...

If the packet loss annoys you don't look at it. You've stated voice quality is fine so be happy with that :)

Not a bug, the server is running, you have network issues that are nothing to do with Teamspeak

Are you having problems with voice quality? I personally wouldn't worry about those packet loss figures (and you'll never get them to 0% anyway), I'd be more worried about your ping time

Because it's not a useful function? (but is already built in to the client)

If clients think it's unnecessary they'll turn it off

I don't think you can stop that message appearing. If you were to supply logs etc. someone here might be able to tell you why the latest version isn't working for you

Very probable that your external IP (the one supplied by your ISP) or the IP given to the machine hosting your Teamspeak server has changed because of DHCP. If it's the internal IP that's changed...

'TS3ANetwork::ResolveHostName failed error'

Nothing weird here, a quick search of these forums would have shown you that a handful of these errors will result in your server being shut down due to...

What version did you update from?

Server logs might be useful

Well in CentOS I'd probably find it in /var/log/messages, but for Ubuntu you're going to have to use Google

Forget the Teamspeak logs, you need to be checking the Linux server logs to see why it's sending Teamspeak sigterms.

And the accounting server doesn't respond to ping or traceroute.