New GUI Node showing offline

Node Operators troubleshooting
1

I’m trying to get my node running using the windows GUI but it is showing offline and I can’t figure out where is problem. I got 2 nodes on docker, this is my first try with GUI. Port is visible, service is running and log shows nothing … any error…
can someone please look at log? thanks in advance

2020-02-16T21:04:12.623+0100 INFO Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml
2020-02-16T21:04:12.626+0100 DEBUG debug server listening on 127.0.0.1:55719
2020-02-16T21:04:12.647+0100 INFO Operator email: ahoj@outlook.com
2020-02-16T21:04:12.647+0100 INFO operator wallet: 0xFbxxxxxaddress
2020-02-16T21:04:12.674+0100 DEBUG Binary Version: v0.31.12 with CommitHash 8214de0e7ee6c55846e6f6a33e1309fc27c183c6, built at 2020-01-30 19:27:58 +0100 CET as Release true
2020-02-16T21:04:13.452+0100 DEBUG version allowed minimum version from control server is: v0.30.0
2020-02-16T21:04:13.452+0100 INFO version running on version v0.31.12
2020-02-16T21:04:13.452+0100 DEBUG telemetry Initialized batcher with id = “122DMs6Hg9jmHH9Xmy4dHEG9oMnpz73s7dJPi7wJzNxGBD389M5”
2020-02-16T21:04:13.474+0100 INFO db.migration Database Version {“version”: 31}
2020-02-16T21:04:14.332+0100 DEBUG trust Fetched URLs from source; updating cache {“source”: “https://tardigrade.io/trusted-satellites”, “count”: 5}
2020-02-16T21:04:14.340+0100 DEBUG trust Satellite is trusted {“id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”}
2020-02-16T21:04:14.340+0100 DEBUG trust Satellite is trusted {“id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2020-02-16T21:04:14.340+0100 DEBUG trust Satellite is trusted {“id”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”}
2020-02-16T21:04:14.340+0100 DEBUG trust Satellite is trusted {“id”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”}
2020-02-16T21:04:14.340+0100 DEBUG trust Satellite is trusted {“id”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”}
2020-02-16T21:04:14.340+0100 INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-02-16T21:04:15.195+0100 INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-02-16T21:04:15.196+0100 INFO bandwidth Performing bandwidth usage rollups
2020-02-16T21:04:15.196+0100 INFO trust Scheduling next refresh {“after”: “3h56m41.307798748s”}
2020-02-16T21:04:15.196+0100 INFO Node 122DMs6Hg9jmHH9Xmy4dHEG9oMnpz73s7dJPi7wJzNxGBD389M5 started
2020-02-16T21:04:15.196+0100 INFO Public server started on [::]:28968
2020-02-16T21:04:15.196+0100 INFO Private server started on 127.0.0.1:7778
2020-02-16T21:04:15.197+0100 DEBUG pieces:trash starting emptying trash
2020-02-16T21:04:15.208+0100 INFO piecestore:monitor Remaining Bandwidth {“bytes”: 100000000000000}
2020-02-16T21:04:15.208+0100 DEBUG contact:chore Starting cycle {“Satellite ID”: “118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW”}
2020-02-16T21:04:15.208+0100 DEBUG contact:chore Starting cycle {“Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”}
2020-02-16T21:04:15.208+0100 DEBUG contact:chore Starting cycle {“Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”}
2020-02-16T21:04:15.208+0100 DEBUG contact:chore Starting cycle {“Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”}
2020-02-16T21:04:15.208+0100 DEBUG contact:chore Starting cycle {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2020-02-16T21:04:15.326+0100 DEBUG version allowed minimum version from control server is: v0.30.0
2020-02-16T21:04:15.326+0100 INFO version running on version v0.31.12
2020-02-16T21:05:11.414+0100 DEBUG orders cleaning
2020-02-16T21:05:11.414+0100 DEBUG orders cleanup finished {“items deleted”: 0}
2020-02-16T21:09:01.297+0100 DEBUG orders sending
2020-02-16T21:09:01.299+0100 DEBUG orders no orders to send
2020-02-16T21:19:15.941+0100 DEBUG version allowed minimum version from control server is: v0.30.0
2020-02-16T21:19:15.941+0100 INFO version running on version v0.31.12

2

did you made port forwarding to your node port 28968?
Also on windows firewall?
and what brouser you use to see the dashboard?
what port using your docker nodes on this pc?

3

did you made port forwarding to your node port 28968? - yes port is mapped and visible
Also on windows firewall? - yes
and what brouser you use to see the dashboard? - chrome and edge showing same
what port using your docker nodes on this pc? - 28966, 28967

4

image
image1374×952 57.9 KB

5

do you use ddns or static ip?

6

tried with both, ddns and ip (dont’know if its really static but didn’t change few months)

7

your indentity has 6 files?

8

yes new one with six files

9

did you tried restart it?

10

computer not , storagenode few times

11

all the time log show the same?
other nodes on same pc? theres dashboard work ok? on this pc?

12

With the Windows GUI unlike docker when you change the external port from a default, and you have it occupied already, you must change the default listen port in the server.address: option of the "%ProgramFiles%\Storj\Storage Node\config.yaml".
Please, use the Notepad++ to edit it. Do not use a regular Notepad.
Save the configuration file and restart the storagenode service either from the Services applet or from the elevated Powershell:

Restart-Service storagenode
13

i did that, before dashboard didn’t show node id and version, now it’s changed and dashboard shows at least something

public address to listen on

server.address: :28968

14

You should change the dashboard port too in the console.address: (uncomment it by the way).

Make sure that you specified your external address with port in the contact.external-address:

15

got both

server address of the api gateway and frontend app

console.address: 127.0.0.1:14002

path to static resources

console.static-dir: “”

the public address of the node, useful for nodes behind NAT

contact.external-address: majkls33.ddns.net:28968

16

i will try to make new identity to be sure …

17

Not needed. Just make sure that no other storagenode is published the dashboard to the same port.

18

others are on 14001 and 14003

19

Please, add a firewall rule (elevated Powershell):

New-NetFirewallRule -DisplayName "Storj v3 - 3" -Direction Inbound –Protocol TCP –LocalPort 28968 -Action allow

Make sure that you do not have any outbound rules enabled.

20

didn’t help, tryied command and restarted node, and outbound rules are all allowed