New Silo Node Still Offline

Announcements
1

I like to get my Node online but keep this error:

2026-05-13T20:20:38Z ERROR contact:service ping orbital failed {“process”: “storagenode”, “orbital_id”: “1dkRxqhU46NfjV1xJZrxnt8RwWGK2uAas1jtncvZoj4s8HVVK4”, “attempts”: 8, “error”: “ping orbital: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: not signed by any CA in the whitelist: CA cert”, “errorVerbose”: “ping orbital: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: tls peer certificate verification: not signed by any CA in the whitelist: CA cert\n\tsilos3.com/silo/storagenode/contact.(*Service).pingOrbitalOnce:232\n\tsilos3.com/silo/storagenode/contact.(*Service).pingOrbital:169\n\tsilos3.com/silo/storagenode/contact.(*Chore).updateCycles.func1:89\n\tsilos3.com/common/sync2.(*Cycle).Run:102\n\tsilos3.com/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:93”}

Adres is DDNS
Ports open > YES
Wallet Connect > YES
20K coins staked > YES

2

What you running it on ? Windows amdx64 ?

3

Screenshot your docker setup, hide wallet address and email

4

docker run -d --restart unless-stopped --stop-timeout 300 -p 28967:28967/tcp -p 28967:28967/udp -p 127.0.0.1:14002:14002 -e WALLET=“0x84a4A71AC285e17301A783CF9E454A5f0fxxxxxx” -e EMAIL=“[email protected]” -e ADDRESS=“xxxx.synology.me:28967” -e STORAGE=“6TB” --mount type=bind,source=“C:\Silo\Trustkey\silonode”,destination=/app/trustkey --mount type=bind,source="D:",destination=/app/config --name storagenode silos3/silo-node:latest

5

image
image3424×777 102 KB

Yes on Windows 11 Pro

6

Are your 3 keys and 3 certs in C:\Silo\Trustkey\silonode ? Does silonode need a capital S ? Is there a file in Silonode called Storagenode with keys in ? So dir would be C:\Silo\Trustkey\silonode\storagenode ?

7

Maybe try with just your public ip:28967 not your ddns

8

The path is correct and I see 2x ca and 2x trustkey files. Not 3 as you state, is 3 needed?

There are in folder silonode

I did use my IP but was told at this forum to use DDNS instead. But both are not the solution.

9

Should have 6 after successful authorisation token generation 2 new ones with numbers like 654356.cert 644356.key. check appdata/roaming/silo . i’m away at mo so can’t check exactly. Maybe use original folder for dir if 6 in

10

Defo using public ip yer, easiest way i check it i run ookla speedtest and it shows your current public ip to bottom left of go circle

11

I did setup all new and then I get 4 files and remove the CA file to safe locations. So then there are 3 files left. But I have to replace those whit my original ones to get my 20k staking Node active. Port open, different (original) keys folder, the page shows node but still ofline.

12

After you generate the 4 tokens you need to do the token authorisation bit which gives the extra 2 files. Use your email and numbers they give you

13

Signup | SILO - Decentralized Storage Solutions put in your email, scroll down if you can’t see box then submit, then copy all they generate youremail:theirnumbers.. use link in blue above

14

Then put this in powershell no quotes "./trustkey.exe authorize silonode " add your email:keysnumbers at end :crossed_fingers::+1:

15

I did do all above steps several times and as my screenshot did show the Node is build, only it is ofline. But I never got more than 4 files in same folder.

16

Check the original folder they put them in. Add your node key last before starting node

17

Original folder has 4 files also. This is madness to setup.

1 Like