Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Polkadot: 429 Too many requests #7039

Closed
rootsoklahoma opened this issue Apr 10, 2023 · 6 comments
Closed

Polkadot: 429 Too many requests #7039

rootsoklahoma opened this issue Apr 10, 2023 · 6 comments

Comments

@rootsoklahoma
Copy link

During high load, HTTP requests to the node start failing with the error "429 Too many requests: Too many connections. Please try again later." This same error is also displayed in the node's logs (screenshot).
Is there a way to increase the number of simultaneously open connections, similar to using the '--ws-max-connections' flag for websockets?

image

@bkchr
Copy link
Member

bkchr commented Apr 11, 2023

Cc @niklasad1

@niklasad1
Copy link
Member

niklasad1 commented Apr 11, 2023

No, unfortunately not it's hardcoded on the server running on --rpc-port but it will fixed by paritytech/substrate#13384

More information regarding this can be found here

@arturgontijo
Copy link

I faced that issue few days ago and just stopped using the HTTP server in favor of the WS one.

If I understood it right, the WS server supports both protocols...so, if you are using --ws-port=9944 you can set your HTTP client to point to http://localhost:9944 and it should work too.

@niklasad1
Copy link
Member

If I understood it right, the WS server supports both protocols...so, if you are using --ws-port=9944 you can set your HTTP client to point to http://localhost:9944 and it should work too.

Yes, that is correct and the max connections will use --ws-max-connections but we have planned to remove all specific HTTP/WS as these apply globally on the RPC server.

@brunopgalvao
Copy link
Contributor

@bkchr
Copy link
Member

bkchr commented Apr 11, 2023

Closing, please re-open if something is missing.

@bkchr bkchr closed this as completed Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants