Gracefully handle errors in `db_key_base` on the Geo primary
Customer had multiple primaries configured for Geo. Somehow one of the primary nodes had an invalid db_key_base
, which led to this error:
The Geo Node admin page just showed a flash message, "Something went wrong on our end", without more details. What was confusing was that the error message was not on the secondary, but on the primary.
This is an ugly screenshot of the backtrace: