2020-04-02 12:12:09.312798|INFO |ServerMain | |Received signal SIGTERM, shutting down.
2020-04-02 12:12:09.469183|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: RESOLVE_ERROR: Host not found (non-authoritative), try again later
2020-04-02 12:12:09.469775|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: Host not found (non-authoritative), try again later
Hello,
Since saturday I have same problem with âError contacting server https://accounting2.teamspeak.com: RESOLVE_ERROR: Host not found (non-authoritative), try again laterâ. My server was running smoothly for 11 months without any problem and my license is valid till Aprill 26th. I had to reboot my whole dedicated server and afterwards this error started happening and my ts3 server is shutting down every 2 hour. All necessary ports are opened (like I mentioned server was running smoothly for past 11 months). I also checked my ip in mentioned above cloudfare thing and there are no records regarding my IP so I take it as my IP is not blocked by cloudfare. I also updated my server to latest verions.
root@server ~ # telnet accounting2.teamspeak.com 443
Trying 104.22.27.164âŚ
Connected to accounting2.teamspeak.com.
Escape character is â^]â.
Connection closed by foreign host.
root@server ~ #
looks like I can
So if in general the machine can resolve the domain and you are not blocked by Cloudflare then something on the system prevents the server from reaching the domain.
Did you double check the port forwardings? Has a IP changed or was a firewall rule updated or (could be so many things here).
Nope. Nothing was changed, ports was doouble checked. Firewall wasnât touched since setting up the TS3 server that is why I say itâs very unlikely that something on my server is causing the problem. On the other hand while looking on the forums Iâve found several more topics regarding the same issue as mine and that there was a problem on your side. So it is safe to assume while resolving the problem on your end something mightâve been messed up. I will try to contact sales department to issue new license just in case.
My ts3 server shuts down automatically every 2 hours. I contacted the company but they couldnât solve it. I have a license Can you tell me the commands I need to send via Putty for my fix?
Operating system: CentOS7
log :
2021-06-02 05:25:30.344375|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: CANCELED
2021-06-02 05:25:30.515626|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: Host not found (authoritative)
2021-06-02 05:25:30.515726|ERROR |Accounting | |Unable to connect to accounting server
2021-06-02 07:25:05.334059|ERROR |Accounting | |Could not connect to accounting server after multiple attempts, shutting down server
I hope my title is not misleading. After the day before yesterday and yesterday my server was exposed to very massive attacks, we have massively revised our firewall settings.
This morning I see the following entry in the LOG file:
2023-03-18 01:23:22.516810|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: RESOLVE_ERROR: Host not found (non-authoritative), try again later
2023-03-18 01:23:42.536748|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: Host not found (non-authoritative), try again later
2023-03-18 02:23:27.497063|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: CANCELED
2023-03-18 02:23:47.518836|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: Host not found (non-authoritative), try again later
2023-03-18 09:04:01.682958|INFO | | |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
Now my question is: is it a general problem with the accounting server (which wouldnât be the first time) or is it because of my firewall settings?
Port 2008 TCP is released and port 443 TCP has just been released. Only the TS runs on this server. Or do I not need 443 at all?
The problem still exists. Do you also have these entries in the logs since yesterday? I donât think itâs the firewall, outgoing traffic is allowed and the two ports are released for incoming traffic.
That must be local problem where your machine can not reach accounting.
There are no other reports of accounting not working or that it canât be reached.