Protected Endpoints for Ethereum and Quorum Nodes on Chainstack
With the release of Chainstack 1.3, we are happy to be introducing protected endpoints for all Ethereum and Quorum nodes using basic access authentication. This is in line with our commitment to providing secure and stable development environments for our users and marks the completion of our goal to have all endpoints protected by default for all nodes across all protocols that we support.
With this change, we will be deprecating all unprotected endpoints by October 1, 2019 (see timeline below). Read on to find out what you need to know to avoid breakages in your applications running on Chainstack nodes.
What does this mean for you?
If you are currently accessing a Quorum or Ethereum node on Chainstack using unprotected RPC or WSS endpoints, you will need to transition to using the new endpoints that require username and password before we stop supporting them on October 1, 2019.
You can find the protected endpoints at the top of your node’s access and credentials section, with the username and password required to access them listed right below. The old, unprotected credentials will still be listed at the bottom of the section, identified with an ‘unlocked’ icon.
When deploying new Quorum or Ethereum nodes, we encourage you to only use the protected endpoints, shown at the top of your node’s access and credentials section.
Connecting to protected endpoints
In order to connect to and interact with the new endpoints, you will need to include the username and password in your connection request. For instance, connect to a protected Geth node over RPC with the URL in the following format:
geth attach https://USERNAME:PASSWORD@RPC_ENDPOINT
- USERNAME — your Ethereum node access username.
- PASSWORD — your Ethereum node access password.
- RPC_ENDPOINT — your Ethereum node RPC endpoint.
Connect to your node:
geth attach https://user-name:firstname.lastname@example.org
Visit the Chainstack Docs for more information about interacting with your nodes.
- September 3, 2019: Chainstack 1.3 released with the introduction of new, protected endpoints. Unprotected endpoints remain accessible and visible in the Chainstack platform.
- October 1, 2019: Unprotected endpoints to be deprecated, removed from the platform and no longer accessible.
Feel free to contact us at email@example.com if you have any questions.