My node is offline after changing the Payment address in the configuration.
I am running a Linux CentOS 7 machine with multiple nodes, and one of them did not come online after the change.
It is not the firewall or port forwarding, as I exchanged the ports of two nodes, and still only the same node has issues (same node under a different port)
In the logs there is no error but the dashboards shows OFFLINE.
$ sudo docker logs storj_kappa
2020-01-19T13:46:56.982Z INFO Configuration loaded from: /app/config/config.yaml
2020-01-19T13:46:57.006Z INFO Operator email: EMAIL_REDACTED
2020-01-19T13:46:57.007Z INFO operator wallet: ADDRESS_REDACTED
2020-01-19T13:46:57.465Z INFO version running on version v0.29.3
2020-01-19T13:46:57.474Z INFO db.migration Database Version {"version": 28}
2020-01-19T13:46:57.937Z INFO Node 12idSMzaHLhRQmUB7kk5GeRBAof6qsQpYCa2nYR7DCk9up5Q67V started
2020-01-19T13:46:57.937Z INFO Public server started on [::]:28968
2020-01-19T13:46:57.937Z INFO Private server started on 127.0.0.1:7778
2020-01-19T13:46:57.937Z INFO bandwidth Performing bandwidth usage rollups
2020-01-19T13:46:57.937Z INFO trust Scheduling next refresh {"after": "4h44m48.181862607s"}
2020-01-19T13:46:58.004Z INFO piecestore:monitor Remaining Bandwidth {"bytes": 998185035401728}
2020-01-19T13:46:58.042Z INFO version running on version v0.29.3
2020-01-19T14:01:58.368Z INFO version running on version v0.29.3
2020-01-19T14:16:58.365Z INFO version running on version v0.29.3
2020-01-19T14:31:58.369Z INFO version running on version v0.29.3
The IP should be the same as your public and WAN IPs.
Also, please, make sure that the local IP of your PC is the same as used in your port forwarding rule. It could change during reboot of PC or your router.
Thank you for your message! I have checked this rigorously, local and remote ip’s are the same. I confirmed that it has nothing to do with the port forwarding nor firewall, but exchanging the port of two of the nodes on the same machine.
But now it seems that even though I specify port 28969 in my config (just confirmed this), it is still looking for port 28968 as shown in the logs…
Apparently I am on my reply limit for my user on this forum… So I will have to update this post:
Stopped and removed the storj_kappa node, and created a new node: storj_kappa3, with the config above (port 28969!). But it still says listening on 28968…
$ sudo docker logs storj_kappa3
2020-01-19T14:52:32.642Z INFO Configuration loaded from: /app/config/config.yaml
2020-01-19T14:52:32.665Z INFO Operator email: REDACTED
2020-01-19T14:52:32.665Z INFO operator wallet: REDACTED
2020-01-19T14:52:33.148Z INFO version running on version v0.29.3
2020-01-19T14:52:33.158Z INFO db.migration Database Version {"version": 28}
2020-01-19T14:52:33.631Z INFO trust Scheduling next refresh {"after": "6h15m26.223642696s"}
2020-01-19T14:52:33.631Z INFO bandwidth Performing bandwidth usage rollups
2020-01-19T14:52:33.631Z INFO Node 12idSMzaHLhRQmUB7kk5GeRBAof6qsQpYCa2nYR7DCk9up5Q67V started
2020-01-19T14:52:33.631Z INFO Public server started on [::]:28968
2020-01-19T14:52:33.631Z INFO Private server started on 127.0.0.1:7778
2020-01-19T14:52:33.693Z INFO piecestore:monitor Remaining Bandwidth {"bytes": 998185035401728}
2020-01-19T14:52:33.739Z INFO version running on version v0.29.3
Removing the config.yaml and restarting the node did the trick! Thank you @Alexey !
had the exact same problem today on my raspberry pi 3…I have checked IPs, renamed container, removed config.yaml and only after a few restarts and some downtime it finally went back online…maybe something happened on Storj today? who knows, glat it’s back online!
Offline can be only if your identity is not signed, or your network does not configured properly: doesn’t updated DDNS, changed public IP (and you did not use the DDNS), your local IP is changed, you forwarded a wrong port, your ISP placed you behind their NAT.