I’ve been banging my head against the following for a while:
All my workflows have been deactivated and I cannot activate any of them. Every time I get this error message:
Workflow could not be activated:
There was a problem activating the workflow: “crypto is not defined”
I checked all my credentials, googled for it and searched for it here in the forum. But I found no solution. My best bet is that I need an n8n activation key. But I run the community edition self-hosted and it says under Settings > Usage and plan that I have unlimited active workflows. Does anybody have an idea?
I have this problem too since my upgrade to 1.47.1.
I’m running it in a standard docker config with a postgres database.
The upgrade was made with npm inside the docker container.
Created a PR to handle older (and unsupported) versions of node.js 18.
We’ll try to get a patch release out later today.
But even after this fix is available, please upgrade node.js to the latest 18.x/20.x as a good security practice. These would include some major security fixes from February.
Hi guys, I now have 1.47.2 installed via Cloudron. Restarted n8n multiple times as well. But I still get an error message and cannot activate any workflow. It says
Workflow could not be activated:
There was a problem activating the workflow: “Your request is invalid or could not be processed by the service”
I’m sorry to bug you guys, but unfortunately I still have the same problem. See error message in my post above. Does it tell you anything?
Am on 1.48.3 now.
Still not working on my end. I’m now running Cloudron in v8.0.0 and n8n in v1.48.3. Also tried in another browser and restarted everything multiple times.
This error message persists for every workflow:
Workflow could not be activated: There was a problem activating the workflow: “Your request is invalid or could not be processed by the service”
While that is a concerning error, it doesn’t sound like the error this thread was meant for
Maybe we should start a new post, and share more details there. Trying to keep this conversation in this thread gives us the impression that the crypto is not defined error is still happening, which I don’t think it is.
Can you please start a new thread, and also please include the workflow, or enough info about what trigger/webhook nodes that workflow has