Skip to main content

Fixing a "Bad Decrypt" error

A "Bad Decrypt" error usually appears after moving Informer between servers. Informer hashes local passwords (for a Datasource, Domain, mail server, local User, and so on) with the tokenSecret in its config.json. If the new server's tokenSecret does not match the one that encrypted the passwords, Informer cannot decrypt them and raises the error.

This does not affect Active Directory, LDAP, or SAML Domain credentials, which are not stored this way.

There are two ways to fix it.

Match the tokenSecret​

  1. Open config.json on the original server and note its tokenSecret.
  2. Open config.json on the new server.
  3. Set the new server's tokenSecret to match the original.
  4. Save the file and restart Informer.

Rehash the passwords​

If you cannot access config.json, re-enter each password on the new server instead. Log in, open each object that has a password, re-enter the password, and save. Informer rehashes it with the new server's tokenSecret. Repeat for every object with a stored password.