n8n - 💡(How to fix) Fix Chat Trigger public chat URL returns "Connection rejected" after upgrade from 2.16.x to 2.17.4 [5 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28891Fetched 2026-04-23 07:44:18
View on GitHub
Comments
5
Participants
4
Timeline
9
Reactions
0
Timeline (top)
commented ×5cross-referenced ×1labeled ×1mentioned ×1

Error Message

Describe the problem/error/question What is the error message (if any)? So instead of receiving the expected chat continuation from the workflow, the public Chat URL fails with that error. • error: all

Root Cause

Share the output returned by the last node I cannot provide a reliable successful output from the final node because the issue happens during the chat interaction itself. From the user side, the observable result is: Connection rejected So instead of receiving the expected chat continuation from the workflow, the public Chat URL fails with that error.

Fix Action

Fix / Workaround

After upgrading from n8n 2.14.2 (and I think also 2.16.1) to n8n 2.17.4, a workflow that was previously working stopped working. The workflow uses: • Chat Trigger • Chat node with sendAndWait with approval buttons (the one that gives the message and stays there)• • a timeout path The important point is that the issue is not related to a custom frontend. I can reproduce it directly using the public Chat URL generated by the Chat Trigger (not in the chat of the n8n editor as the buttons will not be shown as this is still a pending bug to fix: https://github.com/n8n-io/n8n/issues/27187: https://xxxxxxxx/webhook/3e79xxxxxxxxx/chat When I open that public Chat URL and try to use the chat, the execution starts but the chat ends up returning: Connection rejected This same workflow worked correctly on 2.14.2 (and I think also 2.16.1) before the upgrade to 2.17.4.

RAW_BUFFERClick to expand / collapse

Describe the problem/error/question

After upgrading from n8n 2.14.2 (and I think also 2.16.1) to n8n 2.17.4, a workflow that was previously working stopped working. The workflow uses: • Chat Trigger • Chat node with sendAndWait with approval buttons (the one that gives the message and stays there)• • a timeout path The important point is that the issue is not related to a custom frontend. I can reproduce it directly using the public Chat URL generated by the Chat Trigger (not in the chat of the n8n editor as the buttons will not be shown as this is still a pending bug to fix: https://github.com/n8n-io/n8n/issues/27187: https://xxxxxxxx/webhook/3e79xxxxxxxxx/chat When I open that public Chat URL and try to use the chat, the execution starts but the chat ends up returning: Connection rejected This same workflow worked correctly on 2.14.2 (and I think also 2.16.1) before the upgrade to 2.17.4.

Steps to reproduce

  1. Use the workflow (image below) or any workflow with a Chat Trigger and a Chat node with sendAndWait
  2. Open the public Chat URL from the Chat Trigger: https://xxxxxxxx/webhook/3e79xxxxxxxxx/chat
  3. Start the chat.
  4. The workflow starts, but instead of continuing normally, the chat returns: Connection rejected

Expected behavior The public Chat URL should work normally and the workflow should continue through the expected chat interaction: • ask the user "Do you prefer boat or plane travel?" • allow choosing Plane or Boat with buttons (if you dont use the URL but the n8n chat the buttons will not be displayed (this is still a bug already reported: https://github.com/n8n-io/n8n/issues/27187), so you need to use the URL instead.) • or continue to the Timeout branch if no answer is received Actual behavior: The public Chat URL itself fails and returns: Connection rejected

What is the error message (if any)? Connection rejected

Please share your workflow/screenshots/recording

<img width="597" height="375" alt="Image" src="https://github.com/user-attachments/assets/146f5319-76a7-41a6-aabf-28c8f24457c4" /> <img width="1209" height="853" alt="Image" src="https://github.com/user-attachments/assets/ef10d422-51c1-48a9-95c8-02299fb505c0" /> <img width="702" height="589" alt="Image" src="https://github.com/user-attachments/assets/c36e4464-e244-4083-91cf-bf1adf169d39" />

Share the output returned by the last node I cannot provide a reliable successful output from the final node because the issue happens during the chat interaction itself. From the user side, the observable result is: Connection rejected So instead of receiving the expected chat continuation from the workflow, the public Chat URL fails with that error.

Debug info core • n8nVersion: 2.17.4 • platform: docker (self-hosted) • nodeJsVersion: 24.14.1 • nodeEnv: production • database: postgres • executionMode: regular • concurrency: -1 • license: enterprise (production) storage • success: all • error: all • progress: false • manual: true • binaryMode: filesystem pruning • enabled: true • maxAge: 336 hours • maxCount: 10000 executions client • userAgent: mozilla/5.0 (windows nt 10.0; win64; x64) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36 • isTouchDevice: false Generated at: 2026-04-22T10:40:54.579Z

extent analysis

TL;DR

The "Connection rejected" error in n8n 2.17.4 may be related to changes in the Chat Trigger or node configuration, requiring a review of the workflow and potential updates to the chat node settings.

Guidance

  • Review the Chat Trigger and Chat node configurations to ensure they are compatible with n8n 2.17.4, as changes in the new version might have introduced the issue.
  • Check the n8n documentation and release notes for 2.17.4 to see if there are any specific requirements or updates needed for the Chat Trigger and Chat nodes.
  • Test the workflow with a different node or trigger to isolate if the issue is specific to the Chat Trigger or a more general problem.
  • Consider downgrading to n8n 2.16.1 to verify if the issue is indeed version-specific, although this should be a last resort due to potential security and feature updates in newer versions.

Example

No specific code example can be provided without more details on the workflow configuration, but reviewing the node settings and ensuring they match the expected format for n8n 2.17.4 is crucial.

Notes

The issue seems to be version-specific, given that it appeared after upgrading from n8n 2.14.2 or 2.16.1 to 2.17.4. However, without more detailed logs or specific configuration details, it's challenging to provide a precise fix.

Recommendation

Apply a workaround by reviewing and potentially updating the Chat Trigger and Chat node configurations to ensure compatibility with n8n 2.17.4, as this is the most direct approach to resolving the "Connection rejected" error without downgrading the version.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix Chat Trigger public chat URL returns "Connection rejected" after upgrade from 2.16.x to 2.17.4 [5 comments, 4 participants]