Hacker News Reader

No it's not: your hostname is wrong, and your cert is self-signed.

Check https://www.wormly.com/test_ssl/h/www.fluxflex.com/i/64.27.5...

It seems that root of the domain fluxflex.com is redirected to www.fluxflex.com, and fluxflex uses zerigo DNS Redirect to do it. That's the problem.

For avoiding the error, please access to www.fluxflex.com, not fluxflex.com. We'll fix this issue soon.

The link I posted goes to www.fluxflex.com, not fluxflex.com

Both are broken in the same way.

Hmm, it seems weird. We just use zerigo.net as our external DNS nameservers, and it has some relations with this current issue.

I should investigate the problem deeper.

So it looks like the problem was that you updated your DNS but forgot about TTLs. Your new cert has the correct name on it, but you didn't setup the cert chain properly (SSLCACertificateFile under Apache)

https://www.wormly.com/test_ssl/h/50.16.245.9/i/50.16.245.9/...

You are right. We changed our frontend from Django+Apache to Rails+Nginx, and we forgot to specify the certificate chain in nginx config file. Now I added the description, and confirmed that we can access to the web site via SSL.

Reply on news.ycombinator.com