What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Watchover Tyrant Status cant connect

S

swanloves

New Member
Joined
May 29, 2016
Messages
4
Reaction score
0
Hey wehn i try to use the ESP i get the message

Watchover Tyran Status: Unable to establish a connection to our server via TCP

i m trying to connect to Europe TCP on or not
 
Don't use tcp just load it as it is Europe or Asia just don't tick tcp. That was my problem it wouldn't load with tcp only when it was unticked it would work.
 
i was using it without problem yesterday, and if i tick off the tcp, the internet connection will be turned off as well
 
Did you try the shortcut? the tyrant with numbers and letters ex: Bd6421.exe not the one that says watchover tyrant.exe
I think it's an.exe
 
I did, everything works completely fine past few days, but it won't work today. this is strange
 
i tryd the 2 clients which is in my folder non is working only asia without TCP but only for 3-5Mins
 
Yeah, it's only working with asia for now, but with Asia, the radar don't work..

(The radar worked earlier with Europe, but now Europe makes "Unable to establish a connection to our server via TCP" message)
 
Huh Yea that is strange, i can't test it because I'm at work but what I explained is how it worked for me the past few days but not today, but I tried, I'm sure Tony will get you squared away when he gets on.
 
Asian Server will work briefly for European users I found. After 10 minutes it will disconnect you.
 
The binaries you launch shouldn't obviously be an issue since it was last working yesterday. Analysis of all of our clients show the following.

We connect to 2 ports when launching, 1 being 23589 which never changes and a random port it seems to be, or from a list of ports it seems to rely on... after doing analysis 5 times the ports seem to be dynamically changing each time. Also the server we all connect to is ns3041384.ip-164-132-201.eu | 164.132.201.124 which is up and running so this is not a connectivity issue with the server. Does NA have it's own designated server? based on the servers domain name it seems universal so i don't think that can be it. Mabe it's either's NA's pipe or the pipe the server is hosted in that's experiencing the issue. Mabe reboot the server, i'm pretty sure that server is hosted in a VPS Linux. Anyways just helping out with suggestions.

Another idea to think about: maybe there's too many connections established to the server, mabe it's reached it's max capacity and it crashed, which then the server should get a reboot.
 
Last edited:
You must log in or register to reply here.
Back
Top