Issues with Storj Node – Need to Retrieve Public IP and Network Information

Node Operators troubleshooting
, ,
1

Hi everyone,

I’m having some issues with my Storj node, and I’m not sure if it’s running on the correct network. Specifically, when I try to use the storj get-info command, I get the error “Couldn’t resolve host name”, and when trying to list buckets, I’m receiving a 403 error.

I’ve already switched the bridge URL to https://gateway.storjshare.io and set the corresponding environment variables, but the node seems to still be trying to connect to https://api.storj.io, which is confusing.

My main concern:

I would like to retrieve and confirm the public IP address that my Storj node is using. Since I’m not sure if the node is running in the correct network or if it is behind a firewall that could be blocking its communication, I need to verify the exact IP address and network details.

Specifically, I want to know:

  1. How can I retrieve the public IP address that Storj is using?
  2. What network information is Storj working with? For instance, which DNS server is it using, or how does it determine the public IP?
  3. If possible, how can I read this information directly from the Storj node** or the CLI tool itself? If there’s no direct way, I’m open to other suggestions for getting this data.

I also wonder if the issue could be related to a misconfiguration of my firewall or NAT. Should I ensure that certain ports (like 443) are open to allow the node to communicate with the bridge?

Otherwise the Node is running fine.

Any guidance or suggestions on how to resolve this would be greatly appreciated!

Thanks in advance,
Niroj

2

Are you running DDNS?

Are you using DuckDNS for DDNS?

Don’t use DuckDNS.

'nuff said.

3
  1. why would you retrieve something that you actively set by configuration.
  2. FWIR, Satellites run on Google, ergo likely google dns, do an nslookup on your octets/ddns 8.8.8.8, or any public sites like whatismyip.com.
  3. it’ll show in your logs, after configuration loaded start-up.

1 cent,
Julio

5

Hello @Niroj,
Welcome to the forum!

Seems you are from Storj V2 network? It was shutdown many years ago.

There is no such a command, or it’s useless. Storj V2 is no longer working.

Why did you so? Neither of them are needed to run a node. What’s specifically you did?

This is useless info. Your node is contacted by customers with generally random IP and random port. Of course, the satellites and gateways must be able to contact your node too, however, the source port will be random.

With what you have provided as a contact address of your node in the -e ADDRESS option.

Check your docker run command for the provided info in the contact address.

this port is not used, we also do not have bridges (they were in v2 of the network), now the closest analogue are satellites. However, their functioning is different.
You need to port forward the node’s port (28967 TCP+UDP by default).

This is not enough. Is it online on the dashboard http://localhost:14002? or if you call your external IP/hostname and the node’s port from your smartphone using the mobile internet?

I would suggest to remove the Storj V2 node, remove everything what you have configured and use this guide instead:

2 Likes