docker run --name n8n-queue -p 5679:5678 docker.n8n.io/n8nio/n8n worker
No encryption key found - Auto-generated and saved to: /home/node/.n8n/config
Error: Missing encryption key. Worker started without the required
N8N_ENCRYPTION_KEY env var. More information: n8n Hosting Documentation and Guides | n8n Docs
environment-variables/configuration-methods/#encryption-key
I hope you’re all doing well. I’m writing this post to seek assistance with an issue I’m facing regarding the execution queue in n8n.
My goal is to run a set of 10 executions sequentially, one after another, rather than in parallel. To achieve this, I have followed the instructions in the n8n documentation and made the necessary configurations. Here’s what I have done so far:
Enabled Redis as the queue system.
Set the following environment variables inside the environment variable file:
Despite these configurations, the executions are still running in parallel rather than sequentially. As a result, I am encountering unexpected behavior in my workflows.
To find a solution, I referred to the official n8n documentation. I came across a suggested solution that involves running the following Docker command:
However, when I tried this solution, I encountered the following error message:
No encryption key found - Auto-generated and saved to: /home/node/.n8n/config
Error: Missing encryption key. Worker started without the required N8N_ENCRYPTION_KEY env var.
More information: Encryption Key Documentation
To provide you with more information, here are my system specifications:
* n8n version: Latest
* Database: Postgre
* n8n EXECUTIONS_PROCESS setting: I believe it is set to "main"
* Running n8n via: Docker
* Operating system: Ubuntu
I kindly request the assistance of the n8n community in resolving this issue. If you have encountered a similar problem or have any insights or suggestions, please share them with me. I greatly appreciate any help or guidance you can provide.
Thank you all for your time and support.
Have you looked at the documentation?
It should be pretty clear when reading this error and the documentation what you are missing
Ill give you a hint, it ends with encryption key.