Crawl fails with invalid SSL certificate on different domain name

[cromination]

In pointing this to a server that has a different virtual host name and is forcing https the crawl fails. Is there a way to have it ignore ssl errors?

An example is I'm using a 3 tired managed hosting platform, with a dev/test/prod setup. On the prod tier I have a valid FQDN of https://www.site.com with .htaccess forcing https and a valid SSL certificate on a load balancer in front of that environment.

On the test server I have the hosting platform's domain name:
https://test.hostingplatformname.com/

There is no SSL on their load balancer and its giving me an SSL error.

I was looking into settings some flags for phantom.js like this:

--ignore-ssl-errors=true
--ssl-protocol=any

But they don't seem to work.

I've also tried this flag in the a11y machine:

--http-tls-disable

But this didn't work either. Am I doing this right? Or is it not possible here?

Thanks!