You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"
The text was updated successfully, but these errors were encountered:
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.
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.
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"
The text was updated successfully, but these errors were encountered: