I've run into this situation a bunch of times myself and the best way I've
found to get to the root of the issue is to turn on low level debugging
directly in the networking API's.
Shindig is using HttpClient under the covers for all of its network fetching,
and HttpClient is using the
Thanks for that Jesse. I've read and followed the first link you sent.
I successfully connected to the secure server using the sample
application SSLSocketClientWithAuth from that page and got a response
after importing the server's certificate into my cacerts keystore.
However, my gadget still
