rpcdaemon: same default WebSocket port as erigon #15643
Merged
Conversation
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
AskAlexSharov
approved these changes
Jun 19, 2025
2482e9b to
55f3c9e
Compare
|
@canepat https://github.com/erigontech/erigon?tab=readme-ov-file#default-ports-and-firewalls |
This was referenced Jul 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #10068
Currently, when you enable WebSocket (WS) support in stand-alone
rpcdaemon, the WS server listening port changes in every run because the associated configuration parametercfg.WebsocketPortassumes a random default value and is not tied to any command-line option.This is different from
erigon, where the same configuration parameter is associated to thews.portoption, which is set to 8546 by default.