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

Ok, I will try that. Thanks

Unfortunately I’m having the same whitelist problem with the arm image:

2020-12-13T18:41:45.486Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”},
2020-12-13T18:41:45.492Z INFO Operator email {“Address”: “xxxxxxx@hotmail.com”},
2020-12-13T18:41:45.492Z INFO Operator wallet {“Address”: “0xxxxxxxxxxxxx”},
2020-12-13T18:41:45.851Z INFO Telemetry enabled {“instance ID”: “12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp”},
2020-12-13T18:41:46.981Z INFO db.migration Database Version {“version”: 46},
2020-12-13T18:41:47.919Z WARN trust Failed to fetch URLs from source; used cache {“source”: “https://tardigrade.io/trusted-satellites”, “error”: “HTTP source: Get “https://tardigrade.io/trusted-satellites”: x509: certificate signed by unknown authority”, “errorVerbose”: “HTTP source: Get “https://tardigrade.io/trusted-satellites”: x509: certificate signed by unknown authority\n\tstorj.io/storj/storagenode/trust.(*HTTPSource).FetchEntries:63\n\tstorj.io/storj/storagenode/trust.(*List).fetchEntries:90\n\tstorj.io/storj/storagenode/trust.(*List).FetchURLs:49\n\tstorj.io/storj/storagenode/trust.(*Pool).fetchURLs:240\n\tstorj.io/storj/storagenode/trust.(*Pool).Refresh:177\n\tstorj.io/storj/storagenode.(*Peer).Run:781\n\tmain.cmdRun:218\n\tstorj.io/private/process.cleanup.func1.4:362\n\tstorj.io/private/process.cleanup.func1:380\n\tgithub.com/spf13/cobra.(*Command).execute:842\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:950\n\tgithub.com/spf13/cobra.(*Command).Execute:887\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.ExecCustomDebug:70\n\tmain.main:385\n\truntime.main:204”},
2020-12-13T18:41:47.957Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.,
2020-12-13T18:41:48.819Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.,
2020-12-13T18:41:48.820Z INFO bandwidth Performing bandwidth usage rollups,
2020-12-13T18:41:48.821Z INFO Node 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp started,
2020-12-13T18:41:48.821Z INFO Public server started on [::]:28967,
2020-12-13T18:41:48.821Z INFO trust Scheduling next refresh {“after”: “8h49m13.256222059s”},
2020-12-13T18:41:48.821Z INFO Private server started on 127.0.0.1:7778,
2020-12-13T18:41:48.981Z ERROR contact:service ping satellite failed {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “attempts”: 1, “error”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert”, “errorVerbose”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”},
2020-12-13T18:41:49.171Z ERROR contact:service ping satellite failed {“Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “attempts”: 1, “error”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert”, “errorVerbose”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”},
2020-12-13T18:41:49.465Z ERROR contact:service ping satellite failed {“Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “attempts”: 1, “error”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert”, “errorVerbose”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”},
2020-12-13T18:41:50.130Z ERROR contact:service ping satellite failed {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “attempts”: 2, “error”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert”, “errorVerbose”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”},
2020-12-13T18:41:50.239Z ERROR contact:service ping satellite failed {“Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “attempts”: 1, “error”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert”, “errorVerbose”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”},
2020-12-13T18:41:50.401Z ERROR contact:service ping satellite failed {“Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “attempts”: 1, “error”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert”, “errorVerbose”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”},
2020-12-13T18:41:50.512Z ERROR contact:service ping satellite failed {“Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “attempts”: 2, “error”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert”, “errorVerbose”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”},
2020-12-13T18:41:51.107Z ERROR contact:service ping satellite failed {“Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “attempts”: 2, “error”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert”, “errorVerbose”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”},

Ok so I deleted the config and I’m getting the same “x509: certificate signed by unknown authority” error now with the arm image.

The storjlabs/storagenode:arm must work, I checked it on my rpi3
Seems your device using the aarch64 anyway.
Make sure that you run the storagenode with the storjlabs/storagenode:arm image

This is very strange then, I just tired manually and it doesn’t work with the arm image:

pi@gomme600:~ $ sudo docker run -it --entrypoint /bin/sh storjlabs/storagenode:arm
/app # wget -O - https://tardigrade.io/trusted-satellites
Connecting to tardigrade.io (104.198.14.52:443)
wget: error getting response: Connection reset by peer

What is the Image ID for the storjlabs/storagenode:arm?

$ docker run -it --rm --entrypoint /bin/sh storjlabs/storagenode:arm
/app # wget -O - https://tardigrade.io/trusted-satellites
Connecting to tardigrade.io (104.198.14.52:443)
writing to stdout
12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S@us-central-1.tardigrade.io:7777
12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs@europe-west-1.tardigrade.io:7777
121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6@asia-east-1.tardigrade.io:7777
1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE@saltlake.tardigrade.io:7777
12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB@europe-north-1.tardigrade.io:7777
-                    100% |************************************************************************|   417  0:00:00 ETA
written to stdout
$ docker images storjlabs/storagenode
REPOSITORY              TAG                 IMAGE ID            CREATED             SIZE
storjlabs/storagenode   latest              efb7528d1df3        7 days ago          29.5MB
storjlabs/storagenode   arm                 bb347b79869d        7 days ago          35.4MB

The latest is a broken aarch64 in that output

Just checked, the Id is the same as the 64bit version. How could I force it to download to arm 32 bit version? I am running a 64bit OS.

pi@gomme600:~ $ sudo docker images storjlabs/storagenode
REPOSITORY TAG IMAGE ID CREATED SIZE
storjlabs/storagenode arm efb7528d1df3 8 days ago 29.5MB
storjlabs/storagenode latest efb7528d1df3 8 days ago 29.5MB

Ok, so I tried removing everything related to storagenode using docker rmi and that was successful. I did a docker pull for storjilabs/storagenode:arm which downloaded a fresh image. Unfortunately the ID is still efb7528d1df3 ! Is it possible to download the arm 32bit image on a 64bit system?

Thank you so much for all the help by the way!

I have tried a different version : sudo docker pull storjlabs/storagenode:56dee2aef-v1-18-4-slc-1-go1.15.5-arm32v6

I am getting a different error about the clock.

Here is my docker compose:

version: ‘2’

services:
app:
image: storjlabs/storagenode:56dee2aef-v1-18-4-slc-1-go1.15.5-arm32v6
mem_limit: 800m
network_mode: host
#command: /entrypoint
ports:
- 28967:28967
- 14002:14002
- 7778:7778
restart: always
volumes:
- /srv/dev-disk-by-label-Files/Storj/Storagenode:/app/config
- /srv/dev-disk-by-label-Files/Storj/Identity:/app/identity
environment:
- WALLET=0xxxxxxxxxxxx
- EMAIL=xxxxxx@hotmail.com
- ADDRESS=86.xxx.xx.xxx:28967
- STORAGE=2TB
- BANDWIDTH=100000TB
- UID=1000
- GID=1000
- TZ=Europe/Paris
- SETUP=false
#- signer.tls.use-peer-ca-whitelist=false
logging:
driver: “json-file”
options:
max-size: “50m”
max-file: “10”

The timezone is correct, I am in France.

Here is the log:
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:842,
github.com/spf13/cobra.(*Command).ExecuteC,
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950,
github.com/spf13/cobra.(*Command).Execute,
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887,
storj.io/private/process.ExecWithCustomConfig,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:88,
storj.io/private/process.ExecCustomDebug,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:70,,
n,
/go/src/storj.io/storj/cmd/storagenode/main.go:385,
runtime.main,
/usr/local/go/src/runtime/proc.go:204,
Error: system clock is out of sync: system clock is out of sync with all trusted satellites,
2020-12-15T10:58:49.640Z INFO process/exec_conf.go:284 Configuration loaded {“Location”: “/app/config/config.yaml”},
2020-12-15T10:58:49.643Z INFO storagenode/operator.go:34 Operator email {“Address”: “@hotmail.com”},
2020-12-15T10:58:49.644Z INFO storagenode/operator.go:48 Operator wallet {“Address”: “0x39d5”},
2020-12-15T10:58:50.160Z INFO db.migration migrate/versions.go:218 Database Version {“version”: 46},
2020-12-15T10:58:50.916Z INFO preflight:localtime preflight/localtime.go:54 start checking local system clock with trusted satellites’ system clock.,
2020-12-15T10:58:50.916Z ERROR storagenode/peer.go:786 Failed preflight check. {“error”: “system clock is out of sync: system clock is out of sync with all trusted satellites”, “errorVerbose”: “system clock is out of sync: system clock is out of sync with all trusted satellites\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check:96\n\tstorj.io/storj/storagenode.(*Peer).Run:785\n\tmain.cmdRun:218\n\tstorj.io/private/process.cleanup.func1.4:362\n\tstorj.io/private/process.cleanup.func1:380\n\tgithub.com/spf13/cobra.(*Command).execute:842\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:950\n\tgithub.com/spf13/cobra.(*Command).Execute:887\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.ExecCustomDebug:70\n\tmain.main:385\n\truntime.main:204”},
storj.io/storj/storagenode.(*Peer).Run,
/go/src/storj.io/storj/storagenode/peer.go:786,
main.cmdRun,
/go/src/storj.io/storj/cmd/storagenode/main.go:218,
storj.io/private/process.cleanup.func1.4,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:362,
storj.io/private/process.cleanup.func1,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:380,
github.com/spf13/cobra.(*Command).execute,
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:842,
github.com/spf13/cobra.(*Command).ExecuteC,
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950,
github.com/spf13/cobra.(*Command).Execute,
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887,
storj.io/private/process.ExecWithCustomConfig,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:88,
storj.io/private/process.ExecCustomDebug,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:70,,
n,
/go/src/storj.io/storj/cmd/storagenode/main.go:385,
runtime.main,
/usr/local/go/src/runtime/proc.go:204,
Error: system clock is out of sync: system clock is out of sync with all trusted satellites,
2020-12-15T10:58:53.452Z INFO process/exec_conf.go:284 Configuration loaded {“Location”: “/app/config/config.yaml”},
2020-12-15T10:58:53.455Z INFO storagenode/operator.go:34 Operator email {“Address”: “@hotmail.com”},
2020-12-15T10:58:53.456Z INFO storagenode/operator.go:48 Operator wallet {“Address”: “0x5”},
2020-12-15T10:58:54.006Z INFO db.migration migrate/versions.go:218 Database Version {“version”: 46},
2020-12-15T10:58:54.780Z INFO preflight:localtime preflight/localtime.go:54 start checking local system clock with trusted satellites’ system clock.,
2020-12-15T10:58:54.781Z ERROR storagenode/peer.go:786 Failed preflight check. {“error”: “system clock is out of sync: system clock is out of sync with all trusted satellites”, “errorVerbose”: “system clock is out of sync: system clock is out of sync with all trusted satellites\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check:96\n\tstorj.io/storj/storagenode.(*Peer).Run:785\n\tmain.cmdRun:218\n\tstorj.io/private/process.cleanup.func1.4:362\n\tstorj.io/private/process.cleanup.func1:380\n\tgithub.com/spf13/cobra.(*Command).execute:842\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:950\n\tgithub.com/spf13/cobra.(*Command).Execute:887\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.ExecCustomDebug:70\n\tmain.main:385\n\truntime.main:204”},
storj.io/storj/storagenode.(*Peer).Run,
/go/src/storj.io/storj/storagenode/peer.go:786,
main.cmdRun,
/go/src/storj.io/storj/cmd/storagenode/main.go:218,
storj.io/private/process.cleanup.func1.4,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:362,
storj.io/private/process.cleanup.func1,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:380,
github.com/spf13/cobra.(*Command).execute,
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:842,
github.com/spf13/cobra.(*Command).ExecuteC,
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950,
github.com/spf13/cobra.(*Command).Execute,
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887,
storj.io/private/process.ExecWithCustomConfig,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:88,
storj.io/private/process.ExecCustomDebug,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:70,,
n,
/go/src/storj.io/storj/cmd/storagenode/main.go:385,
runtime.main,
/usr/local/go/src/runtime/proc.go:204,
Error: system clock is out of sync: system clock is out of sync with all trusted satellites,
2020-12-15T10:58:57.254Z INFO process/exec_conf.go:284 Configuration loaded {“Location”: “/app/config/config.yaml”},
2020-12-15T10:58:57.258Z INFO storagenode/operator.go:34 Operator email {“Address”: “@hotmail.com”},
2020-12-15T10:58:57.258Z INFO storagenode/operator.go:48 Operator wallet {“Address”: “0x39d5”},
2020-12-15T10:58:57.758Z INFO db.migration migrate/versions.go:218 Database Version {“version”: 46},
2020-12-15T10:58:58.528Z INFO preflight:localtime preflight/localtime.go:54 start checking local system clock with trusted satellites’ system clock.,
2020-12-15T10:58:58.528Z ERROR storagenode/peer.go:786 Failed preflight check. {“error”: “system clock is out of sync: system clock is out of sync with all trusted satellites”, “errorVerbose”: “system clock is out of sync: system clock is out of sync with all trusted satellites\n\tstorj.io/storj/storagenode/preflight.(*LocalTime).Check:96\n\tstorj.io/storj/storagenode.(*Peer).Run:785\n\tmain.cmdRun:218\n\tstorj.io/private/process.cleanup.func1.4:362\n\tstorj.io/private/process.cleanup.func1:380\n\tgithub.com/spf13/cobra.(*Command).execute:842\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:950\n\tgithub.com/spf13/cobra.(*Command).Execute:887\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.ExecCustomDebug:70\n\tmain.main:385\n\truntime.main:204”},
storj.io/storj/storagenode.(*Peer).Run,
/go/src/storj.io/storj/storagenode/peer.go:786,
main.cmdRun,
/go/src/storj.io/storj/cmd/storagenode/main.go:218,
storj.io/private/process.cleanup.func1.4,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:362,
storj.io/private/process.cleanup.func1,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:380,
github.com/spf13/cobra.(*Command).execute,
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:842,
github.com/spf13/cobra.(*Command).ExecuteC,
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:950,
github.com/spf13/cobra.(*Command).Execute,
/go/pkg/mod/github.com/spf13/cobra@v1.0.0/command.go:887,
storj.io/private/process.ExecWithCustomConfig,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:88,
storj.io/private/process.ExecCustomDebug,
/go/pkg/mod/storj.io/private@v0.0.0-20201026143115-bc926bfa3bca/process/exec_conf.go:70,,
n,
/go/src/storj.io/storj/cmd/storagenode/main.go:385,
runtime.main,
/usr/local/go/src/runtime/proc.go:204,

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 would not mount for any reason.
The 7778 port should not be exposed unless you have an external CLI dashboard. Anyway, if you use a host network, then all ports are exposed to your host directly.
The “clock out of sync” is mean that your node is unable to connect to the satellites.
It could be a firewall or wrong ADDRESS option or wrong port forwarding rule on your router or unsigned identity

1 Like

Ok, I have tried the exact image you provided and I am getting this:

ERROR contact:service ping satellite failed {“Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “attempts”: 6, “error”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert”, “errorVerbose”: “ping satellite error: failed to dial storage node (ID: 12VdhXf3NCUPaLUK9FxtF8xCc4dvSey79jCGwhveN4bLTxgrwjp) at address 86.201.25.141:28967: rpc: tls peer certificate verification error: not signed by any CA in the whitelist: CA cert\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:141\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”)

It looks like your identity hasn’t been signed/authorized. Have you followed those steps in the setup guide?

I just had the same Issue with that broken image, my existing Nodes are still running because of some caching:

2020-12-16T16:34:02.073Z	WARN	trust	Failed to fetch URLs from source; used cache	{"source": "https://tardigrade.io/trusted-satellites", "error": "HTTP source: Get \"https://tardigrade.io/trusted-satellites\": x509: certificate signed by unknown authority", "errorVerbose": "HTTP source: Get \"https://tardigrade.io/trusted-satellites\": x509: certificate signed by unknown authority\n\tstorj.io/storj/storagenode/trust.(*HTTPSource).FetchEntries:63\n\tstorj.io/storj/storagenode/trust.(*List).fetchEntries:90\n\tstorj.io/storj/storagenode/trust.(*List).FetchURLs:49\n\tstorj.io/storj/storagenode/trust.(*Pool).fetchURLs:240\n\tstorj.io/storj/storagenode/trust.(*Pool).Refresh:177\n\tstorj.io/storj/storagenode.(*Peer).Run:781\n\tmain.cmdRun:218\n\tstorj.io/private/process.cleanup.func1.4:362\n\tstorj.io/private/process.cleanup.func1:380\n\tgithub.com/spf13/cobra.(*Command).execute:842\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:950\n\tgithub.com/spf13/cobra.(*Command).Execute:887\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.ExecCustomDebug:70\n\tmain.main:385\n\truntime.main:204"}

A new Node is in a restart Loop. I think following URL is the fixed Image by @stefanbenten: https://hub.docker.com/layers/storjlabs/storagenode/latest/images/sha256-23e59f54f05cb898ed0f6f2cf8beea9f93fadb8bd6deb659dc289a57b96ea50b?context=explore

There you can see following Digest (for linux/arm64):

DIGEST:sha256:3ce5e5009e519ecc41aa5e9e901bebe11fcdff2d5099fd9750ac1deaefa72714

I have now testwise removed all my local images, and pulled that one especially by its digest.

arkina@helios64:~$ sudo docker pull storjlabs/storagenode@sha256:3ce5e5009e519ecc41aa5e9e901bebe11fcdff2d5099fd9750ac1deaefa72714
sha256:3ce5e5009e519ecc41aa5e9e901bebe11fcdff2d5099fd9750ac1deaefa72714: Pulling from storjlabs/storagenode
e92c575fea6b: Pull complete
fdbe0fb60210: Pull complete
a224a9e037fd: Pull complete
471c8fb23208: Pull complete
28c597448628: Pull complete
Digest: sha256:3ce5e5009e519ecc41aa5e9e901bebe11fcdff2d5099fd9750ac1deaefa72714
Status: Downloaded newer image for storjlabs/storagenode@sha256:3ce5e5009e519ecc41aa5e9e901bebe11fcdff2d5099fd9750ac1deaefa72714

Now we can see we have the correct digest:

arkina@helios64:~$ sudo docker images --digests storjlabs/storagenode
REPOSITORY              TAG                 DIGEST                                                                    IMAGE ID            CREATED             SIZE
storjlabs/storagenode   <none> sha256:3ce5e5009e519ecc41aa5e9e901bebe11fcdff2d5099fd9750ac1deaefa72714efb7528d1df3        10 days ago         29.5MB

Now when i do an usual Pull (like watchtower would do) i got another Digest:

arkina@helios64:~$ sudo docker pull storjlabs/storagenode:latest
latest: Pulling from storjlabs/storagenode
Digest: sha256:51e6a0e450c16120bb491b1e9a4adf0c2f370275b958a337b4f6392b9debbca8
Status: Downloaded newer image for storjlabs/storagenode:latest docker.io/storjlabs/storagenode:latest

And now we have to images with the same id, but different digests:

arkina@helios64:~$ sudo docker images --digests storjlabs/storagenode
REPOSITORY              TAG                 DIGEST                                                                    IMAGE ID            CREATED             SIZE
storjlabs/storagenode   latest              sha256:3ce5e5009e519ecc41aa5e9e901bebe11fcdff2d5099fd9750ac1deaefa72714   efb7528d1df3        10 days ago         29.5MB
storjlabs/storagenode   latest              sha256:51e6a0e450c16120bb491b1e9a4adf0c2f370275b958a337b4f6392b9debbca8   efb7528d1df3        10 days ago         29.5MB

On Dockerhub i wasn’t able to find an image with the Digest sha256:51e6a0e450c16120bb491b1e9a4adf0c2f370275b958a337b4f6392b9debbca8, but i bet thats the one which is broken. Question is now from where does it come? Also strange they have the same age even if on Dockerhub is is stated that sha256:3ce5e is 2 days newer than sha256:51e6a0e4.

I followed this guide : https://support.storj.io/hc/en-us/articles/360026612332-Install-storagenode-on-Raspberry-Pi3

Turned out I had completly forgotten to sign my identity! Thank you! Seems to be working now!
Although that still doesn’t explain why the 64bit image is broken.

Hi all,

I have the same problem with a new, fresh installation of a storage node.

Rock Pi 4, Ubuntu 20.04, 64Bit ARM.

Followed this instructions:
https://documentation.storj.io/setup/cli/storage-node

Paths to reproduce:

  1. Fresh install OS in Rock Pi.
  2. Run Get Docker script: https://get.docker.com/
  3. Ask for a new token by entering your email.
  4. Run the following commands:

identity create storagenode

identity authorize storagenode your_email:your_previously_obtained_token

docker pull storjlabs/storagenode:latest

docker run --rm -e SETUP=“true” --mount type=bind,source="/root/.local/share/storj/identity/storagenode/",destination=/app/identity --mount type=bind,source="/mnt/storagenode/",destination=/app/config \

docker run -d --restart unless-stopped --stop-timeout 300
-p 28967:28967
-p 192.168.0.xxx:14002:14002
-e WALLET=“0x***
-e EMAIL=“@.**"
-e ADDRESS="
.domain.net:28967”
-e STORAGE=“10TB”
–network host
–mount type=bind,source=”/root/.local/share/storj/identity/storagenode/",destination=/app/identity
–mount type=bind,source="/mnt/storagenode/",destination=/app/config
–name storagenode storjlabs/storagenode:latest

You are supposed yo get a running node after this, but logs says:

2020-12-17T04:18:18.323Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}
2020-12-17T04:18:18.329Z INFO Operator email {“Address”: “@."}
2020-12-17T04:18:18.329Z INFO Operator wallet {“Address”: "0x
”}
2020-12-17T04:18:18.805Z INFO Telemetry enabled {“instance ID”: “***”}
2020-12-17T04:18:18.911Z INFO db.migration Database Version {“version”: 46}
2020-12-17T04:18:20.714Z ERROR trust Failed to fetch URLs from source {“source”: “https://tardigrade.io/trusted-satellites”, “error”: “HTTP source: Get “https://tardigrade.io/trusted-satellites”: x509: certificate signed by unknown authority”, “errorVerbose”: “HTTP source: Get “https://tardigrade.io/trusted-satellites”: x509: certificate signed by unknown authority\n\tstorj.io/storj/storagenode/trust.(*HTTPSource).FetchEntries:63\n\tstorj.io/storj/storagenode/trust.(*List).fetchEntries:90\n\tstorj.io/storj/storagenode/trust.(*List).FetchURLs:49\n\tstorj.io/storj/storagenode/trust.(*Pool).fetchURLs:240\n\tstorj.io/storj/storagenode/trust.(*Pool).Refresh:177\n\tstorj.io/storj/storagenode.(*Peer).Run:781\n\tmain.cmdRun:218\n\tstorj.io/private/process.cleanup.func1.4:362\n\tstorj.io/private/process.cleanup.func1:380\n\tgithub.com/spf13/cobra.(*Command).execute:842\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:950\n\tgithub.com/spf13/cobra.(*Command).Execute:887\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.ExecCustomDebug:70\n\tmain.main:385\n\truntime.main:204”}

I signed the node certificate using identity for aarch64.

Use your Static IP or DDNS not your lan IP.

The 32bit image fixed this for me. The 64bit image is broken.

I will check the 64 bit image again later today.

How long did it take to create the identity? I should have taken a long time to create if you just used the little rock64. Did you verify that it was signed correctly?
https://documentation.storj.io/dependencies/identity#confirm-the-identity

I am running aarch64 with this digest on a rock64 with no issues. I can’t seem to find it on docker hub either, but this is the image that was pulled when watchtower upgraded the node. It has survived multiple restarts since installed. I am using Debian Stretch though, not a recent release.

Is it maybe still cached on your active node (as it is on mine)? See following message in the Log during Startup:

I just cannot start new nodes, old ones which were before the Update running still fine because of the caching.