#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)%E2%80%9D 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)%E2%80%9D 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-ht...