Problem docker config - no dashboard and not connect satelite

Node Operators troubleshooting
1

Hello
It opened udp/tcp port 7777 and udp/tcp 47000 on my router. But I have no connectivity to the satellites, he tells me that the waiting time has expired.
Am I missing a port to open?
It is installed in a docker in synology, with ext4 format the hard disk.

2023-01-31T09:44:40.228Z	ERROR	contact:service	ping satellite failed 	{"Process": "storagenode", "Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 8, "error": "ping satellite: rpc: tcp connector failed: rpc: dial tcp 34.XX.XXX.46:7777: connect: connection timed out", "errorVerbose": "ping satellite: rpc: tcp connector failed: rpc: dial tcp 34.XX.153.46:7777: connect: connection timed out\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189"}

this dashabord ip_synology:14002 not connect :frowning:

thank you
regards

2

hello what is your docker run command?

3

sudo docker run -d --restart unless-stopped --stop-timeout 300 -p 47000:47000/tcp -p 47000:47000/udp -p 127.0.0.1:14002:14002 -e WALLET=“0xe4XXXXX” -e EMAIL=“EMAIL@gmail.com” -e ADDRESS=“NAS.ddns.net:47000” -e STORAGE=“15TB” --user $(id -u):$(id -g) --mount type=bind,source=“/volume1/docker/storj/identity”,destination=/app/identity --mount type=bind,source=“/volume1/docker/storj/data”,destination=/app/config --name storagenode storjlabs/storagenode:latest

4

please check your DDNS record is mach your external ip in reality

5

image
image2218Ă—1144 112 KB

yes , and port enabled

6

Should not be
-p 47000:28967/tcp
-p 47000:28967/udp \

3 Likes
7

2023-01-31T11:45:25.412Z ERROR preflight:localtime unable to get satellite system time {“Process”: “storagenode”, “Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “error”: “rpc: tcp connector failed: rpc: dial tcp 35.228.31.57:7777: connect: connection timed out”, “errorVerbose”: “rpc: tcp connector failed: rpc: dial tcp 35.228.31.57:7777: connect: connection timed out\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:189”}

8

2023-01-31T11:43:17.195Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet-features”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “contact.external-address”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.private-address”}

2023-01-31T11:43:17.195Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.email”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.address”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.enabled”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-disk-space”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-bandwidth”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “console.address”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “healthcheck.details”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.caller”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.development”}
2023-01-31T11:43:17.195Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.output”}

I get all these info, but I don’t know why.
The wallet is from crypto.com

9

I think the docker command is wrong. Of course it should be

-p 47000:28967/tcp
-p 47000:28967/udp \

1 Like
10

@roberwii there’s a few things wrong…

Don’t do this. Close this port.

Are you wanting this to be your main port? Normally it’s 28967, and that should be the only port open in the router. If you want 47000 instead then that’s fine but you should use the docker settings from @Roberto.

These are all fine as they refer to the storagenode-updater. You can ignore.

1 Like
11

close port 7777 udp/tcp

image
image1858Ă—1152 190 KB

use new config

sudo docker run -d --restart unless-stopped --stop-timeout 300 -p 47000: 28967/tcp -p 47000: 28967/udp -p 127.0.0.1:14002:14002 -e WALLET=“0xe4XXXXX” -e EMAIL=“EMAIL@gmail.com” -e ADDRESS=“NAS.ddns.net:47000" -e STORAGE=“15TB” --user $(id -u):$(id -g) --mount type=bind,source=“/volume1/docker/storj/identity”,destination=/app/identity --mount type=bind,source=“/volume1/docker/storj/data”,destination=/app/config --name storagenode storjlabs/storagenode:latest

12

You should forward only 47000 tcp+udp to your host with the node. Please do not publish your dashboard (14002) with all your private information to the internet without protection, use How to remote access the web dashboard - Storj Node Operator Docs or [Tech Preview] Multinode Dashboard Binaries instead.

Does it show as online?

13

now work but not access dashboard

image
image1884Ă—1136 218 KB

14

image
image2052Ă—1234 122 KB

port 14002

15

config node

image
image1058Ă—1192 109 KB

16

… -p 0.0.0.0:14002:14002 …

And close port 14002 in your router as Alexey said. It’s not required to show the dashboard in your LAN

1 Like
17

I have closed port 14002, but how do I modify to see the dashboard locally?

18

image
image2452Ă—272 92.5 KB

127.0.0.1:14002 → not work
“Containers”: {
“XXX”: {
“Name”: “storagenode”,
“EndpointID”: “XXXXX”,
“MacAddress”: “XXXX”,
“IPv4Address”: “172.17.0.2/16”, → 172.17.0.2:14002 not work
“IPv6Address”: “”
}
},

19

stop and remove the container

docker stop -t 300 storagenode
docker rm storagenode

Then change the part with the port 14002 in your docker run command as I wrote in my last post. You can omit the 0.0.0.0 as this is the default when no IP is specified.

-p 127.0.0.1:14002:14002

becomes

-p 14002:14002
1 Like
20

now work :slight_smile: fantastic!! thanks!!

2 Likes