To ensure a fair and stable experience for all users, we limit the number of websocket connections allowed per user. This helps prevent scenarios where a few high-usage users could impact the performance and stability of the sessions. When the number of websocket connections from your account exceeds this limit, the system automatically restricts the excess connections to maintain optimal performance. Please close the idle connections on your end and try again after some time. For additional assistance, please reach out to support.
Why do I see ‘Connection Restricted: Your websocket connections have exceeded the allowed limit’ in my logs?
Did this answer your question?
What did you like?
We're sorry to hear that.
Thank you for your feedback.
Related articles
- Local Testing
- Local Testing Internals
- Inbound IP Whitelisting
- Local Binary Release Notes
- Why are my TCP connections failing during local testing?
- When using BrowserStack Local, I encountered the ‘self signed certificate in certificate chain‘ error. What should I do?
- When using BrowserStack Local, I encountered the ‘Could not start Browserstack Local: Looks like you have SSL inspection enabled.‘ error. What should I do?
