I had some time today and I’ve done some more investigation. I’ve exposed the 14002 port number to the outside world and it is working, I’m able to reach my dashboard from outside. And also checked the status of the port using an online port-checker, and everything is fine for 14002.
As the 14002 port number is working I can’t see any reason for ISP to block the 28967 port. I thought maybe it is because my raspberry-pi-4(64Bit) blocks some of the outgoing ports. To verify that I’ve compared the iptables outputs of my working node (static-ip, raspberry pi-3, different location) and the problematic node (DDNS, raspberrypi4 64Bit).
iptables output for my working node:
Chain DOCKER (1 references)
pkts bytes target prot opt in out source destination
199K 11M ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.3 tcp dpt:28967
1386 1774K ACCEPT udp -- !docker0 docker0 0.0.0.0/0 172.17.0.3 udp dpt:28967
29 1548 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.3 tcp dpt:14002
iptables output for my problematic node:
Chain DOCKER (1 references)
pkts bytes target prot opt in out source destination
72 4320 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.3 tcp dpt:28967
0 0 ACCEPT udp -- !docker0 docker0 0.0.0.0/0 172.17.0.3 udp dpt:28967
6 352 ACCEPT tcp -- !docker0 docker0 0.0.0.0/0 172.17.0.3 tcp dpt:14002
As you can see in the second iptables output 28967/UDP has 0 bytes. But I don’t see any restriction on the outgoing direction when I look whole output.
May I get disqualified? I saw the @BrightSilence’s comment here. And executed the below command to check the identity.
docker exec -it storagenode ls -l /app/identity
total 24
-rw-r--r-- 1 1000 1000 558 Jan 14 19:10 ca.1673723418.cert
-rw-r--r-- 1 1000 1000 1088 Jan 14 19:10 ca.cert
-rw------- 1 1000 1000 241 Jan 14 06:40 ca.key
-rw-r--r-- 1 1000 1000 1100 Jan 14 19:10 identity.1673723418.cert
-rw-r--r-- 1 1000 1000 1630 Jan 14 19:10 identity.cert
-rw------- 1 1000 1000 241 Jan 14 06:40 identity.key
Looks like there is no issue regarding identity. Shall I reconfigure my node from the beginning by generating a new token?
I’m still waiting for a response from ISP probably they’ll call me tomorrow but I’m feeling that the problem is not on their end.
Lastly, I’ve tried to change the port numbers with each other in my run command to be sure that the problem is not because of the ISP as below:
docker run -d --restart unless-stopped --stop-timeout 300 \
-p 14002:14002/tcp \
-p 14002:14002/udp \
-p 28967:28967\
-e WALLET="??????" \
-e EMAIL="abcdefg@gmail.com" \
-e ADDRESS="MY_DDNS:14002" \
-e STORAGE="748GB" \
--user $(id -u):$(id -g) \
--mount type=bind,source="/home/heraclitus/.local/share/storj/identity/storagenode",destination=/app/id>
--mount type=bind,source="/storj-storage1/storagenode",destination=/app/config \
--name storagenode storjlabs/storagenode:latest
Unfortunately, that trick did not work, I was able to connect to my dashboard through MY_DDNS:14002 link. My expectation was to reach my dashboard through MY_DDNS:28967 link, but weirdly it did not work.