The SSL certificate is fine; the site just redirects from https to http for whatever reason, so you end up with no certificate at all. There's no SSL issue for Chrome to report about.

    $ curl -v https://pigshell.com 2>&1 | grep Location
    < Location: http://pigshell.com

I think it was the fact that by default Chrome hides the protocol from the url, so I could'nt see at a glance it was downgraded. This is exactly what I was talking about when mentioning chrome removing this stuff was hindering troubleshooting. Once I found the setting in chrome to always show the http section, it became clear what was happening.