TeamSpeak Server Crack 3.0.12.2

[texwiller]

it is possible that some of it is wrong, because their server does not resolve the domain name

Just test example : ping ipcheck.teamspeak.com

Normally result is :

Pinging ipcheck.teamspeak.com [127.0.0.1] with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Btw, im using ec2 amazon server to host my teamspeak server.. and i unlock this ports to port forward my ts3 server.

https://gyazo.com/2352f334b028f582ac7900744bee34b4

 

[quickwick]

This works perfect and so does the non-emu version over on the vip section.

 

[Manager]

Hm...

Could not connect to accounting server after multiple attempts, shutting down server

The services is up (I can find it on htop), so why he can't connect it? I start first the accounting, after this, the teamspeak-instance. Seems to be correct?

 

[Manager]

ERROR | | | TS3ANetwork::Connect failed error: 110
-> The TeamSpeak Server is not able to connect to the weblist server (your server will NOT shut down because of this error)[/spoiler]

ERROR | | | TS3ANetwork::Send failed error: 111
Make sure your hosts file looks like this:

127.0.0.1 accounting.teamspeak.com
127.0.0.1 backupaccounting.teamspeak.com
127.0.0.1 ipcheck.teamspeak.com
127.0.0.1 weblist.teamspeak.com #(only if you dont want to be on the weblist)

Hm. Thats weird.

I have "TS3ANetwork::Connect failed error: 111". Have you made a typo?

Can I ignore the error message or not?

 

[qAlex26]

well i ignore it and my server shut down
so i remove
127.0.0.1 weblist.teamspeak.com
and
Online Since : 4d 14h 29m 37s
Started: 16-02-21 03:24:34
Time: 16-02-25 17:54:11

 

[Manager]

so i remove
127.0.0.1 weblist.teamspeak.com

I think, that's not a great idea...

 

[qAlex26]

why ?

 

[Bluscream]

I had a weblisted teamspeak server running > 1 year so there should not be a big problem with removing that line

 

[Manager]

why ?

That doesn't sound right.

I had a weblisted teamspeak server running > 1 year so there should not be a big problem with removing that line

Hm.

After the tutorial, but you should do it. If that does not cause problems, why that is then there?

 

[Bluscream]

idk, i did not created the tutorial

 

[Manager]

I removed the entry "127.0.0.1 weblist.teamspeak.com" and get again the error "TS3ANetwork::Connect failed error: 111".

Weird.

 

[Bluscream]

Check your firewall

 

[Manager]

All fine.

root@kuchen:~# ping -c 3 weblist.teamspeak.com
PING weblist.teamspeak.com (194.97.114.3) 56(84) bytes of data.
64 bytes from hardy.teamspeak.4players.de (194.97.114.3): icmp_seq=1 ttl=56 time=11.9 ms
64 bytes from hardy.teamspeak.4players.de (194.97.114.3): icmp_seq=2 ttl=56 time=12.0 ms
64 bytes from hardy.teamspeak.4players.de (194.97.114.3): icmp_seq=3 ttl=56 time=12.1 ms

 

[X-Ecutioner]

Today i have saw a next version TeamSpeak v3.0.12.2b
A new release in futur ? v3.0.12.2b

 

[0x0539]

Today i have saw a next version TeamSpeak v3.0.12.2b
A new release in futur ? v3.0.12.2b

Which server?

 

[X-Ecutioner]

Yes for linux server.
I have seen it on the internet today by browsing various wares forum.

A pre-realease ? a Béta ? a Fake ?

 

[0x0539]

Yes for linux server.
I have seen it on the internet today by browsing various wares forum.

A pre-realease ? a Béta ? a Fake ?

I'm also seeing v3.0.12.2b on the forums but the TS3 server itself is v3.0.12.2.

 

[X-Ecutioner]

I hast seen: p It was on the same server . Crook.
A verif in the coming days if this is true or a fake

 

[Manager]

Well, I tested it with a NPL-Server and get the same error. So it has nothing to do with it, but with a different localhost-entry.

 

[Michuupro]

thx for this cracked version