[ET Trac] #2536: Certificate for https://cactuscode.org is not trusted

[Steven R. Brandt]

#2536: Certificate for https://cactuscode.org is not trusted

 Reporter: Erik Schnetter
   Status: open
Milestone: 
  Version: development version
     Type: bug
 Priority: major
Component: Cactus website

Comment (by Steven R. Brandt):

Weird. Chrome says, “certificate valid.” If I call “openssl s\_client -servername [cactuscode.org](http://cactuscode.org) -showcerts -connect [cactuscode.org:443](http://cactuscode.org:443)” I don’t see a certificate. If I do “openssl s\_client -servername [cactuscode.org](http://cactuscode.org) -showcerts -connect www.[cactuscode.org:443](http://cactuscode.org:443)” I see a github cert \(since the site is now on github\). Nowhere, though, do I see an [lsu.edu](http://lsu.edu) cert. Could that be cached on your machine, Erik?

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2536/certificate-for-https-cactuscodeorg-is-not
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.einsteintoolkit.org/pipermail/trac/attachments/20210602/01276b37/attachment.html