Error while connecting to email account Notifications

[willspenc]

Good day all

Trust you are having a great weekend

I have just completed an exercise of migrating my V12 server to V13. My end-goal is to
migrate 4 servers on a multi-tenant system but for now I am checking my procedures on
a single domain server.

The thread that I posted is -

Upgrading from V12 to V13

Hi @smino Your list is the same as mine with these exceptions- node 14.19.1 mariadb 10.6.7 pip 20.0.2 So far all is well …except 62 of the same error in the error-log. Error while connecting to email account Notifications cryptography.exceptions.InvalidSignature: Signature did not match digest. cryptography.fernet.InvalidToken frappe.exceptions.ValidationError: Encryption key is invalid, Please check site_config.json I did not paste the entire trace-back. This is in line with the link …

The procedure involved the following -

Existing server : V12.29

1. make backups on V12 server : sql-database + csv exports
2. Create fresh V13 server
3. Copy database.sql.gz file to new server with winscp
4. Unzip gz file to yield sql-file
5. Do restore
6. do migration
7. No errors reported

( detail of commands in thread listed above)

Logged in to server. No problems. All data seem to be there. Can create new data e.g. item.

At some stage I saw a pop-up about unread error messages and when I looked in the
error log list I saw 62 errors of the same kind-

Error while connecting to email account Notifications

Trace-back further down in this post.

I did see a post before I did the database transfer and hence I made a backup of the
site_config.json file. The post that I saw is -

frappe.exceptions.ValidationError: Encryption key is invalid, Please check site_config.json

For us this was a sort of hidden requirement we didn’t even know the existence of the encryption keys in site_config.json and its dependency had we known that we would have certainly factored that into our solution. When a product says it has a backup solution and a restoral methodology one generally believes that the makers of the software know what they need and include everything necessary for a working restoral but in this case that was not true. We found a work around and hope it saves oth…

My observaions-

Fresh V13 site_config.json file did not have an encryption key.
Unfortunately I did not check the state of the json file directly of the migration.
I deleted the “notifications” email and its domain and recreated them.
The json file on the new V13 server now has an encryption key.
No more errors.

My question;
I read suggestions about transfering the encryption key. Do I still need to do that since the
error does not occur anyore ? Is this key only used for emails? It seems to have been
created when I re-created the email account and domain. It sees as if the problem
is solved … or am I missing something?

If someone can clarify this I would really appreciate it. After “practicing” my procedure on
a single domain system I need to push on and migrate my multi-tenant system.

Thank you all for reading such a long post !

Trace back

Traceback (most recent call last):
File “env/lib/python3.8/site-packages/cryptography/fernet.py”, line 119, in _verify_signature
h.verify(data[-32:])
File “env/lib/python3.8/site-packages/cryptography/hazmat/primitives/hmac.py”, line 74, in verify
ctx.verify(signature)
File “env/lib/python3.8/site-packages/cryptography/hazmat/backends/openssl/hmac.py”, line 75, in verify
raise InvalidSignature(“Signature did not match digest.”)
cryptography.exceptions.InvalidSignature: Signature did not match digest.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “apps/frappe/frappe/utils/password.py”, line 212, in decrypt
plain_text = cstr(cipher_suite.decrypt(encode(pwd)))
File “env/lib/python3.8/site-packages/cryptography/fernet.py”, line 80, in decrypt
return self._decrypt_data(data, timestamp, time_info)
File “env/lib/python3.8/site-packages/cryptography/fernet.py”, line 137, in _decrypt_data
self._verify_signature(data)
File “env/lib/python3.8/site-packages/cryptography/fernet.py”, line 121, in _verify_signature
raise InvalidToken
cryptography.fernet.InvalidToken

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “apps/frappe/frappe/email/doctype/email_account/email_account.py”, line 308, in receive
email_server = self.get_incoming_server(in_receive=True, email_sync_rule=email_sync_rule)
File “apps/frappe/frappe/email/doctype/email_account/email_account.py”, line 188, in get_incoming_server
args.password = self.get_password()
File “apps/frappe/frappe/model/base_document.py”, line 859, in get_password
return get_decrypted_password(self.doctype, self.name, fieldname, raise_exception=raise_exception)
File “apps/frappe/frappe/utils/password.py”, line 59, in get_decrypted_password
return decrypt(result[0][0])
File “apps/frappe/frappe/utils/password.py”, line 216, in decrypt
frappe.throw(_(‘Encryption key is invalid, Please check site_config.json’))
File “apps/frappe/frappe/init.py”, line 444, in throw
msgprint(msg, raise_exception=exc, title=title, indicator=‘red’, is_minimizable=is_minimizable, wide=wide, as_list=as_list)
File “apps/frappe/frappe/init.py”, line 423, in msgprint
_raise_exception()
File “apps/frappe/frappe/init.py”, line 378, in _raise_exception
raise raise_exception(msg)
frappe.exceptions.ValidationError: Encryption key is invalid, Please check site_config.json