Why is server FIN'ing after starting TLS session?
Solution 1:
Its probably due to an SNI issue with either the client or some device in the middle, like a load balancer. The load balancing device must be able to present the server name to the backend host as part of the initial Client Hello. see https://en.m.wikipedia.org/wiki/Server_Name_Indication
Solution 2:
The most important packet is the "Encrypted Alert" as it contains the reason why the connection is closed.
It seems to be a validation error. This means that the certificate is not trusted, or invalid. But the real reason is send via the TLS Alert protocol