Creating new node and X509: certificate signed by unknown authority

[kosti11]

Hello,

I have problem with starting my new second node. There’s problem with certificate authority. Can anyone find solution for my problem? Last forum topics didn’t help me. I looked too on my first node using docker inspect storagenode, settings are looking the same except file location but problem still occurs.

I would be thankful for your help.

[LinuxNet]

Did you authorize the identity?
https://documentation.storj.io/dependencies/identity#authorize-the-identity

[kosti11]

Yes. When i used grep commands it gave me 2 and 3.

[Alexey]

Please show the output of the command:

docker pull storjlabs/storagenode

[kosti11]

[Alexey]

Please, stop and remove the storagenode container and run it back with all your parameters: https://documentation.storj.io/setup/cli/storage-node#running-the-storage-node
Make sure that you updated your docker run command with new parameters.

I would like recommend to run a watchtower to update your storagenode automatically next time: https://documentation.storj.io/setup/cli/software-updates#automatic-updates

[kosti11]

Have done that a lot of times without any effect. I’m really helpless.

[Alexey]

Please, use this image for your node for a while:

X509: certificate signed by unknown authority for https://tardigrade.io/trusted-satellites

You can pull the 32 bit image, by specifying the --platform arm32v6, but the docker should be configured to use experimental features for that. Or use the explicit tag for the 1.18.1 arm image: docker pull storjlabs/storagenode:2413a9a0d-v1.18.1-go1.15.5-arm32v6 Also, please use a full volume binding command instead of simple in the docker-compose: https://docs.docker.com/compose/compose-file/#long-syntax-3 Use the type bind, otherwise you risking to get a disqualification if your drive woul…

I hope the next image will be build correctly and you can replace the tag to the latest.

[kosti11]

Yeah. Problem was fixed after update. Thank you for help.