Hi people, I have another request, I know it doesn't belong here in the forum, but I'll try it anyway.
I installed Ts3 server via container but unfortunately it loses the connection after a short time. I suspect it also has something to do with an IP. Does anyone know anything about this?
2024-02-05 14:26:48.673368|INFO |ServerLibPriv | |TeamSpeak 3 Server 3.13.7 (2022-06-20 12:21:53)
2024-02-05 14:26:48.676717|INFO |ServerLibPriv | |SystemInformation: Linux 6.1.0-rpi7-rpi-2712 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) x86_64 Binary: 64bit
2024-02-05 14:26:48.676937|INFO |ServerLibPriv | |Using hardware aes
2024-02-05 14:26:48.739401|INFO |DatabaseQuery | |dbPlugin name: SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH
2024-02-05 14:26:48.739871|INFO |DatabaseQuery | |dbPlugin version: 3.11.1
2024-02-05 14:26:48.753333|INFO |DatabaseQuery | |checking database integrity (may take a while)
2024-02-05 14:26:48.997861|WARNING |Accounting | |Unable to open licensekey.dat, falling back to limited functionality
2024-02-05 14:26:49.003455|INFO |Accounting | |Licensing Information
2024-02-05 14:26:49.003783|INFO |Accounting | |licensed to : Anonymous
2024-02-05 14:26:49.003993|INFO |Accounting | |type : No License
2024-02-05 14:26:49.004316|INFO |Accounting | |starting date : Tue Feb 1 00:00:00 2022
2024-02-05 14:26:49.004482|INFO |Accounting | |ending date : Thu Jul 1 00:00:00 2027
2024-02-05 14:26:49.004668|INFO |Accounting | |max virtualservers: 1
2024-02-05 14:26:49.004810|INFO |Accounting | |max slots : 32
2024-02-05 14:26:50.929846|INFO | | |Puzzle precompute time: 1843
2024-02-05 14:26:50.933915|INFO |FileManager | |listening on 0.0.0.0:30033, [::]:30033
2024-02-05 14:27:01.072827|INFO |Query | |Using a query thread pool size of 2
2024-02-05 14:27:01.162654|INFO |ServerLibPriv | |failed to download revocation list - count: 1
2024-02-05 14:27:01.299518|INFO |Query | |listening for query on 0.0.0.0:10011, [::]:10011
2024-02-05 14:27:01.306262|INFO |Query | |listening for ssh query on 0.0.0.0:10022, [::]:10022
2024-02-05 14:27:01.307061|INFO |Query | |listening for http query on 0.0.0.0:10080, [::]:10080
2024-02-05 14:27:01.309424|INFO |CIDRManager | |updated query_ip_allowlist ips: 127.0.0.1/32,
2024-02-05 14:37:21.205037|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:37:41.226729|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:38:01.246595|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:38:21.262653|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:38:41.278692|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:39:01.299448|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:39:21.318683|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:39:41.340808|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:40:01.362823|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:40:21.382846|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:40:41.404824|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:41:01.426633|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:41:21.448710|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:41:41.470945|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:42:01.485290|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:42:21.506719|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:42:41.522687|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:43:01.540443|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:43:21.560017|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:43:41.576001|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:44:01.597998|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:44:21.619846|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:44:41.640391|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:45:01.662644|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:45:21.684310|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:45:41.706420|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:46:01.723056|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:46:21.741736|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:46:41.764019|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:47:01.786249|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:47:21.805984|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:47:41.826704|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:48:01.847141|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:48:21.868786|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:48:41.890735|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:49:01.907860|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:49:21.928894|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:49:41.950353|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:50:01.971729|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:50:21.993141|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:50:42.014596|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:51:02.030630|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:51:22.046705|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:51:42.058716|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:52:02.074636|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:52:22.091953|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:52:42.114023|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:53:02.135719|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:53:22.156551|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:53:42.178023|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:54:02.197702|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:54:22.218954|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:54:42.240185|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:55:02.261509|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:55:22.282883|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:55:42.304069|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:56:02.325233|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:56:22.346498|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:56:42.367971|ERROR | | |TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0
2024-02-05 14:57:12.399232|ERROR | | |TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
2024-02-05 14:57:52.425240|ERROR | | |TS3ANetwork::ResolveHostName failed error: -3 (Temporary failure in name resolution) 11
pi@solaranzeige:~ $ ping google.com
PING google.com(fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e)) 56 data bytes
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=1 ttl=58 time=9.52 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=2 ttl=58 time=8.69 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=3 ttl=58 time=8.84 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=4 ttl=58 time=8.86 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=5 ttl=58 time=8.72 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=6 ttl=58 time=8.99 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=7 ttl=58 time=8.81 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=8 ttl=58 time=8.81 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=9 ttl=58 time=8.86 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=10 ttl=58 time=8.81 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=11 ttl=58 time=8.42 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=12 ttl=58 time=8.30 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=13 ttl=58 time=8.67 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=14 ttl=58 time=8.69 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=15 ttl=58 time=8.56 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=16 ttl=58 time=8.90 ms
64 bytes from fra24s06-in-x0e.1e100.net (2a00:1450:4001:829::200e): icmp_seq=17 ttl=58 time=8.55 ms
^C
--- google.com ping statistics ---
17 packets transmitted, 17 received, 0% packet loss, time 16117ms
rtt min/avg/max/mdev = 8.297/8.764/9.522/0.256 ms
pi@solaranzeige:~ $ ping google.com
ping: google.com: Temporärer Fehler bei der Namensauflösung
pi@solaranzeige:~ $
And what I noticed is that when I restart the Pi, Google Ping stops working after about 5 minutes