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

Can't update JSON-RPC Server for Beacon Nodes #289

Open
ahmed-abdelhamid opened this issue Sep 25, 2023 · 2 comments
Open

Can't update JSON-RPC Server for Beacon Nodes #289

ahmed-abdelhamid opened this issue Sep 25, 2023 · 2 comments

Comments

@ahmed-abdelhamid
Copy link
Member

JSON-RPC Server for Beacon Nodes created using Prysatic Labs Prysm is always "on" by default but when try to update it is value, I got "500 Internal server error"

@mohamed-abdelrhman
Copy link
Collaborator

  • JSON-RPC and REST are enabled by default is a business decision to enable node stats by default
  • Disabling JSON-RPC for beacon nodes is not possible. The spec.rpc feature cannot be disabled in the Prysm client. We are aware that a more informative error message should be provided. However, for the time being, can you ensure that users cannot update the RPC settings in the Prysm client from your side by disable the update for this case.

@ahmed-abdelhamid
Copy link
Member Author

  • Thank you, I disabled the switch for JSON-RPC Server in case of client is Prysm.
  • Please notice that however JSON-RPC is enabled by default to enable node stats for beacon nodes created using Prysm client, websockets always respond with "REST API sever is not enabled". I do not understand this as Prysm clients have only JSON-RPC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants