This might be the same issue as in TOOLS-3122.

See https://spruce.mongodb.com/task/mongo_tools_debian10_native_cert_ssl_4.4_9f5380c0d78ba4e88ec24b6b5f8791db589d6929_22_05_03_20_13_50/tests?execution=0&sortBy=STATUS&sortDir=ASC for an example

This seems to have started after TOOLS-3049 was merged, but it's not clear whether this is because of the upgrade to Go 1.17 from that change, or if this is some other problem that simply manifested around the same time.

The easiest potential fix may be to simply generate a new certificate with the same properties as the current one. Specifically, we need to make sure that the cert has the right Subject Alternative Name (SAN) fields for the localhost host and 127.0.0.1 IP.