Thanks that’s a good catch I actually had -e ADDRESS:28967=dns.ddns.net
I dont know why I copied wrong here in the blog
however I will keep trying and run the log as suggested
If you have a ARM64 device and 64 bit OS, then try this workaround:
However after the next version with fix would be published you will need to pull the right image with the latest tag and replace the image in the docker run command.
Please, show your full docker run command, you can remove any personal data.
Please use a new line with three backticks (```) before the command and the new line with three backticks after the command for the nice formatting.
Thanks Alexey - looks like that was the main problem
Right now the image is running but I got the following error: edu@edu-desktop:~$ sudo docker logs -t storagenode --tail 100 -f 2020-12-23T19:59:55.165509107Z 2020-12-23T19:59:55.165Z INFO Configuration loaded {"Location": "/app/config/config.yaml"} 2020-12-23T19:59:55.175724940Z 2020-12-23T19:59:55.168Z INFO Operator email {"Address": "eduardo.sequeira.hernandez@gmail.com"} 2020-12-23T19:59:55.175778958Z 2020-12-23T19:59:55.168Z INFO Operator wallet {"Address": "0xE26b4761DD50CfE22D8eF632bc229d17D09DF5B8"} 2020-12-23T19:59:55.809564097Z 2020-12-23T19:59:55.809Z INFO Telemetry enabled {"instance ID": "17rUiCzph4fnAGUWwCuUaidxU4o2xGBtnvTyWzwfEbSiQ3Wk8B"} 2020-12-23T19:59:55.869126464Z 2020-12-23T19:59:55.868Z INFO db.migration Database Version {"version": 46} 2020-12-23T19:59:56.872495556Z 2020-12-23T19:59:56.872Z INFO preflight:localtime start checking local system clock with trusted satellites' system clock. 2020-12-23T19:59:57.558364030Z 2020-12-23T19:59:57.557Z INFO preflight:localtime local system clock is in sync with trusted satellites' system clock. 2020-12-23T19:59:57.559114244Z 2020-12-23T19:59:57.558Z INFO bandwidth Performing bandwidth usage rollups 2020-12-23T19:59:57.559548980Z 2020-12-23T19:59:57.559Z INFO Node 17rUiCzph4fnAGUWwCuUaidxU4o2xGBtnvTyWzwfEbSiQ3Wk8B started 2020-12-23T19:59:57.559610627Z 2020-12-23T19:59:57.559Z INFO Public server started on [::]:28967 2020-12-23T19:59:57.559941698Z 2020-12-23T19:59:57.559Z INFO Private server started on 127.0.0.1:7778 2020-12-23T19:59:57.562292154Z 2020-12-23T19:59:57.558Z INFO trust Scheduling next refresh {"after": "5h22m48.494741911s"} 2020-12-23T20:00:17.750146882Z 2020-12-23T20:00:17.748Z ERROR contact:service ping satellite failed {"Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "attempts": 1, "error": "ping satellite error: failed to dial storage node (ID: 17rUiCzph4fnAGUWwCuUaidxU4o2xGBtnvTyWzwfEbSiQ3Wk8B) at address xxxxedu.ddns.net:28967: rpc: dial tcp 19x.16x.x.1x:28967: i/o timeout", "errorVerbose": "ping satellite error: failed to dial storage node (ID: 17rUiCzph4fnAGUWwCuUaidxU4o2xGBtnvTyWzwfEbSiQ3Wk8B) at address xxxedu.ddns.net:28967: rpc: dial tcp x.x.3x9.x:28967: i/o timeout\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"}
Your external address xxxxedu.ddns.net:28967 is not available from outside.
Make sure that you updated it to your actual public IP (replace to your actual address):
nslookup xxxxedu.ddns.net 8.8.8.8
The actual public IP you can see there: https://www.yougetsignal.com/tools/open-ports/
Also, make sure that WAN IP on the main page of your router is match that public IP, otherwise port forwarding will not work.
Hi Alexey - Thanks for your patience and all your tips.
I think that I found the solution my ip was fine but you are not going to believe it I don’t know why I didn’t start the NoIP Client. So I went back and launched and now I got this in the dashboard
I really hope everything is ok
Once again thank you very much.
Storage Node Dashboard ( Node Version: v1.18.1 )
======================
ID xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxQ3Wk8B Status ONLINE Uptime 18m12s
Available Used Egress Ingress
Bandwidth N/A 29.87 MB 0 B 29.87 MB (since Dec 1)
Disk 6.00 TB 26.25 MB