Unable to approve SendAndWait responses – always receiving ‘Invalid token'

Questions
1

Describe the problem/error/question

I’m running an on-premise n8n instance behind nginx on a VPS.
Everything works normally except for all nodes using “Send message and wait for response” (Telegram, Discord, etc.).

When I click the approval button or send a free-text response, I get this in my browser:

{“error”: “Invalid token”}

The workflow stays stuck waiting.
This happens 100% of the time, regardless of platform.

I found issue sendAndWait Broken with missing/invalid token · Issue #18610 · n8n-io/n8n · GitHub and tried the suggested proxy fixes, but the error still persists.

What is the error message (if any)?

{“error”: “Invalid token”}

Please share your workflow

A minimal example reproduces the problem:

  1. Trigger (manual)

  2. Telegram/Discord/Slack — Send message and wait for response

  3. Click Approve → browser opens → “Invalid token”

Same issue with free-text response.

Share the output returned by the last node

Share the output returned by the last node

The workflow stays in waiting state.
No output is produced.
Browser callback simply says:

{"error": "Invalid token"}

Information on your n8n setup

  • n8n version: Version 1.122.5
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default (own, main)
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker (self-hosted)
  • **Operating system:**Ubuntu 22.04 on VPS

Any help would be appreciated — I can provide logs or test patches if needed.

Thanks!

1 Like
2

Hi @lorvaill, welcome!

That’s strange, I’ve never encountered an issue like that..
I checked the GitHub link and saw many similar cases, Did you try setting:

N8N_PROXY_HOPS=1

Also, what’s your setup on the VPS? Are you using any server management tools like Coolify, EasyPanel, etc.? I’ve used both and never had this problem, so if I had to guess, it might be something related to SSL, idk..

Finally, I’d recommend upgrading n8n to the latest version (or beta) and trying again.

3

Hey, thanks for the feedback! I did try what you suggested. I even tried setting it to 0, 1, and 2, just in case it worked like magic :p. I don’t use any of those tools, just pure CMD. I updated before publishing and it didn’t change anything. What’s more, I’ve had this problem for several updates, but until now I didn’t really need this node and I thought, “Oh, it will be resolved in a future update.”

4

up bcs still stuck