Fix/caddy ws flush and upgrade limit - #1
Merged
Conversation
Disable response buffering on the RPC upstream (flush_interval -1) so WebSocket frames pass through immediately. Buffering stalled long-lived subscription sockets, which surfaced as WS connections dying after a few seconds and clients reconnecting in a loop. Raise the WS upgrade limit from 10 to 30 events / 60s on both the CF-Connecting-IP and direct-origin zones, so the reconnect storms caused by the above don't trip the limiter while the fix is validated. Also pin COMPOSE_PROJECT_NAME=testnet in the RPC .env example. Compose derives the volume prefix from the directory name, so this stack would look for `rpc_rpc-node-data` while nodes deployed from the old `docker/testnet/` layout keep their chain DB in `testnet_rpc-node-data`. Without the pin, migrating an existing RPC starts an archive resync from block 0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.