Error prompts with "window.crypto.randomUUID is not a function" after I updated the version to 1.120.3

Questions
1

Describe the problem/error/question

Error prompts w/ “window.crypto.randomUUID is not a function” when I added any nodes after I update the n8n version from 1.110 to 1.120.3

What is the error message (if any)?

“window.crypto.randomUUID is not a function” when I added any nodes

Please share your workflow

Share the output returned by the last node

[
{
“id”: “atini7sdm3ny7y9dh18m9crjjw”,
“create_at”: 1763026518382,
“update_at”: 1763026518382,
“edit_at”: 0,
“delete_at”: 0,
“is_pinned”: false,
“user_id”: “3run47epxpgjpgawp9zdhg1inc”,
“channel_id”: “8ydoo7iudbbgxj5kg98q4ybmwh”,
“root_id”: “fwztw8sy5bdcde7fqwbip86zio”,
“original_id”: “”,
“message”: “xxomitxxxx”,
“type”: “”,
“props”: {
“from_bot”: “true”
},
“hashtags”: “”,
“file_ids”: ,
“pending_post_id”: “”,
“remote_id”: “”,
“reply_count”: 1,
“last_reply_at”: 0,
“participants”: null,
“metadata”: {}
}
]

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

I used the following command to update n8n:
docker run -d --name n8n --restart unless-stopped
-p 8080:8080
-v n8n_data:/home/node/.n8n
-v /opt/n8n/files:/tmp
-e N8N_LISTEN_ADDRESS=0.0.0.0
-e N8N_PORT=8080
-e N8N_PROTOCOL=http
-e N8N_HOST=10.66.208.235
-e N8N_SECURE_COOKIE=false

docker.n8n.io/n8nio/n8n:latest

3

I am getting the same error. Any movement on this?

4

hello, im getting the same on [email protected]

i just jump from cca 1.117.3 and there wasnt this problem.

now i will try to downgrade to find version without this problem.

UPDATE:

i have another instance the same version (but another VPS) and there is it working. One difference i can see - here i have https

and problematic instance is http

UPDATE2:

found it - its a 1.120.x problem - read more here: After update to 1.120.3 -> window.crypto.randomUUID is not a function · Issue #22017 · n8n-io/n8n · GitHub

1 Like
5

resolved when I downgrade to 1.119.x

6

just upgraded docker to the “next” version (1.121.2) and seems to work fine now

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.