Dear fellows, please help to identify the OTC auth issue with active working instance when OTC code and Recovery code not accepted while the password is correct
I found some answers but is seems not my case
Before I implemented 2FA Google Authenticator OTC for my account - everything work smoothly.
env keys N8N_MFA_ENABLED=false will not work for me
The only thing i’ve done after simple email:pass were stable is docker volume prune docker image prune -a
The error looks like there is an issue with decrypting the credentials. Is your n8n volume has been changed? Or the encryption key has been entered incorrectly?
I’m not sure, how it can be changed - if the system properly working and actively serving API requests and all the nodes are working properly.
Or the encryption key has been entered incorrectly?
What I have to say - the section N8N_ENCRYPTION_KEY={{mysecret}}
I created manually after I was denied accessing the dashboard and found this (following next log):
1st line whowing there is encryption key found
last two lines - just the same denied reties with OTC Autneticator
2024-03-25T19:15:21.261643463Z No encryption key found - Auto-generated and saved to: /home/node/.n8n/config
2024-03-25T19:15:22.633288339Z Initializing n8n process
2024-03-25T19:15:22.972029514Z n8n ready on 0.0.0.0, port 5678
2024-03-25T19:15:23.457309390Z n8n detected that some packages are missing. For more information, visit https://docs.n8n.io/integrations/community-nodes/troubleshooting/
2024-03-25T19:15:23.457531257Z Attempting to reinstall missing packages
2024-03-25T19:15:49.660282022Z Packages reinstalled successfully. Resuming regular initialization.
2024-03-25T19:15:50.690386616Z Version: 1.31.1
2024-03-25T19:15:50.707840972Z ================================
2024-03-25T19:15:50.708149770Z Start Active Workflows:
2024-03-25T19:15:50.708189795Z ================================
2024-03-25T19:15:50.708712766Z - "Z-C-A" (ID: Q7***********3II)
2024-03-25T19:15:50.756861466Z => Started
2024-03-25T19:15:50.757197145Z - "Z-P-B" (ID: d9u**********5FH)
2024-03-25T19:15:50.761121560Z => Started
2024-03-25T19:15:50.773368266Z
2024-03-25T19:15:50.773409674Z Editor is now accessible via:
2024-03-25T19:15:50.773417168Z https://pupsub.myhost.com:5678/
2024-03-25T19:17:04.218414533Z Error: error:1C800064:Provider routines::bad decrypt
2024-03-25T19:17:05.579107870Z Error: error:1C800064:Provider routines::bad decrypt
The only issue — is Authentication.
As you may see - nodes acting properly.
And my email:pass is also valid.
I didn’t added it initially, but I remember I tried to play with that vars, to change.
Because I found somewhere so it may help.
But the issue caused before I made my first move with change of TZ (I hope I right saying this).
What I do now - will try to guess which TZ it was before I made it such +4
Can you say please, what the initial state of TZ KEY:VALUE ?
May be it was empty or was not ?
In that case, the only other possibility is that N8N_ENCRYPTION_KEY was changed at some point.
The fact that the logs keep saying No encryption key found - Auto-generated and saved, I think somehow the env variable is not getting set on the container, and the container is using a new random key at every startup.
Do you not have a volume configured to mount to /home/node/.n8n ?
Thanks for pointing out this.
I generated own N8N_ENCRYPTION_KEY={{mysecret}} as mentioned above, because I cant understand how to read that one which is generated on the server… To keep it stored.
nope, I have this
— how to do that, you mentioned, and what it is doing?
