After pc restart the node is offline i dont know what to do.
The port in https://www.yougetsignal.com/tools/open-ports/ is open
WAN IP of router is the same as IP from port forwarding page tester page
Port forward is set up correctly
but is still offline
Compare the IP from the nslookup mwstorjnode.ddns.net 8.8.8.8
with IP on yougetsignal
Please, copy the output of the command sudo ufw status
So I set up a new node, external HDD, Windows host. Everything seems fine, but the dashboard shows the node is offline. It does show the “neighborhood” at about 400, and shows the bootstrap address, so I assume everything is connected to the internet, but I suspect something on the internet can’t contact my node first, without the node sending a connection out first. Anyways, when I first set it up it was 1:00 am so I thought “maybe it needs some time to get started”, but it’s been over a day now, so I feel it should be working if it’s going to work.
I guess I need some directions regarding troubleshooting.
I did forward the port 28967 on my router and opened it in the Windows firewall.
There weren’t any immediate errors given when I launched Docker or the container, but I didn’t look at any actual logs.
Thought I’d add the node ID.
12HgxBftAhJFNFrBWJ78mnUtboTfr5dwGN5ohXGWNGaw5PhMDi8
In case that helps with diagnosing connections. That’s according to the dashboard.
Hmm this sounds like it might be a port issue, can you post your logs?
docker logs --tail 10 storagenode
Not sure it’ll be useful, but…
2019-08-27T01:27:15.457Z INFO version running on version v0.17.0
2019-08-27T01:42:14.990Z INFO bandwidth Performing bandwidth usage rollups
2019-08-27T01:42:15.375Z INFO version running on version v0.17.0
2019-08-27T01:57:15.348Z INFO version running on version v0.17.0
2019-08-27T02:12:15.293Z INFO version running on version v0.17.0
2019-08-27T02:27:15.286Z INFO version running on version v0.17.0
2019-08-27T02:42:14.990Z INFO bandwidth Performing bandwidth usage rollups
2019-08-27T02:42:15.317Z INFO version running on version v0.17.0
2019-08-27T02:57:15.442Z INFO version running on version v0.17.0
2019-08-27T03:12:15.306Z INFO version running on version v0.17.0
Here’s the output immediately after restarting the container.
2019-08-27T03:25:56.944Z INFO Private server started on 127.0.0.1:7778
2019-08-27T03:25:56.944Z INFO vouchers Requesting voucher {"satellite": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S"}
2019-08-27T03:25:56.944Z INFO vouchers Requesting voucher {"satellite": "118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW"}
2019-08-27T03:25:56.944Z INFO vouchers Requesting voucher {"satellite": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6"}
2019-08-27T03:25:56.950Z INFO piecestore:monitor Remaining Bandwidth {"bytes": 16000000000000}
2019-08-27T03:25:56.996Z INFO version running on version v0.17.0
2019-08-27T03:25:58.026Z INFO vouchers Voucher request denied. Vetting process not yet complete
2019-08-27T03:25:58.211Z INFO vouchers Voucher request denied. Vetting process not yet complete
2019-08-27T03:25:58.278Z INFO vouchers Voucher request denied. Vetting process not yet complete
2019-08-27T03:25:58.443Z INFO vouchers Voucher request denied. Vetting process not yet complete
Try the suggestions I listed here
Well, seeing that the port was indeed not open made me check a few things. Turned out my port settings had the wrong local IP address. Oh well. I feel like I totally checked that. Anyways, all seems good now. Dumb mistake. Thanks for the help!
My node stays OFFLINE. I tried to restart it and to disable firewall but nothing.
Dashboard stops after few seconds.
Here is my dashboard:
Please check your port forwarding rule on your router, it should forward TCP port 28967 to your PC with Docker. Make sure that the IP in the port forwarding rule is the same as the IP of your PC.
Check that your external address on https://www.yougetsignal.com/tools/open-ports/ matches the WAN IP on your router, otherwise your port forwarding rule will not work.
Please also make sure that your ADDRESS option in the docker run
command includes the port, for example:
-e ADDRESS=external.address.tld:28967
If your public IP is not static, then you should register your own DDNS domain, for example on noip.com, and then use this domain as your external address. You also need to configure the updating of this domain with an actual public IP on your router (it’s usually configured in the DDNS section of your router settings) or with a special application from the DDNS provider. For NoIP this application is called DUC. Make sure to use only one of those methods - either directly in the router configuration, or with the DUC application (or equivalent application if you use a different DDNS service than NoIP).
If you have a firewall, make an inbound rule to allow any traffic from any source and TCP 28967 port and your PC/NAS as a destination. If you have any outbound restricted rule, then make an outbound rule for any traffic from any port of your PC as a source and any host with any port as a destination.
to me? I don’t have a problem I was just directing the OP to a very similar thread…
ok then never mind and thanks
2 posts were merged into an existing topic: Restart loop because of “Fatal error: piecestore monitor: disk space requirement not met”
A post was merged into an existing topic: Restart loop because of “Fatal error: piecestore monitor: disk space requirement not met”
Hi all,
I just set up a node for the 1st time on Raspberry Pi. It starts correctly but stays Offline and also doesn’t see any neighbours. There seems to be a bootstrap issue as far as I can read from the logs.
Any help is appreciated,
Thanks Wunderbaer