A deployment that cannot be reached says why on its tile: an expired, not yet valid or mismatched security certificate, a server error, a server that does not answer or cannot be found, or a server that answers Connect but not its window. Click the tile to check again
The tile of a deployment that cannot be reached shows the reason in words instead of the "check your network and/or VPN" picture
Connect refuses to launch a deployment whose server certificate has expired, is not valid yet or is for another name, and shows the reason, instead of opening tiCrypt with a server it cannot use
A deployment's tile does not launch while Connect is still checking whether its server can be reached, as the Launch button of a single deployment already did not
An update repository whose security certificate has expired shows the day it expired instead of Go's error text, and a refused connection on Windows is reported as refused
Deployment tiles are highlighted under the pointer again and turn red in delete mode, as before 4.1.3
Security updates to the libraries Connect is built with (gRPC, Echo, golang-jwt, Go's crypto packages, Angular and its tools)
