Accounting Server Problem

I updated that to server 3.11.0. Unfortunately there is a problem with the Accounting Service.

https://accounting2.teamspeak.com/

I get a 404 error! This shuts down my server for a short time. What’s going on there? I have Unbutu 10 as a system.

My log says:

4 Likes

Tnx. Forwarded the issue to the right department.

4 Likes

Accounting should work again.

There is one issue left with the revocation list. We are still working on this but this should not have any effect on the server.

4 Likes

Unfortunately, as you can see, the TS server then shuts down and cannot be used

1 Like

Unfortunately we don’t see that here any longer.
Yes there was a problem (hiccup) but we don’t see any errors now.

The reply in a Browser does not matter for the problem. Please ignore that one.

What could be is that you need to update your firewall rules after the update.

3 Likes

I have now edited my / etc / hosts and my / etc / networks and added accounting2.teamspeak.com

/ Etc / hosts:
104.20.74.196 accounting2.teamspeak.com

/ Etc / networks:
accounting2.teamspeak.com 104.20.74.196

He can now connect to accounting, but still has an error.

2020-01-31 15: 10: 42.281901 | INFO | ServerLibPriv | TeamSpeak 3 Server 3.11.0 (2020-01-13 08:12:37)
2020-01-31 15: 10: 42.282122 | INFO | ServerLibPriv | | SystemInformation: Linux 4.19.0-6-amd64 # 1 SMP Debian 4.19.67-2 + deb10u2 (2019-11-11) x86_64 Binary: 64bit
2020-01-31 15: 10: 42.282170 | INFO | ServerLibPriv | | Using hardware aes
2020-01-31 15: 10: 42.283384 | INFO | DatabaseQuery | | dbPlugin name: SQLite3 plugin, version 3, (c) TeamSpeak Systems GmbH
2020-01-31 15: 10: 42.283427 | INFO | DatabaseQuery | | dbPlugin version: 3.11.1
2020-01-31 15: 10: 42.283781 | INFO | DatabaseQuery | | checking database integrity (may take a while)
2020-01-31 15: 10: 42.319697 | INFO | Accounting | | Licensing information
2020-01-31 15: 10: 42.319760 | INFO | Accounting | | licensed to: XXXXXX
2020-01-31 15: 10: 42.319779 | INFO | Accounting | | type: Activation License
2020-01-31 15: 10: 42.319800 | INFO | Accounting | | starting date: Wed Oct 23 00:00:00 2019
2020-01-31 15: 10: 42.319812 | INFO | Accounting | | ending date: Fri Oct 23 00:00:00 2020
2020-01-31 15: 10: 42.319822 | INFO | Accounting | | max virtualservers: 2
2020-01-31 15: 10: 42.319831 | INFO | Accounting | | max slots: 128
2020-01-31 15: 10: 42.439518 | INFO | | | myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2020-01-31 15: 10: 43.147949 | INFO | | | Puzzle precompute time: 792
2020-01-31 15: 10: 43.148669 | INFO | FileManager | | listening on 0.0.0.0:30033, [::]: 30033
2020-01-31 15: 10: 43.161834 | INFO | Query | | listening for query on 0.0.0.0:10011, [::]: 10011
2020-01-31 15: 10: 43.162221 | INFO | Query | | listening for query ssh on 0.0.0.0:10022, [::]: 10022
2020-01-31 15: 10: 43.162436 | INFO | CIDRManager | | updated query_ip_whitelist ips: 127.0.0.1/32, :: 1/128,
2020-01-31 15: 15: 45.004318 | ERROR | | | TS3ANetwork :: Send failed error: 111
2020-01-31 15: 15: 47.004264 | ERROR | | | TS3ANetwork :: Send failed error: 111`

What I do not understand is that everything worked without errors beforehand. I checked the firewall and everything is correct. No change.

This error is now gone:

2020-01-29 11:21: 37.320212 | ERROR | Accounting | | Error contacting server https://accounting2.teamspeak.com: CANCELED
2020-01-29 11:22: 02.321692 | ERROR | Accounting | | Error contacting server https://backupaccounting2.teamspeak.com: CANCELED
2020-01-29 11:22: 02.321967 | ERROR | Accounting | | Unable to connect to accounting server

but I still have “TS3ANetwork :: Send failed error: 111”

1 Like

This error is from your system and says that the connection was refused.
You have no internet access or port is blocked or firewall rules do not count for the process.

This FAQ entry tells you needed ports and the domains you must be able to reach.

2 Likes

Meine Firewall für Teamspeak:

iptables -L:

...
Chain TEAMSPEAK (1 references)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:2008 /* Erlaube: TeamSpeak Accounting */
ACCEPT     udp  --  anywhere             anywhere             udp dpt:9987 /* Erlaube: TeamSpeak Voiceport */
ACCEPT     udp  --  anywhere             anywhere             udp dpt:9988 /* Erlaube: TeamSpeak Voiceport */
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:10011 /* Erlaube: TeamSpeak ServerQuery */
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:30033 /* Erlaube: TeamSpeak Avatar */
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:41144 /* Erlaube: TeamSpeak TSDNS */
...
1 Like

Try
1024 tcp
2008 tcp
2010 udp

2 Likes

I am in the same boat. We were having random server crashes and upon investigation, I discovered that the server was shutting down, not crashing. The logs show an accounting2.teamspeak.com error ever since January 15th, 2020. We are running Windows Server 2016 with TS Server Version 3.11.1. We were running a previous version. After I updated, the issue still remained.

2020-01-15 01:11:40.576007|INFO | | |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2020-01-15 01:11:41.435358|INFO | | |Puzzle precompute time: 1296
2020-01-15 01:11:41.439264|INFO |FileManager | |listening on 0.0.0.0:30033, [::]:30033
2020-01-15 01:11:41.483213|INFO |Query | |listening for query on 0.0.0.0:47660, [::]:47660
2020-01-15 01:11:41.483213|INFO |Query | |listening for query ssh on 0.0.0.0:10022, [::]:10022
2020-01-15 01:11:41.483213|INFO |CIDRManager | |updated query_ip_whitelist ips: 127.0.0.1/32, ::1/128,
2020-01-16 01:11:40.698246|INFO | | |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2020-01-17 01:11:40.812514|INFO | | |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2020-01-17 16:13:04.997372|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: CANCELED
2020-01-17 16:13:05.019903|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: No such host is known
2020-01-18 01:11:40.926988|INFO | | |myTeamSpeak identifier revocation list was downloaded successfully - all related features are activated
2020-01-18 16:14:25.144278|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: TIMEOUT
2020-01-18 16:14:25.178387|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: No such host is known
2020-01-18 17:14:25.075707|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: TIMEOUT
2020-01-18 17:14:25.096218|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: No such host is known
2020-01-18 18:14:25.130560|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: TIMEOUT
2020-01-18 18:14:25.150069|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: No such host is known
2020-01-18 19:14:25.096238|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: TIMEOUT
2020-01-18 19:14:25.117585|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: No such host is known
2020-01-18 20:04:19.007172|INFO |ServerLibPriv | |failed to download revocation list - count: 1

All the logs since then have shown similar if not the same errors until January 31st, 2020 we started getting this.

2020-01-31 22:57:25.173196|INFO |ServerLibPriv | |failed to download revocation list - count: 1
2020-01-31 22:57:25.179048|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: SSL_ERROR: Alert on protocol: TLS 1.2 level: fatal error: unsupported_certificate (43)
2020-01-31 22:57:25.199600|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: No such host is known
2020-01-31 22:57:25.199600|ERROR |Accounting | |Unable to connect to accounting server
2020-01-31 22:57:26.147843|INFO |ServerLibPriv | |failed to download revocation list - count: 1
2020-01-31 22:57:26.215237|INFO | | |Puzzle precompute time: 1058
2020-01-31 22:57:26.220073|INFO |FileManager | |listening on 0.0.0.0:30033, [::]:30033
2020-01-31 22:57:26.295273|INFO |Query | |listening for query on 0.0.0.0:47660, [::]:47660
2020-01-31 22:57:26.296235|INFO |Query | |listening for query ssh on 0.0.0.0:10022, [::]:10022
2020-01-31 22:57:26.300137|INFO |CIDRManager | |updated query_ip_whitelist ips: 127.0.0.1/32, ::1/128,
2020-02-01 00:00:25.122971|INFO |VirtualSvrMgr | |executing monthly interval
2020-02-01 00:00:25.140585|INFO |VirtualSvrMgr | |reset virtualserver traffic statistics
2020-02-01 00:57:25.133982|ERROR |Accounting | |Could not connect to accounting server after multiple attempts, shutting down server

The server has shut down over 20 times since then, however the last few have changed to this.

2020-02-01 10:02:19.237297|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: TIMEOUT
2020-02-01 10:02:19.319322|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: No such host is known
2020-02-01 10:02:19.319322|ERROR |Accounting | |Unable to connect to accounting server
2020-02-01 10:05:34.271465|INFO |ServerLibPriv | |failed to download revocation list - count: 1
2020-02-01 10:05:34.271465|INFO |ServerLibPriv | |failed to download revocation list - count: 1

And here is more of the shutdowns.

2020-02-01 06:32:26.299573|ERROR |Accounting | |Error contacting server https://accounting2.teamspeak.com: TIMEOUT
2020-02-01 06:32:26.299573|INFO |ServerLibPriv | |failed to download revocation list - count: 1
2020-02-01 06:32:26.320077|ERROR |Accounting | |Error contacting server https://backupaccounting2.teamspeak.com: RESOLVE_ERROR: No such host is known
2020-02-01 06:32:26.320077|ERROR |Accounting | |Unable to connect to accounting server
2020-02-01 06:32:26.325973|INFO |ServerLibPriv | |failed to download revocation list - count: 1
2020-02-01 08:31:42.720498|ERROR |Accounting | |Could not connect to accounting server after multiple attempts, shutting down server

2 Likes

Is there a solution for that? Funny that it only came after the update. But of course it is the user and his server who are to blame.

Is the timeout still an issue?

In the past, regarding to the old forum, there are only 2 cases if this happens.

(1) The service TeamSpeak provides is down (for real) and the backup.teamspeak.com what appears to be a failover doesn’t work either.

(2) Due to many attempts your IP address got blocked for a specific time.

2 Likes

Hello, everybody,
since i updated to the new ts3 version last week, the server loses connection several times a day.

It’s still an issue for me, as it’s been happening on and off since Friday, since I got version 3.11.0.
the failure is always around 11-13pm and 00-2am for about 5-10 minutes. Therefore I do not assume that my IP will be banned.

I finally had a chance to follow up with you and test. The url is still timing out. Upon loading the url I get a 404 error. The backup url isn’t found on any devices across multiple networks. I also tried downgrading back to 3.9.1 on the same machine (with original files backed up) with no success. A copy as well as a backup copy of the Teamspeak server on a completely different system seems to be working with no problems. Checking the logs show the list downloaded successfully on 3.9.1. It doesn’t make any sense.

The site is not supposed the be opened in your webbrowser.
I guess it requires a specific user-agent to access it.

https://accounting2.teamspeak.com: TIMEOUT

Like I’ve already said the TIMEOUT has 2 reasons:

(1) The accounting system is down (for real) which would mean I couldn’t (re)start my server, too.
(2) Your IP, range or region is currently blocked (by Cloudflare I assume) and you need to wait a while until you can deal with another try again.

That’s what I’ve noticed in the past to now could happen if this error occurs.

Maybe @TS.ChrisR has more details about the current status of the accounting service.

2 Likes

I didn’t even think about Cloudflare. It appears cloudlfare is blocking the ip of the webserver for some reason. I have the UK excluded. I’m going to try excluding the specific IP and see what happens.

Well nice to hear you could figure it out.

I guess you’re not alone with this issue.
A lot of reports has been made the last days with similar descriptions. :open_mouth:

I’ve given it time to propagate across the servers and the issue still exists. The server has not been running either. We have the server on a temporary server that is not having any issues, which is really odd to me. I’ve started the server and connected to it and I am still getting the same errors. It doesn’t make any sense to me.

2 Likes
twitch instagram twitter facebook