FreeTakServer: 1.9.1: SSL connection breaks after short time
Not sure if that’s a bug or if I’m missing anything… I can’t seem to get SSL to work. I have built the docker image from the current FreeTakServer-Docker main branch on an x86_64 server and it’s running fine. tcp connectivity is fine too. I’m using an Android 8.1.0 phone and an Android 10 tablet for testing. Both have ATAK 4.3.1 installed. I created users in the WebUI and tried to deploy the datapackages. That was the first problem - the certificates don’t seem to get installed in ATAK. At least they don’t show up in /atak/certs. Additionally, the data package prefs refer to the internal docker network IP of the server, not to the external IP (which is set correctly throught the IP envvar) (see https://github.com/FreeTAKTeam/FreeTAKServer-Docker/issues/26). I pulled the certificates out of the ZIP files and uploaded them to the EUDs manually. Then I imported the certificates on the EUDs manually through the server settings. Which seems to work - at least I don’t get an error. The EUDs try to connect and I immediately get “IOerror - reconnecting”. When I additionally enter authentication credentials, the EUDs connect, apparently stay connected for like 20-30secs and then disconnect. Same error message on the EUDs. On the server I found the following logs…:
FTS_debug.log (repeating over and over)
INFO : 2021-07-31 17:35:18,456 : DataPackageServer.py:144 : sending client version json
INFO : 2021-07-31 17:35:18,457 : DataPackageServer.py:150 : sending client version info
FTS_error.log (repeating over and over)
ERROR : 2021-07-31 16:22:04,519 : ClientReceptionHandler.py:72 : Exception other than broken pipe in monitor for data function [Errno 11] Resource temporarily unavailable
Another thing I noticed are updated timestamps on the server certificates in the persistent storage after a container restart. Does the container recreate the server certificates after a restart or recreate without checking for exixting certificates?
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 23
I tried rollback to 1.9 but I’m getting the same issue. I’m looking at the moment into temporary deploying taky until this is fixed…