Storagenode is running on PI and it's offline

Hi There,

I have a PI4 and it’s running storagenode 1.9.4. At bootup it’s offline. I am trying to run IPv6*. How can I get my node online?

Runcommand:

sudo docker run -d --restart unless-stopped --stop-timeout 300 \
    -p 28967:28967 \
    -p 127.0.0.1:14002:14002 \
    -e WALLET="000000000000000000000000000000000000x" \
    -e EMAIL="email@email.email" \
    -e ADDRESS="[XXXX:XXXX:XXXX:XXX:XXX:XXXX:XXXX:XXX]:28967" \
    -e STORAGE="10 TB" \
    --mount type=bind,source="/home/jwolf/storj-identity",destination=/app/identity \
    --mount type=bind,source="/mnt/storj",destination=/app/config \
    --name storagenode storjlabs/storagenode:beta

Logs

2020-08-06T08:43:24.886Z INFO Configuration loaded {"Location": "/app/config/config.yaml"}

2020-08-06T08:43:24.890Z INFO Operator email {"Address": "email@email.email"}

2020-08-06T08:43:24.890Z INFO Operator wallet {"Address": "0xCENSOR"}

2020-08-06T08:43:37.152Z INFO Telemetry enabled

2020-08-06T08:43:37.183Z INFO db.migration Database Version {"version": 43}

2020-08-06T08:43:37.915Z INFO preflight:localtime start checking local system clock with trusted satellites' system clock.

2020-08-06T08:43:39.119Z INFO preflight:localtime local system clock is in sync with trusted satellites' system clock.

2020-08-06T08:43:39.120Z INFO Node 12okQEEY8PyyPJbGoku6uBqVyAy5qwvqnt5fSvbiepqLLEH7eRw started

**2020-08-06T08:43:39.120Z INFO Public server started on [::]:28967**

2020-08-06T08:43:39.121Z INFO Private server started on 127.0.0.1:7778

2020-08-06T08:43:39.121Z INFO trust Scheduling next refresh {"after": "8h0m27.239961328s"}

2020-08-06T08:43:39.123Z INFO bandwidth Performing bandwidth usage rollups

Note that in the logs no public server is started (or atleast the IPv6 seems empty)…

*Unfortunately my ISP ran out of IPv4 adresses and therefore I only have a ipv6 which is available. I am trying to get a unique public IPv4 but it’s currently shared by multiple household routers

Only one of the 6 satellites currently supports IPv6 at all. And that satellite is almost entirely idle. I think it’s time to switch ISPs. Either that or contact them to ask for a public IP. You don’t need a static IP (they usually charge more for that) just a public one. Don’t bother explaining storj to them, just tell them you need to access your IP camera. That makes the conversation a lot simpler.

1 Like

Is there a timeline for IPv6 support on Storj?
It’s the future, after all (supposedly).

For now IPv4 isn’t going anywhere. For Storj it’s primarily because GCP doesn’t support IPv6 and the satellites run on that. So I guess it’s not entirely up to Storj (unless of course they move their satellite infra). But I don’t expect it would be high on the priority list.

Unfortunately my ISP (openfiber) does not seem to hurry up to put this change through. For now; can anyone answer to this: Is the ipv6 the actual reason my node is not online or is it something else? Can I give you people some logs?

It’s likely that your node is not displaying online because it’s only IPv6 and the satellites don’t know about your node because they are busily working on IPv4.

You indicated that you have a shared IPv4 address. So, one possible solution would be to purchase a small IaaS and setup a reverse ssh tunnel from that external and static (probably) IPv4 server to your storage node.

No reputable ISP is going to close port 22… so as long as the IaaS is less expensive than an average month’s earnings And has at least 2 TB of included bandwidth, you’ll probably still make a few dollars a month… but the budget will be close.

The other alternative is to use a VPN with port forwarding option such as portmap.io, ngrok, PIA, PureVPN

Thank you for all the answers. I asked my ip and I received an ipv4. When do you plan to support Ipv6?

Hopefully they don’t put you behind a CGNAT… if so, you’d be in a similar position.

I am online now. Zero bytes transferred yet. I hope I did not suffer too much reputation loss from this. 10TB potential storage is added to the network with 1000MB up/down

2 Likes