Packet.net DNS/SAN issues?

[Cael Jacobs]

Hi, all!

I am attempting to use jClouds to interact with Packet.Net, and when I 
make a call to

   packetApi.operatingSystemApi().list();

I get a stack trace for a thrown exception:

   java.security.cert.CertificateException: No subject alternative DNS
   name matching api.packet.net found. connecting to GET
   https://api.packet.net/operating-systems HTTP/1.1

I pulled the cert for api.packet.net, which appears to be a PaaS or IaaS 
node that is serving dozens of domains, and a Subject Alternative Name 
for "api.packet.net" does exist in there along with many others.

I am able to access the same url via curl, from the same machine and 
others, and get proper responses, so I know that there's not an 
intrinsic error between me and the api server that's preventing me from 
reaching it; it seems to me that either jClouds is doing something 
squirrelly, or the underlying Java SSL class is not handling the 
certificate SANs properly.

Has anyone seen anything like this on packet.net or any other provider?

Thanks,

-Cael