n8n - 💡(How to fix) Fix n8n Mongodb Chat node giving error when 10 user start chatting simultaneously [1 comments, 2 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#28380Fetched 2026-04-13 05:45:16
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Author
Timeline (top)
closed ×1commented ×1labeled ×1

Error Message

n8n Mongodb Chat node giving error when 10 user start chatting simultaneously

MongoDB connection error: Server selection timed out after 30000 ms

MongoDB connection error: Server selection timed out after 30000 ms

RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

n8n Mongodb Chat node giving error when 10 user start chatting simultaneously

MongoDB connection error: Server selection timed out after 30000 ms

Share the output returned by the last node

MongoDB connection error: Server selection timed out after 30000 ms

<img width="1240" height="664" alt="Image" src="https://github.com/user-attachments/assets/697517f3-1ec9-4ea5-9544-cffb2e699289" />

Debug info

core

  • n8nVersion: 2.15.1

Generated at: 2026-04-13T00:51:40.314Z

extent analysis

TL;DR

Increase the MongoDB connection timeout or optimize the database configuration to handle concurrent connections.

Guidance

  • Check the MongoDB server configuration to ensure it can handle 10 simultaneous connections from the n8n Chat node.
  • Verify that the n8n node is properly configured to handle concurrent connections, and consider increasing the connection pool size if possible.
  • Investigate optimizing MongoDB queries or indexing to reduce the load on the database and prevent timeouts.
  • Consider implementing a retry mechanism in the n8n workflow to handle temporary connection timeouts.

Example

No specific code example is provided, as the issue is related to configuration and database optimization.

Notes

The provided information suggests a connection timeout issue, but the root cause may be related to the MongoDB server configuration, n8n node configuration, or the workload of the database. Further investigation is needed to determine the best solution.

Recommendation

Apply workaround: Increase the MongoDB connection timeout or optimize the database configuration to handle concurrent connections, as upgrading to a fixed version is not implied in the provided issue.

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