401 Unauthorized: Signature Invalid
If you see a log that looks like this inop-node
:
op-node
is unable to authenticate with execution client
’s authenticated RPC using the JWT secret.
Solution
- Check that the JWT secret is correct in both services.
- Check that
execution client
’s authenticated RPC is enabled, and that the URL is correct.
403 Forbidden: Invalid Host Specified
If you see a log that looks like this inop-node
:
op-node
’s host with execution client
.
Solution
- Make sure that the
--authrpc.vhosts
parameter inexecution client
is either set to the correct host, or*
. - Check that
execution client
’s authenticated RPC is enabled, and that the URL is correct.
Failed to Load P2P Config
If you see a log that looks like this inop-node
:
op-node
lacks write access to the P2P discovery or peerstore directories.
Solution
- Make sure that the
op-node
has write access to the P2P directory. By default, this is/p2p
. - Set the P2P directory to somewhere the
op-node
can access via the--p2p.discovery.path
and--p2p.peerstore.path
parameters. - Set the discovery path to
memory
to disable persistence via the--p2p.discovery.path
and--p2p.peerstore.path
parameters.
Wrong Chain
If you see a log that looks like this inop-node
:
op-node
is pointing to the wrong chain.
Solution
- Verify that the
op-node
’s L1 URL is pointing to the correct L1 for the given network. - Verify that the
op-node
’s rollup config/--network
parameter is set to the correct network. - Verify that the
op-node
’s L2 URL is pointing to the correct instance ofexecution client
, and thatexecution client
is properly initialized for the given network.
Unclean Shutdowns
If you see a log that looks like this inexecution client
:
execution client
has experienced an unclean shutdown. The geth docs
say if Geth stops unexpectedly, the database can be corrupted. This is known as an
“unclean shutdown” and it can lead to a variety of problems for the node when
it is restarted.