Skip to content
Discussion options

You must be logged in to vote

Scratch that, my initial attempt at rebuilding the package wasn't fruitful but I figured out the problem. The beacon error is gone since the flag is now available, I'll try to troubleshoot the new errors (failed to init L2: failed to get L2 chain ID: 401 Unauthorized: signature is invalid) and get back to you if I'm stuck. Thank you! ❤️

401 Unauthorized: signature is invalid usually means your opgeth(--authrpc.jwtsecret) and opnode(--l2.jwt-secret) didn't use same jwt file

Replies: 2 comments 10 replies

Comment options

You must be logged in to vote
10 replies
@zaguezzar
Comment options

@imtipi
Comment options

@zaguezzar
Comment options

@imtipi
Comment options

Answer selected by opfocus
@javjerez
Comment options

@imtipi
Comment options

@javjerez
Comment options

@imtipi
Comment options

Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
op-stack-deployment Questions relating to deploying your own OP Stack. discussion-metrics Used by Github Action to gather discussion metrics on the question and answer section.
4 participants