Comment 8 for bug 1885585

I verified this in the staging environment and it looks like something is not working in the TLS negotiation between the mirror prober client (Twisted treq) and the affected servers and it is causing the client to error out with a `<class 'twisted.web._newclient.ResponseNeverReceived'>: [<twisted.python.failure.Failure OpenSSL.SSL.Error: [('SSL routines', 'ssl3_read_bytes', 'tlsv1 alert internal error')]>]` exception.