Skip to content

Comments

Fixed JWT_SECRET value is not being saved in the .env file#1746

Merged
yorickdowne merged 1 commit intoethstaker:mainfrom
victorelec14:patch-2
Feb 12, 2024
Merged

Fixed JWT_SECRET value is not being saved in the .env file#1746
yorickdowne merged 1 commit intoethstaker:mainfrom
victorelec14:patch-2

Conversation

@victorelec14
Copy link
Contributor

@victorelec14 victorelec14 commented Feb 11, 2024

Hi,

By using a Custom EL, the JWT_SECRET token entered in the Wizard does not get saved in the .env file, which later causes 'Failed jwt authorization - InvalidToken' issues when Consensus attempts to communicate.

consensus-1  | Feb 11 20:44:18.348 ERRO Error updating deposit contract cache   error: Invalid endpoint state: RequestFailed("eth_chainId call failed Auth(InvalidToken)"), retry_millis: 60000, service: beacon
consensus-1  | Feb 11 20:44:23.505 ERRO Failed jwt authorization                error: InvalidToken, service: exec

The JWT token generates a new random value and does not use the one provided in the Wizard.

docker compose exec consensus cat /var/lib/lighthouse/beacon/ee-secret/jwtsecret
06835bd9def92b91e95a1bw93bbcaae646288c767a53d785dceaae8d26c2905a

After putting the correct JWT token, everything works normally.

consensus-1  | Feb 11 20:45:13.141 INFO Block production enabled                method: json rpc via http, endpoint: Auth { endpoint: "http://192.168.178.121:8551/", jwt_path: "/var/lib/lighthouse/beacon/ee-secret/jwtsecret", jwt_id: None, jwt_version: None }

Stack:

eth.docker: Version 2.6.1.0
Consensus version: Lighthouse/v4.6.0-c7e5dd1
Execution Layer: Custom 

Thanks.

By using a Custom Execution Layer, the JWT_SECRET token entered in the Wizard is not being saved in the .env file. This subsequently causes issues when the Consensus attempts to communicate.
@yorickdowne yorickdowne merged commit a425fc8 into ethstaker:main Feb 12, 2024
@victorelec14 victorelec14 deleted the patch-2 branch February 12, 2024 18:19
@victorelec14 victorelec14 restored the patch-2 branch February 12, 2024 18:19
@victorelec14 victorelec14 deleted the patch-2 branch February 12, 2024 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants