In the meantime, I had to just disable SSL in ambari until this can be fixed.
Chrome likes to fail on a regular basis with net::ERR_INSECURE_RESPONSE
On a related note, Ambari does use a ton of network bandwidth (it appears it isn’t gzip’ng responses, and the PNGs are uncompressed(?), and the data is being refetched every few seconds). So I’m considering putting ambari-server behind a reverse-proxy that will compress the data. It isn’t a easy application to use if you’re on a network that’s <1mbit/sec; it seems to prefer 1-1.5mbit/sec.