Its a known issue that updating the firewall bouncer creates an extra key so that is us most likely

Weird. As with the instance ID, the firewallbouncer with the newest ID is the unknown one…

Yes, cause inside the postinstall script it replaces `` with the key but if you already have a key that string isn't in the config anymore

Oops. That doesn't sound very practical… 🙈