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
{{ message }}
This repository has been archived by the owner on May 19, 2023. It is now read-only.
DevOps has rather often a problem when receiving error
Error: Invalid JSON RPC response: ""
While this is not issue of Cache but usually the deployment and most probably not accessible RSKj node, we should add a check to the ethFactory() which calls web3.eth.getProtocolVersion() that verifies that:
there is live server on the provider address
there is live ETH compatible server on the provider address
If the call fails, we can then display some better error about Provider's unavailability.
The text was updated successfully, but these errors were encountered:
DevOps has rather often a problem when receiving error
While this is not issue of Cache but usually the deployment and most probably not accessible RSKj node, we should add a check to the
ethFactory()
which callsweb3.eth.getProtocolVersion()
that verifies that:If the call fails, we can then display some better error about Provider's unavailability.
The text was updated successfully, but these errors were encountered: