3 ms·
Your TLS configuration is broken, in a way that often happens: You aren't serving the appropriate intermediates. It's only serving the leaf certificate, but s
by mcpherrinm 10y ago
Your TLS configuration is broken, in a way that often happens:
You aren't serving the appropriate intermediates. It's only serving the leaf certificate, but should also serve intermediates that get us to a trusted root.
Because browsers cache intermediates, this obscures the problem much of the time.
This is pretty amazing though. I copied some Go code from Gogland and got it in a browser, syntax highlighting and all! https://ctxt.io/2/AAAAwO9VEA https://ctxt.io/2/AAAAwO9VEA
- kahseng 10y agoThanks for this great feedback and TLS tip. I'm using GAE to host this, and it only has these options https://ctxt.io/2/AAAAACLGEg https://ctxt.io/2/AAAAACLGEg. Do you think this is broken or how I generated the cert? I think I followed instructions from here to get the certs: https://github.com/arkarkark/letsencrypt-nosudo https://github.com/arkarkark/letsencrypt-nosudo but I can try all this again. edit: Looks like this is the solution, thanks for pointing this problem out: http://stackoverflow.com/questions/17746643/how-to-set-the-intermediate-certificates-on-gae http://stackoverflow.com/questions/17746643/how-to-set-the-i...