Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WS connection and messages limit improvements #2367

Open
quiet-node opened this issue Apr 18, 2024 · 0 comments
Open

WS connection and messages limit improvements #2367

quiet-node opened this issue Apr 18, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@quiet-node
Copy link
Collaborator

Problem

Currently, the WS server relies on environment variables WS_CONNECTION_LIMIT and WS_CONNECTION_LIMIT_PER_IP to determine the maximum amount of connections that can subscribe to the websocket. The fallback value is 10, which means if the env vars are not configured, the WS server only accepts max 10 connections from either multiple client machines or from 1 client machine (signle IP address).

The second issue is that currently, there's no limit configured for methods sent to the server.

Solution

Increase the fallback value for the connection limit

  • WS_CONNECTION_LIMIT = TBD (currently 10)
  • WS_CONNECTION_LIMIT_PER_IP = TBD (currently 10)
  • WS_METHOD_REQUEST_LIMIT_PER_IP = TBD

Alternatives

No response

@quiet-node quiet-node added the enhancement New feature or request label Apr 18, 2024
@quiet-node quiet-node self-assigned this Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant