Skip to content

bug: Jwt.hex error with Nethermind Client  #355

Open
@GLCNI

Description

@GLCNI

Lately running into this issue, following the docs for setting up execution client (nethermind v1.15.0) where the client runs in a loop stopping and restarting with the error

execution  | 2023-01-11 23:41:08.6730|Cannot write authentication secret to '/jwt.hex'. To change file location, set the 'JsonRpc.JwtSecretFile' parameter. System.UnauthorizedAccessException: Access to the path '/jwt.hex' is denied.
execution  |  ---> System.IO.IOException: Permission denied

This has worked before without any issues, but testing again recently after reports from other users having difficulties. I am encountering the same problem.

Steps to Re-produce

Fresh install of Ubuntu 20.04LTS running locally, update the system, install docker (v20.10.22) and docker-compose (v2.2.3), following instructions here : https://docs.gnosischain.com/node/guide/execution/nethermind/#using-docker

Make directories

mkdir -p /home/$USER/gnosis/execution
mkdir /home/$USER/gnosis/jwtsecret

Create jwt.hex
openssl rand -hex 32 | tr -d "\n" > /home/$USER/gnosis/jwtsecret/jwt.hex

Create docker-compose.yml
Using the example docker-compose.yml here: https://docs.gnosischain.com/node/guide/execution/nethermind/#2-docker-compose

this is with a fresh install of Ubuntu 20.04LTS on a local device, I’ve tried this a few times with the same result.

image

important Notes

The file jwt.hex is created and visible in the directory ./gnosis/jwtsecret opening the file the contents are what is expected, there don’t look to be any special permissions with the file.
The file jwt.hex does not appear to exist within the docker containers file system

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions