Docker again failed rcp

Hi,

i have again problem with my docker.

Private server started on 127.0.0.1:7778        {"Process": "storagenode"}
2022-06-09T20:21:28.969Z        INFO    failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.     {"Process": "storagenode"}
2022-06-09T20:21:34.043Z        WARN    contact:service failed PingMe request to satellite      {"Process": "storagenode", "Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "error": "ping satellite: check-in network: failed to ping node (ID: 12g8oi2ZyLUyP9jcrGH7KN6bKZ1nEUSLRx9AiXsokxwNTbgabbu) at address: xxxx:28970, err: contact: failed to dial storage node (ID: 12g8oi2ZyLUyP9jcrGH7KN6bKZ1nEUSLRx9AiXsokxwNTbgabbu) at address xxxx:28970 using QUIC: rpc: quic: timeout: no recent network activity", "errorVerbose": "ping satellite: check-in network: failed to ping node (ID: 12g8oi2ZyLUyP9jcrGH7KN6bKZ1nEUSLRx9AiXsokxwNTbgabbu) at address: xxxx:28970, err: contact: failed to dial storage node (ID: 12g8oi2ZyLUyP9jcrGH7KN6bKZ1nEUSLRx9AiXsokxwNTbgabbu) at address xxxx:28970 using QUIC: rpc: quic: timeout: no recent network activity\n\tstorj.io/storj/storagenode/contact.(*Service).requestPingMeOnce:194\n\tstorj.io/storj/storagenode/contact.(*Service).RequestPingMeQUIC:167\n\tstorj.io/storj/storagenode.(*Peer).addConsoleService:845\n\tstorj.io/storj/storagenode.(*Peer).Run:884\n\tmain.cmdRun:251\n\tstorj.io/private/process.cleanup.func1.4:372\n\tstorj.io/private/process.cleanup.func1:390\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfigAndLogger:93\n\tmain.main:479\n\truntime.main:255"}
2022-06-09T20:21:39.444Z        WARN    contact:service failed PingMe request to satellite      {"Process": "storagenode", "Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "error": "ping satellite: check-in network: failed to ping node (ID: 12g8oi2ZyLUyP9jcrGH7KN6bKZ1nEUSLRx9AiXsokxwNTbgabbu) at address: xxxx:28970, err: contact: failed to dial storage node (ID: 12g8oi2ZyLUyP9jcrGH7KN6bKZ1nEUSLRx9AiXsokxwNTbgabbu) at address xxxx:28970 using QUIC: rpc: quic: timeout: no recent network activity", "errorVerbose": "ping satellite: check-in network: failed to ping node (ID: 12g8oi2ZyLUyP9jcrGH7KN6bKZ1nEUSLRx9AiXsokxwNTbgabbu) at address: xxx:28970, err: contact: failed to dial storage node (ID: 12g8oi2ZyLUyP9jcrGH7KN6bKZ1nEUSLRx9AiXsokxwNTbgabbu) at address xxx:28970 using QUIC: rpc: quic: timeout: no recent network activity\n\tstorj.io/storj/storagenode/contact.(*Service).requestPingMeOnce:194\n\tstorj.io/storj/storagenode/contact.(*Service).RequestPingMeQUIC:167\n\tstorj.io/storj/storagenode.(*Peer).addConsoleService:845\n\tstorj.io/storj/storagenode.(*Peer).Run:884\n\tmain.cmdRun:251\n\tstorj.io/private/process.cleanup.func1.4:372\n\tstorj.io/private/process.cleanup.func1:390\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfigAndLogger:93\n\tmain.main:479\n\truntime.main:255"}

and i have ports open


docker-pr 10954            root    4u  IPv4  91170      0t0  TCP *:28970 (LISTEN)
docker-pr 10961            root    4u  IPv6  90225      0t0  TCP *:28970 (LISTEN)

my config

	sudo docker run -d --restart unless-stopped --stop-timeout 300 \
    -p 28970:28967/tcp \
    -p 28970:28967/udp \
    -p 14004:14002 \
    -e WALLET="0x7xxx" \
    -e EMAIL="xxx" \
    -e ADDRESS="nxxx:28970" \
    -e STORAGE="xxx" \
    --user $(id -u):$(id -g) \
    --mount type=bind,source="/root/.local/share/storj/identity/nodo2/",destination=/app/identity \
    --mount type=bind,source="/home/nodo2/",destination=/app/config \
    --name nodo2 storjlabs/storagenode:latest

my nc

nc -vz xxxx 28970
Connection to xxxx (xxxx) 28970 port [tcp/*] succeeded!

iptable -L

iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy DROP)
target     prot opt source               destination
DOCKER-USER  all  --  anywhere             anywhere
DOCKER-ISOLATION-STAGE-1  all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain DOCKER (1 references)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             172.17.0.2           tcp dpt:28967
ACCEPT     udp  --  anywhere             172.17.0.2           udp dpt:28967
ACCEPT     tcp  --  anywhere             172.17.0.2           tcp dpt:14002
ACCEPT     tcp  --  anywhere             172.17.0.3           tcp dpt:28967
ACCEPT     udp  --  anywhere             172.17.0.3           udp dpt:28967
ACCEPT     tcp  --  anywhere             172.17.0.3           tcp dpt:14002

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target     prot opt source               destination
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere

Chain DOCKER-ISOLATION-STAGE-2 (1 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere
RETURN     all  --  anywhere             anywhere

Chain DOCKER-USER (1 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

i dont know all it ok…

Is your node actually offline on the dashboard?
The referred error related to QUIC UDP, not TCP. Please make sure that you forwarded UDP port 28967 on your router too.
See QUIC requirements | Storj Docs
Please also check your DDNS address (replace nxxx to your actual address)

nslookup nxxx 8.8.8.8

It should return the same IP as WAN IP on your router and as IP from Open Port Check Tool - Test Port Forwarding on Your Router

Hi Alexey

Yes is offline on dashboard. The check it ok, quic in my command run docker and ports it open.

nslookup xxxx 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   xxxx
Address: 51xxx

If it’s offline on the dashboard, then make sure that your WAN IP on your router matches IP on yougetsignal and matches IP, resolved from your DDNS hostname.
If they do not match - the node will be offline.
Please also make sure that the local IP of your device where is storagenode running is the same as in your port forwarding rule, if it changed - you need to update the rule.

1 Like