Hey,
the issue is identifiable from your config. A few things to address:
Root Cause: TSSERVER_QUERY_HTTP_IP=<localaddress>
You’re binding the HTTP query interface to your Raspberry Pi’s LAN IP (e.g. 192.168.x.x). A Docker container doesn’t recognize the host’s LAN IP as one of its own network interfaces — so the TS server either doesn’t bind correctly, or the port mapping doesn’t work as expected.
Fix 1 — Bind to all interfaces
Change this line in your compose file:
- TSSERVER_QUERY_HTTP_IP=0.0.0.0
This tells the TS server to listen on all interfaces inside the container, which is required for Docker port mapping 10080:10080 to work properly.
Fix 2 — Container-to-container communication
If ts6-manager is also running as a Docker container (in the same Compose file or network), do not use the Pi’s LAN IP as the host in the ts6-manager settings. Use the service name instead:
Host: teamspeak Port: 10080
Docker has built-in DNS resolution for service names within the same network. The LAN IP only works reliably if you’re using network_mode: host.
Regarding the SSH error (wrong version number)
ssl3_get_record:wrong version number
This error occurred when you switched to the SSH connection type in ts6-manager. It suggests a protocol mismatch — ts6-manager may be attempting a TLS-wrapped connection to the SSH query port (10022), which the TS server doesn’t expect. The exact internal behavior of ts6-manager’s SSH connection handling isn’t fully clear to me, so I’d recommend getting the HTTP connection working first (after applying the fixes above) before troubleshooting the SSH path further.
b]Summary[/b]
ECONNREFUSED :10080
Set TSSERVER_QUERY_HTTP_IP=0.0.0.0
Manager can’t reach TS server
Use service name teamspeak instead of LAN IP
SSL wrong version number
Likely protocol mismatch — get HTTP working first
Hope that helps — let us know if the issue persists after these changes.