Problem after migration from Windows to Linux

Node Operators troubleshooting
1

Hi,
After starting Docker, the port remains closed.
All data has been synchronized according to the instructions.
The log file is shown below..

Thank you in advance

2025-09-16T17:46:54Z INFO lazyfilewalker.used-space-filewalker.subprocess Database started {“Process”: “storagenode”, “satelliteID”: “12EayRS2V1genode”}
2025-09-16T17:46:54Z INFO lazyfilewalker.used-space-filewalker subprocess finished successfully {“Process”: “storagenode”, “satelliteID”: "12
2025-09-16T17:46:54Z INFO pieces used-space-filewalker completed {“Process”: “storagenode”, “Satellite ID”: "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZ70590438640, “Total Pieces Content Size”: 370007566064, “Total Pieces Count”: 1138423, “Duration”: “141.307882ms”}
2025-09-16T17:48:18Z INFO reputation:service node scores updated {“Process”: “storagenode”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtm”: 11260, “Audit Score”: 1, “Online Score”: 0.9310148770075242, “Suspension Score”: 1, “Audit Score Delta”: 0, “Online Score Delta”: 0, "Suspension Score Del
2025-09-16T17:48:18Z INFO reputation:service node scores updated {“Process”: “storagenode”, “Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWs”: 39239, “Audit Score”: 1, “Online Score”: 0.9562535854986239, “Suspension Score”: 1, “Audit Score Delta”: 0, “Online Score Delta”: 0, "Suspension Score De
2025-09-16T17:48:19Z INFO reputation:service node scores updated {“Process”: “storagenode”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicss”: 54675, “Audit Score”: 1, “Online Score”: 0.928658530408461, “Suspension Score”: 1, “Audit Score Delta”: 0, “Online Score Delta”: 0, "Suspension Score Del
2025-09-16T17:48:19Z INFO reputation:service node scores updated {“Process”: “storagenode”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbs”: 55361, “Audit Score”: 1, “Online Score”: 0.9012277263926229, “Suspension Score”: 1, “Audit Score Delta”: 0, “Online Score Delta”: 0, "Suspension Score De
2025-09-16T17:49:06Z ERROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZto ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.131.248.101:28974: connect: connection timed out”, “erro node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.131.248.101:28974: connect: connection timed out\n\tstorj.io/storj/storagenode/congenode/contact.(*Service).pingSatellite:169\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\x/sync/errgroup.(*Group).add.func1:130”}
2025-09-16T17:49:07Z ERROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmto ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.131.248.101:28974: connect: connection timed out”, “erro node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.131.248.101:28974: connect: connection timed out\n\tstorj.io/storj/storagenode/congenode/contact.(*Service).pingSatellite:169\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\x/sync/errgroup.(*Group).add.func1:130”}
2025-09-16T17:49:08Z ERROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tto ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.131.248.101:28974: connect: connection timed out”, “erro node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.131.248.101:28974: connect: connection timed out\n\tstorj.io/storj/storagenode/congenode/contact.(*Service).pingSatellite:169\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\x/sync/errgroup.(*Group).add.func1:130”}
2025-09-16T17:49:09Z ERROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcso ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.131.248.101:28974: connect: connection timed out”, “errornode indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.131.248.101:28974: connect: connection timed out\n\tstorj.io/storj/storagenode/contenode/contact.(*Service).pingSatellite:169\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\t/sync/errgroup.(*Group).add.func1:130”}

2

May be port forward changed as your internal ip of linux pc is other?
is it your only node?

1 Like
3

Share your docker command please.

1 Like
4

Port forwarding is fine.

Docker command without private stuff:
docker run -d --restart unless-stopped --stop-timeout 300
-p 28974:28967/tcp
-p 28974:28967/udp
-p 14008:14002
-e WALLET=“wallet”
-e EMAIL="mail@gmail.com"
-e ADDRESS=“domain:28974”
-e STORAGE=“3.5TB”
–user $(id -u):$(id -g)
–mount type=bind,source=“/mnt/storj/storagenode/identity”,destination=/app/identity
–mount type=bind,source=“/mnt/storj/storagenode”,destination=/app/config
–log-opt max-size=512m
–log-opt max-file=3
–name storagenode storjlabs/storagenode:latest

5

Basic things comming to my mind to check (sorry if you already did so):

  • firewall rules for TCP and UDP on the router?
  • port forwarding/dst-nat/whatever-is-thename on the router. Correct (most probably changed) address in the local network for both TCP and UDP?
  • firewall rules on your linux machine?
  • Are you able to connect to http://your_linux_machine:14008 (from machine in your local network, but not linux machine itself)?
  • telnet -4 your_linux_machine 28974 (from machine in your local network, but not linux machine itself) successful?
  • nmap -sU -p 28974-v your_linux_machine (from machine in your local network, but not linux machine itself) reporting open?
1 Like
6

hwm.land thanks for a lot of advice.

Docker is on Rocky 9, minimal install, everything is default. I have several such Storj installations and they work without problems. It seems to me that it’s blocked somewhere, but I tried everything, even mounting the storage disk on another OS, there were always the same errors…
Currently that Storj is running on the original win, should rsync again to try again. Rocky OS is alive but without docker running so I doubt I can test properly with nmap. Before shutting down docker and returning to win, the dashboard on linux worked and reported Offline.
I am most suspicious of the rsync data migration from Windows to Linux, but I can’t find any errors there either. Could this be the reason even though all the errors point to bad port forwarding?

7

one more thing, I find that the owner of directories and files on linux is 1000 1000! Could that be the source of the problem? Although I looked at a long-migrated Storj from win to linux and it has 1000 1000 but it works without any problems.

8

That is currently showing as closed. So either that isn’t your external IP or there’s an issue in the port forwarding or a firewall blocking it.

It will work if the permissions are set loose enough to let any user read/write. Better to set more restrictive permissions with the correct user/group.

Cheers.

9

You need to open the port up on firewalld

1 Like
10

Is it a DDNS? If so - please check, that it’s updated to your current IP: Open Port Check Tool - Test Port Forwarding on Your Router
(please replace domain to your actual domain):

nslookup domain 8.8.8.8

The resolved IP must match the IP on yougetsignal and the WAN IP on your router.

Also, is the container running?

docker ps -a

If not, please check why:

docker logs --tail 20 storagenode
11

Do you have SElinux enabled, or AppArmor?

You may need to addd extra mount parameters and configure permissions and namespaces differently. Have a look here, including every referenced article from there:

It’s about podman, but docker will be same (but everyone shall switch to podman anyway). Or since you just switched — consider FreeBSD instead. Much superior, non-nonsense, performant system for servers. (Yes, I’m biased. Very much so. The points still stand)