gene1wood
commented
11 years ago This would have been caused by the hash of the new gmail public key not being present in our allowed hashes monitoring list. It's been added.
Closed jrgm closed 11 years ago
gene1wood
commented
11 years ago This would have been caused by the hash of the new gmail public key not being present in our allowed hashes monitoring list. It's been added.
That's the bridge-gmail solo instance:
"i-70ad8145": { "Name": "identity-dev-stage-bridge-gmail-0621", "private_ip_address": "10.148.25.187" }