Webhook with code node crash

Describe the problem/error/question

What is the error message (if any)?

No error message but webhook call crash when my webhook workflow contains a code node. Is it normal (for security reasons or something ?) When I delete my code node it works

Share the output returned by the last node

No output just crash :

Error with code node :

No error without code node :

Information on your n8n setup

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

Hey @Kent1,

That is odd, I have a few webhooks that use code nodes so I would expect them to work but. I would first recommend upgrading as 0.231.1 is really old now and if it was a bug in that release it would probably be fixed by now.

Have you tried making a workflow that only has a webhook node in it and a code node to see if that works?

Hi @Jon,

Thanks for your help.

We should definitly upgrade our n8n version, but once we had issue with the upgrade so we are a bit affraid now, but we will.

Same issue when I call a webhook with only a code node (with default code inside) :

We will upgrade at least or pre-production instance to see if the problem persist or not after the upgrade.

1 Like

Hello @Jon,

I wanted to upgrade n8n but there is no more debian image ? We used debian to do some customisation and use “Execute command” node to make some kerberos command. See bellow what we use to do.

Is it possible to keep this custom config with n8n 1.11.1 ?

Thank a lot for your help.

Hey @Kent1,

That is a good question, Sadly I don’t have an answer for that as it would depend on if the packages are available in Alpine I suspect they will be but it means you would need to update your docker file to use the apk package manager instead.

1 Like

Hello @Jon,

Thank for your help. I succed to make a custom n8n image to be able to make ldap request through execute command node.

However, I have one last point to manage. Since the update some requests make via HTTP Request node don’t work anymore. Before the migration I used the following ENV variable : N8N_USE_DEPRECATED_REQUEST_LIB (but now it is deprecated) and I set proxy ENV http_proxy and https_proxy in the docker image.

I found an other topics that mention the same problem, and it’s because axios package that is used doesn’t support https request through http proxy ? Unfortunatly we can’t upgrade our prod if we can’t use http request node to make https calls. Do you know if this problem will be solve soon ?

Hey @Kent1,

I popped a reply on that thread before seeing your response here.

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