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
Using version 0.6.0, using 20.04LTS. fails at JWT secret generation, not found. Gnosischain and Ethereum
To Reproduce
sedge v0.6.0 sedge cli --network gnosis -c lighthouse -e nethermind
(sedge cli -c lighthouse -e nethermind) same result
Result [ERRO] JWT secret generation failed. Error: open /home/glc/docker-compose-scripts/jwtsecret: no such file or directory.
No directory is created for docker-compose-scripts
Screenshots
Had dependencies installed previous already on this device,
docker-compose version
v2.2.3
attempted with fresh OS 20.04LTS and dependencies installed via sedge, same result
Additional Info:
Using Sedge Version: 0.5.0
This works still, must manually change the version for nethermind 1.14.6 > 1.15.0 to start syncing.
The text was updated successfully, but these errors were encountered:
Hi @GLCNI@tharune . Thanks for reporting. Sadly this is a know issue an should be fixed in the next release. The problem is with a non existing generation path which is the case by default. A workaround is to change this path to another one that exist for example: sedge cli -p .
Using version 0.6.0, using 20.04LTS. fails at JWT secret generation, not found. Gnosischain and Ethereum
To Reproduce
sedge v0.6.0
sedge cli --network gnosis -c lighthouse -e nethermind
(
sedge cli -c lighthouse -e nethermind
) same resultResult
[ERRO] JWT secret generation failed. Error: open /home/glc/docker-compose-scripts/jwtsecret: no such file or directory.
No directory is created for
docker-compose-scripts
Screenshots
Had dependencies installed previous already on this device,
attempted with fresh OS 20.04LTS and dependencies installed via sedge, same result
Additional Info:
Using Sedge Version: 0.5.0
This works still, must manually change the version for nethermind 1.14.6 > 1.15.0 to start syncing.
The text was updated successfully, but these errors were encountered: