After Windows server reboot dashboard zeroed but traffic exist

Node Operators troubleshooting
,
1

After Windows server reboot dashboard zeroed but traffic exist. Connection status OFFLINE but log shows activity

2026-05-24T01:08:49+03:00 INFO piecestore downloaded {piece_id: RJJ3GQBIIA5XNPV3X63EKQEEAKXBS7YI6LGIZ2I6SP4XCIFPZCRQ, satellite_id: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, action: GET, offset: 353280, size: 256, remote_address: 192.168.113.1:50512}
2026-05-24T01:08:49+03:00 INFO piecestore downloaded {piece_id: RJJ3GQBIIA5XNPV3X63EKQEEAKXBS7YI6LGIZ2I6SP4XCIFPZCRQ, satellite_id: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, action: GET, offset: 504320, size: 256, remote_address: 192.168.113.1:50512}

Also - log file size is HUGE - more than 3GB

2
3

You may try to clear the cache and force reload a dashboard in your browser.
If the status wouldn’t change, then please search for “ping satellite failed” in your logs, e.g. in PowerShell:

sls "ping satellite failed" "C:\Program Files\Storj\Storage Node\storagenode.log" | Select -last 20

To reduce a log file, you may stop the node, rename the file and restart the node.
Also you may use these scripts:

4

No “Error starting master database on storagenode” errors foung
Instead see filewealker errors

2026-05-23T14:01:15-07:00 INFO Stop/Shutdown request received.
2026-05-23T14:01:15-07:00 INFO piecestore upload canceled {“piece_id”: “IRQTR3QSWBU4BP63VPABR27VNA2OSPXTHPPNWHFEJV4WFOW5YYTQ”, “satellite_id”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “action”: “PUT”, “remote_address”: “192.168.113.1:34596”, “size”: 1769472}
2026-05-23T14:01:15-07:00 INFO lazyfilewalker.used-space-filewalker subprocess exited with status {“satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “status”: 1, “error”: “exit status 1”}
2026-05-23T14:01:15-07:00 ERROR pieces used-space-filewalker failed {“satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “lazy_file_walker”: true, “error”: “lazyfilewalker: exit status 1”, “errorVerbose”: “lazyfilewalker: exit status 1\n\tstorj.io/storj/storagenode/pieces/lazyfilewalker.(*process).run:85\n\tstorj.io/storj/storagenode/pieces/lazyfilewalker.(*Supervisor).WalkAndComputeSpaceUsedBySatellite:134\n\tstorj.io/storj/storagenode/pieces.(*Store).WalkAndComputeSpaceUsedBySatellite:781\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:85\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:93”}
2026-05-23T14:01:15-07:00 ERROR pieces used-space-filewalker failed {“satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “lazy_file_walker”: false, “error”: “filewalker: used_space_per_prefix_db: context canceled”, “errorVerbose”: “filewalker: used_space_per_prefix_db: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*usedSpacePerPrefixDB).Get:81\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatelliteWithWalkFunc:163\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatellite:150\n\tstorj.io/storj/storagenode/pieces.(*Store).WalkAndComputeSpaceUsedBySatellite:790\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:85\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:93”}
2026-05-23T14:01:15-07:00 ERROR piecestore:cache encountered error while computing space used by satellite {“error”: “filewalker: used_space_per_prefix_db: context canceled”, “errorVerbose”: “filewalker: used_space_per_prefix_db: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*usedSpacePerPrefixDB).Get:81\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatelliteWithWalkFunc:163\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatellite:150\n\tstorj.io/storj/storagenode/pieces.(*Store).WalkAndComputeSpaceUsedBySatellite:790\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:85\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:93”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”}
2026-05-23T14:01:15-07:00 INFO pieces used-space-filewalker started {“satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2026-05-23T14:01:15-07:00 INFO lazyfilewalker.used-space-filewalker starting subprocess {“satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2026-05-23T14:01:15-07:00 ERROR lazyfilewalker.used-space-filewalker failed to start subprocess {“satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “error”: “context canceled”}
2026-05-23T14:01:15-07:00 ERROR pieces used-space-filewalker failed {“satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “lazy_file_walker”: true, “error”: “lazyfilewalker: context canceled”, “errorVerbose”: “lazyfilewalker: context canceled\n\tstorj.io/storj/storagenode/pieces/lazyfilewalker.(*process).run:73\n\tstorj.io/storj/storagenode/pieces/lazyfilewalker.(*Supervisor).WalkAndComputeSpaceUsedBySatellite:134\n\tstorj.io/storj/storagenode/pieces.(*Store).WalkAndComputeSpaceUsedBySatellite:781\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:85\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:93”}
2026-05-23T14:01:15-07:00 ERROR pieces used-space-filewalker failed {“satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “lazy_file_walker”: false, “error”: “filewalker: used_space_per_prefix_db: context canceled”, “errorVerbose”: “filewalker: used_space_per_prefix_db: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*usedSpacePerPrefixDB).Get:81\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatelliteWithWalkFunc:163\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatellite:150\n\tstorj.io/storj/storagenode/pieces.(*Store).WalkAndComputeSpaceUsedBySatellite:790\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:85\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:93”}
2026-05-23T14:01:15-07:00 ERROR piecestore:cache encountered error while computing space used by satellite {“error”: “filewalker: used_space_per_prefix_db: context canceled”, “errorVerbose”: “filewalker: used_space_per_prefix_db: context canceled\n\tstorj.io/storj/storagenode/storagenodedb.(*usedSpacePerPrefixDB).Get:81\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatelliteWithWalkFunc:163\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkAndComputeSpaceUsedBySatellite:150\n\tstorj.io/storj/storagenode/pieces.(*Store).WalkAndComputeSpaceUsedBySatellite:790\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:85\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:93”, “satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2026-05-23T14:01:15-07:00 ERROR piecestore:cache error getting current used space for trash: {“error”: “filestore error: failed to walk trash namespace 7b2de9d72c2e935f1918c058caaf8ed00f0581639008707317ff1bd000000000: context canceled”, “errorVerbose”: “filestore error: failed to walk trash namespace 7b2de9d72c2e935f1918c058caaf8ed00f0581639008707317ff1bd000000000: context canceled\n\tstorj.io/storj/storagenode/blobstore/filestore.(*blobStore).SpaceUsedForTrash:302\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run.func1:104\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:93”}
2026-05-23T14:01:16-07:00 INFO Configuration loaded {“location”: “C:\Program Files\Storj\Storage Node\config.yaml”}
2026-05-23T14:01:16-07:00 INFO Anonymized tracing enabled

5

After this errors block no any errors shown and node upload/dounload other pieces

6

errors not visible for the moment

7

These are shutdown logs, ending with two lines of your node starting back.

2026-05-23T14:01:16-07:00 INFO Configuration loaded {"location": "C:\Program Files\Storj\Storage Node\config.yaml"}
2026-05-23T14:01:16-07:00 INFO Anonymized tracing enabled

Post what happens next.

Please format logs properly; it’s hard to read the unwieldy unformatted blob.

8

Hi Here is pice of log from last restart (i’ve recereated log file as Alexey recommended)
2026-05-24T18:17:44+03:00 INFO Stop/Shutdown request received.
2026-05-24T18:17:44+03:00 INFO lazyfilewalker.trash-cleanup-filewalker subprocess exited with status {“satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “status”: 1, “error”: “exit status 1”}
2026-05-24T18:17:44+03:00 ERROR pieces:trash emptying trash failed {“error”: “pieces error: lazyfilewalker: exit status 1”, “errorVerbose”: “pieces error: lazyfilewalker: exit status 1\n\tstorj.io/storj/storagenode/pieces/lazyfilewalker.(process).run:85\n\tstorj.io/storj/storagenode/pieces/lazyfilewalker.(Supervisor).WalkCleanupTrash:196\n\tstorj.io/storj/storagenode/pieces.(Store).EmptyTrash:486\n\tstorj.io/storj/storagenode/pieces.(TrashChore).Run.func1.1:86\n\tstorj.io/common/sync2.(Workplace).Start.func1:89"}
2026-05-24T18:17:44+03:00 ERROR piecestore:cache error getting current used space for trash: {“error”: “filestore error: failed to walk trash namespace a28b4f04e10bae85d67f4c6cb82bf8d4c0f0f47a8ea72627524deb6ec0000000: context canceled”, “errorVerbose”: "filestore error: failed to walk trash namespace a28b4f04e10bae85d67f4c6cb82bf8d4c0f0f47a8ea72627524deb6ec0000000: context canceled\n\tstorj.io/storj/storagenode/blobstore/filestore.(blobStore).SpaceUsedForTrash:302\n\tstorj.io/storj/storagenode/pieces.(CacheService).Run.func1:104\n\tgolang.org/x/sync/errgroup.(Group).Go.func1:93"}
2026-05-24T18:17:48+03:00 INFO Configuration loaded {“location”: “C:\Program Files\Storj\Storage Node\config.yaml”}
2026-05-24T18:17:48+03:00 INFO Anonymized tracing enabled
2026-05-24T18:17:48+03:00 INFO Operator email {“address”: ""}
2026-05-24T18:17:48+03:00 INFO Operator wallet {“address”: "******************”}
2026-05-24T18:17:48+03:00 INFO hashstore loaded hint file {“satellite”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “store”: “s0”, “path”: “T:\Storj\hashstore\1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE\s0\meta\hint-0000000000000013”, “writable”: , “largest”: 15, “skip”: false}
2026-05-24T18:17:48+03:00 INFO hashstore loaded hint file {“satellite”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “store”: “s1”, “path”: “T:\Storj\hashstore\1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE\s1\meta\hint-0000000000000015”, “writable”: , “largest”: 21, “skip”: false}
2026-05-24T18:17:48+03:00 INFO hashstore hashstore opened successfully {“satellite”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “open_time”: “32.3779ms”, “logs_skipped”: 22, “logs_matched”: 0, “logs_mismatched”: 0}
2026-05-24T18:17:48+03:00 INFO piecemigrate:chore piece migration chore initialized {“old_blobs_path”: “T:\Storj\blobs”, “cleanup_enabled”: true}
2026-05-24T18:17:49+03:00 INFO Telemetry enabled {“instance_id”: “12E12QF1yEZ8DCKRukMnJpykqXLfEbaon6zNMpGvTGfJYdUm8PD”}
2026-05-24T18:17:49+03:00 INFO Event collection enabled {“instance_id”: “12E12QF1yEZ8DCKRukMnJpykqXLfEbaon6zNMpGvTGfJYdUm8PD”}
2026-05-24T18:17:49+03:00 INFO db.migration Database Version {“version”: 62}
2026-05-24T18:17:49+03:00 INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2026-05-24T18:17:49+03:00 INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2026-05-24T18:17:49+03:00 INFO collector expired pieces collection started
2026-05-24T18:17:49+03:00 INFO Node 12E12QF1yEZ8DCKRukMnJpykqXLfEbaon6zNMpGvTGfJYdUm8PD started
2026-05-24T18:17:49+03:00 INFO Public server started on [::]:28967
2026-05-24T18:17:49+03:00 INFO Private server started on 127.0.0.1:7778
2026-05-24T18:17:49+03:00 INFO trust Scheduling next refresh {“after”: “5h40m29.305617452s”}
2026-05-24T18:17:49+03:00 INFO bandwidth Persisting bandwidth usage cache to db
2026-05-24T18:17:49+03:00 INFO pieces:trash emptying trash started {“satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2026-05-24T18:17:49+03:00 INFO lazyfilewalker.trash-cleanup-filewalker starting subprocess {“satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2026-05-24T18:17:49+03:00 INFO pieces used-space-filewalker started {“satellite_id”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”}
2026-05-24T18:17:49+03:00 INFO lazyfilewalker.used-space-filewalker starting subprocess {“satellite_id”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”}
2026-05-24T18:17:49+03:00 INFO piecemigrate:chore enqueued for migration {“sat”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”}
2026-05-24T18:17:49+03:00 INFO piecemigrate:chore all enqueued for migration; will sleep before next pooling {“active”: {“121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”: false, “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”: false, “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”: false, “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”: true}, “interval”: “10m0s”}
2026-05-24T18:17:50+03:00 INFO collector expired pieces collection completed {“count”: 0}
2026-05-24T18:17:50+03:00 INFO lazyfilewalker.trash-cleanup-filewalker subprocess started {“satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”}
2026-05-24T18:17:50+03:00 INFO lazyfilewalker.used-space-filewalker subprocess started {“satellite_id”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”}
2026-05-24T18:17:50+03:00 INFO lazyfilewalker.trash-cleanup-filewalker.subprocess trash-filewalker started {“satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “process”: “storagenode”, “date_before”: “2026-05-17T18:17:49+03:00”}
2026-05-24T18:17:50+03:00 INFO lazyfilewalker.trash-cleanup-filewalker.subprocess Database started {“satellite_id”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “process”: “storagenode”}
2026-05-24T18:17:50+03:00 INFO lazyfilewalker.used-space-filewalker.subprocess Database started {“satellite_id”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “process”: “storagenode”}
2026-05-24T18:17:58+03:00 INFO piecestore uploaded {“piece_id”: “QFE7CHVIKRHAEBGHOABUWS7MJNC6NIH6AA4NIIIEKCC6OM4JDEFA”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “PUT_REPAIR”, “remote_address”: “192.168.113.1:34638”, “size”: 169984}
2026-05-24T18:17:58+03:00 INFO piecestore downloaded {“piece_id”: “JCGRNI7IUH276AGWW255VY4G67W2EWOWZFCRNP2BZSWFMFYVEIJQ”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET”, “offset”: 0, “size”: 8448, “remote_address”: “192.168.113.1:45148”}
2026-05-24T18:17:58+03:00 INFO piecestore downloaded {“piece_id”: “WR3NRWEIXZYRSMIYXRUEKIJP7HEWRFZVLMNGV3R3P4GOWKTW5K6Q”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET”, “offset”: 0, “size”: 1024, “remote_address”: “192.168.113.1:51444”}
2026-05-24T18:17:58+03:00 INFO piecestore uploaded {“piece_id”: “7YYAZR2JJCU7OWE5TLCV2WQZ2QLDBPBNTZCKVUCJOCPXWA2K6SRA”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “PUT”, “remote_address”: “192.168.113.1:60238”, “size”: 7168}
2026-05-24T18:17:58+03:00 INFO piecestore downloaded {“piece_id”: “JXDP5GBBZUEKQLW2QGK2ILCAKL2W4EAHTUUPX2YCUXW3SQQXQQ6A”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET”, “offset”: 0, “size”: 9216, “remote_address”: “192.168.113.1:45168”}
2026-05-24T18:17:59+03:00 INFO piecestore downloaded {“piece_id”: “5CJGTLRVVDVREMD4VTWGC3I4J5UFI677BP5QJVXTECAH2YDWIW5Q”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET”, “offset”: 0, “size”: 7424, “remote_address”: “192.168.113.1:42962”}
2026-05-24T18:17:59+03:00 INFO piecestore downloaded {“piece_id”: “5FLFQRHVXJSQJMQJDI2J7BVDWQYXL6CGU7X2TQP7YLP5IG25ARDQ”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET”, “offset”: 0, “size”: 8192, “remote_address”: “192.168.113.1:34908”}
2026-05-24T18:17:59+03:00 INFO piecestore downloaded {“piece_id”: “ZE4UI2S4O5XMZAESSQ34JYC6LVCDAYGI62KGMJCBQ3VV3YHBOSHA”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET”, “offset”: 0, “size”: 4608, “remote_address”: “192.168.113.1:58060”}
2026-05-24T18:17:59+03:00 INFO piecestore downloaded {“piece_id”: “JCGRNI7IUH276AGWW255VY4G67W2EWOWZFCRNP2BZSWFMFYVEIJQ”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET”, “offset”: 0, “size”: 8448, “remote_address”: “192.168.113.1:55928”}
2026-05-24T18:17:59+03:00 INFO piecestore uploaded {“piece_id”: “2275DRZLL4FBSKOQFMQD2KNOCT3GWMLFUOJX3GYFGE7RWSC7NZDQ”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “PUT”, “remote_address”: “192.168.113.1:58540”, “size”: 1536}
2026-05-24T18:18:00+03:00 INFO piecestore downloaded

9

Sorry if it formatted wrong, how I can format it in a right way for this forum?

10

I’m still have Dashboard in a this state

image
image883Ă—798 29.6 KB

11

Storj traffic active

image
image758Ă—486 32 KB

12

Looks like your node is online and accepting traffic

However all IPs it interacts with are 192.168.113.1. Yiu have masquerading configured incorrectly.

This is discourse. So it supports markdown.

Also there are UI controls right in the comment/post editor.

It’s either stale web page (refresh from origin) or it gets confused because your NAT is messed up.

I would focus on fixing networking. You want to see actual addresses in the log and. Of those of your translator host.

Your FortiGate inbound port-forward/DNAT rule is also doing source NAT, so the Storj node sees the firewall interface address 192.168.113.1 instead of the real remote peer

13

Before last reboot all was right - even with mascraded IP’s after NAT. It’s not a reason - I’ve cheked olg logs and anything with transfers looks the same

14

The fact that it worked sometimes does not make it right. Your firewall rule is still wrong. Whether this can cause intermittent failures with online status detection or other issues I don’t know, and don’t care to find out. There is no reason to ignore known broken configuration.

Then restart the node and refresh the page. Also ensure your DDNS is correct. It can be totally wrong, and node will still be receiving and sending traffic for a while becuse satellites resolved a good IP once and cached it.

What DDNS provider are you using? Have you tested reachabilty from outside of your network, outside of your fortigate gateway? E.g. go to http://node-ddns:node-port on your cell phone with WiFi disabled.

Verify the log of your ddns updater that it programs correct address and does not flap.

(And by the way I would replace fortigate with better firewall. The fact that it allowed to silently mess up the configuration like that (it enabled SNAT without you asking) is disqualifying enough.)

15

If you know issue - please show it. It worked 3 years for me for old node and after year gap - 2 month for the new one

16

Done and checked - DDNS works fine. Storj not only service that works for me

17

You can’t possibly know that.

What ddns service are you using?

18

For the moment it’s best one’s that can show me what happened with my network and traffic. If you dont’t like it - it’s not mean that it totally bad. My colleage told me - allthings around us totally shit. But it works

19

If you want help debugging this, you need to answer the specific questions (I asked about DDNS three times anlready) and provide the requested external reachability test results, not just assert that it works. If everything is working correctly, then there is no problem to debug; but your dashboard says offline, so something in the current setup or reporting path is still broken.

You need to fix the inbound SNAT. The fact that a broken configuration appeared to work for some time does not make it correct, and it does not make it irrelevant to an offline-dashboard problem.

20

Ping from console far from my country

C:\Users\user>ping anlhome31.float-zone.com

Pinging anlhome31.float-zone.com [93.125.84.152] with 32 bytes of data:
Reply from 93.125.84.152: bytes=32 time=87ms TTL=243
Reply from 93.125.84.152: bytes=32 time=78ms TTL=243
Reply from 93.125.84.152: bytes=32 time=77ms TTL=243
Reply from 93.125.84.152: bytes=32 time=80ms TTL=243

Ping statistics for 93.125.84.152:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 87ms, Average = 80ms

C:\Users\user>