David,

Thanks for the explanation. I thought this was deep in the plumbing, and it was -- that was some impressive detective work on your part!

For what it's worth, the domain name is only a convenience that allows us to give you an HTTPS connection that works right from the start. If you point your browser to https://IP-ADDRESS/, the instance will certainly behave, but you'll have to tell your browser not to worry about the fact that there's no SSL certificate set up for the IP address.

We did find that we were running up against a quota for serving the certificates. Having changed that, you shouldn't have any trouble with this in the future. Of course, please do let us know if you run into problems.

Preparing a VM for you to use locally has proven more troublesome than I had expected.  Is this something you need in fairly short order, or can it wait a few weeks until our next release?

Christian