Error when setting up a Validator node

Tutorials and Guides From DA Support
1

  • Problem
    You are trying to set up a devEnv validator node but you get an error saying validator is unhealthy. There could be lot of reason for that, here are some common issue you can face.

  • Analysis:
    First thing you want is to check the logs to know exactly what is the error.
    If you are using docker-compose you can use docker logs splice-validator-validator-1 > ./validatorLog.log to extract the logs into a file then identify the error message.

  • Solution:

    • HTTP 403 Forbidden
      The 403 Forbidden response typically indicates that the server understood the request but refuses to authorise it. It usually happens when you IP has not been whitelisted yet, please refer to the documentation to validate that your ip has been approved

    • Unknown secret
      This error indicate that your ONBOARDING_SECRET is not valid. ONBOARDING_SECRET expire so you may need to curl a new one

    • If this doesn’t work or you have another issue you should try to restart to spin up the node from a clean state. to do that with docker compose you can:
      1. Spin down your current setup using the stop.sh script
      2. Delete all volumes related to that setup with the command “docker volume rm splice-validator_postgres-splice splice-validator_domain-upgrade-dump”
      3. Generate a new secret from the same SV that you are onboarding with (sv-2 or sv-1)
      4. Attempt to spin up the node again.

Hopefully this will help you setting up a validator node on the Canton Network.
If you don’t know where to start please refer to the official GSF documentation

2 Likes