Node was suspended

Node Operators troubleshooting
, , ,
1

Hi, i have a this problem:

Your Node was suspended 2022-01-21 00:26:51.646073 +0000 UTC:
This is a reminder that your StorageNode on 12rfG3sWiXXXXXXXXXXXXXXxxxxxxxxxXXXXXXwymB Satellite is suspended

The problem I have had is that they changed my router and the opening of ports was not configured correctly.

Now everything works very well, and in another node that I have everything is Ok, but in this other node this message appears.

Can I do something to restart the node?

Thanks

2

If you node is properly set up, all you need to do is keep it online and wait for the node to recover from suspension. Successful audit and get_repair traffic will increase your suspension score. Make sure your node version is up to date (v1.47.3 as of this writing), and check the node logs for successful GET_AUDIT and GET_REPAIR lines. Note that your node will not get any ingress traffic until your suspension score is above 60%.

1 Like
3

ok, but its normal that the status its offline??

4

STATUS: Offline
QUIC: Misconfigured
UPTIME: 1h 32m
LAST CONTACT: 17716508h 58m ago
VERSION: v1.47.3
PERIOD: February

Its This Normal??

Thanks

5

No, the status should be online. Can you provide the last 30 lines of your storagenode log? To neatly put them in the forum, place the log lines with three backticks ``` above and below the block of log lines.

6

You said 30 lines of storagenode.log? i dont open because this file have a 10.2Gb and the notepad++ no open the file because its so big

7

In Storagenode-update.log said this:

2022-02-02T23:25:31.667+0100 INFO Downloading versions. {Server Address: https://version.storj.io}
2022-02-02T23:25:32.464+0100 INFO Version is up to date {Service: storagenode}
2022-02-02T23:25:32.464+0100 INFO Download started. {From: https://github.com/storj/storj/releases/download/v1.47.3/storagenode-updater_windows_amd64.zip, To: C:\Windows\TEMP\storagenode-updater_windows_amd64.939670252.zip}
2022-02-02T23:25:33.942+0100 ERROR Error updating service. {Service: storagenode-updater, error: open C:\Program Files\Storj\Storage Node\storagenode-updater.1.47.3.exe: Este archivo ya existe., errorVerbose: open C:\Program Files\Storj\Storage Node\storagenode-updater.1.47.3.exe: Este archivo ya existe.\n\tmain.downloadBinary:62\n\tmain.updateSelf:64\n\tmain.loopFunc:36\n\tstorj.io/common/sync2.(*Cycle).Run:152\n\tmain.cmdRun:116\n\tstorj.io/private/process.cleanup.func1.4:353\n\tstorj.io/private/process.cleanup.func1:371\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.Exec:65\n\tmain.(*service).Execute.func1:55\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57}
2022-02-02T23:40:31.667+0100 INFO Downloading versions. {Server Address: https://version.storj.io}
2022-02-02T23:40:32.238+0100 INFO Version is up to date {Service: storagenode}
2022-02-02T23:40:32.238+0100 INFO Download started. {From: https://github.com/storj/storj/releases/download/v1.47.3/storagenode-updater_windows_amd64.zip, To: C:\Windows\TEMP\storagenode-updater_windows_amd64.478996827.zip}
2022-02-02T23:40:33.461+0100 ERROR Error updating service. {Service: storagenode-updater, error: open C:\Program Files\Storj\Storage Node\storagenode-updater.1.47.3.exe: Este archivo ya existe., errorVerbose: open C:\Program Files\Storj\Storage Node\storagenode-updater.1.47.3.exe: Este archivo ya existe.\n\tmain.downloadBinary:62\n\tmain.updateSelf:64\n\tmain.loopFunc:36\n\tstorj.io/common/sync2.(*Cycle).Run:152\n\tmain.cmdRun:116\n\tstorj.io/private/process.cleanup.func1.4:353\n\tstorj.io/private/process.cleanup.func1:371\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.Exec:65\n\tmain.(*service).Execute.func1:55\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57}
8

You can get the logs lines we need by stopping the storagenode service, renaming the log file to something like oldstorj.log and then starting the storagenode service again. This will create a new log file. Don’t delete the old log file yet in case it is needed for troubleshooting.

Instructions to stop and start the node:

9
2022-02-03T07:11:00.326+0100 ERROR contact:service ping satellite failed {Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, attempts: 5, error: ping satellite: failed to dial storage node (ID: 12XXXXXXXXXaHcugha) at address nodXXXXete.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID, errorVerbose: ping satellite: failed to dial storage node (ID: 12XXXXXXXXXXXXHcugha) at address nodxxxxxxete.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:139\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57}
2022-02-03T07:11:01.111+0100 ERROR contact:service ping satellite failed {Satellite ID: 12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB, attempts: 5, error: ping satellite: failed to dial storage node (ID: 12XXXXXXXXXXXXHcugha) at address nodxxxxxete.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID, errorVerbose: ping satellite: failed to dial storage node (ID: 12XXXXXXXXXXXXHcugha) at address nodxxxxxxete.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:139\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57}
2022-02-03T07:11:02.081+0100 ERROR contact:service ping satellite failed {Satellite ID: 12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo, attempts: 5, error: ping satellite: check-in ratelimit: node rate limited by id, errorVerbose: ping satellite: check-in ratelimit: node rate limited by id\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:136\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57}
2022-02-03T07:11:03.047+0100 ERROR contact:service ping satellite failed {Satellite ID: 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE, attempts: 5, error: ping satellite: check-in ratelimit: node rate limited by id, errorVerbose: ping satellite: check-in ratelimit: node rate limited by id\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:136\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57}
2022-02-03T07:11:03.127+0100 ERROR contact:service ping satellite failed {Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, attempts: 5, error: ping satellite: failed to dial storage node (ID: 12XXXXXXXXXXXXHcugha) at address nodxxxxxete.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID, errorVerbose: ping satellite: failed to dial storage node (ID: 12XXXXXXXXXXXXHcugha) at address nodxxxxxete.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:139\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57}
2022-02-03T07:11:04.004+0100 ERROR contact:service ping satellite failed {Satellite ID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, attempts: 5, error: ping satellite: check-in ratelimit: node rate limited by id, errorVerbose: ping satellite: check-in ratelimit: node rate limited by id\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:136\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57}
2022-02-03T07:11:16.548+0100 ERROR contact:service ping satellite failed {Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, attempts: 6, error: ping satellite: failed to dial storage node (ID: 12XXXXXXXXXXXXHcugha: tlsopts: peer ID did not match requested ID, errorVerbose: ping satellite: failed to dial storage node (ID: 12XXXXXXXXXXXXHcugha) at address nodxxxxete.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:139\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57}
10

Interesting. This message suggests that your identity is corrupted somehow. The NodeID (the public key) doesn’t match the private key (identity.key)

However, I now have a question - is that node even worked? Because it cannot be online with unsigned or corrupted identity.
Have you removed the previous identity or did something unusual or have you lost something recently?

11

Hello, no, I have not changed or modified anything, if you see it well I can change the Key for the Backup that I made of it when I created the node.

12

If you have a back-up of the identity, and you are 100% sure that it is for this specific node, then you could try using a copy of the backup identity files. However don’t delete your current identity files yet. Save them somewhere else.

2 Likes
13

Sure this is not a DNS issue?
Your ISP probably reset DDNS settings in the router?
Did your port mapping changed to another address?
Do you have the host with static lease in DHCP?

14

Hi, dont work. Storagenode.log said this:

2022-02-04T16:36:53.167+0100 WARN failed QUIC check {“error”: “ping satellite: failed to ping storage node using QUIC: ping satellite: check-in network: failed to ping node (ID: MY ID NODE ADDRESS) at address: MY IP ADDRESS.ddns.net:28967, err: contact: failed to dial storage node (ID: MY ID NODE ADDRESS) at address MY IP ADDRESS.ddns.net:28967 using QUIC: rpc: quic: CRYPTO_ERROR (0x12a): tls peer certificate verification: tlsopts: peer ID did not match requested ID”, “errorVerbose”: “ping satellite: failed to ping storage node using QUIC: ping satellite: check-in network: failed to ping node (ID: MY ID NODE ADDRESS) at address: MY IP ADDRESS.ddns.net:28967, err: contact: failed to dial storage node (ID: MY ID NODE ADDRESS) at address MY IP ADDRESS.ddns.net:28967 using QUIC: rpc: quic: CRYPTO_ERROR (0x12a): tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).RequestPingMeQUIC:176\n\tstorj.io/storj/storagenode.(*Peer).addConsoleService:841\n\tstorj.io/storj/storagenode.(*Peer).Run:880\n\tmain.cmdRun:251\n\tstorj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\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.ExecWithCustomConfig:88\n\tstorj.io/private/process.Exec:65\n\tmain.(*service).Execute.func1:61\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2022-02-04T16:36:53.167+0100 INFO trust Scheduling next refresh {“after”: “6h0m45.680571344s”}
2022-02-04T16:36:53.169+0100 INFO bandwidth Performing bandwidth usage rollups
2022-02-04T16:36:53.438+0100 ERROR contact:service ping satellite failed {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “attempts”: 1, “error”: “ping satellite: failed to dial storage node (ID: MY ID NODE ADDRESS) at address MY IP ADDRESS.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID”, “errorVerbose”: “ping satellite: failed to dial storage node (ID: MY ID NODE ADDRESS) at address MY IP ADDRESS.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:139\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2022-02-04T16:36:53.589+0100 ERROR contact:service ping satellite failed {“Satellite ID”: “12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB”, “attempts”: 1, “error”: “ping satellite: failed to dial storage node (ID: MY ID NODE ADDRESS) at address MY IP ADDRESS.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID”, “errorVerbose”: “ping satellite: failed to dial storage node (ID: MY ID NODE ADDRESS) at address MY IP ADDRESS.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:139\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2022-02-04T16:36:53.678+0100 ERROR collector unable to delete piece {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Piece ID”: “2S3VNAIJBOINVHFQNCCFHM3277B3DRYALIEM73ZJGEC2Y56UPX3A”, “error”: “pieces error: filestore error: file does not exist”, “errorVerbose”: “pieces error: filestore error: file does not exist\n\tstorj.io/storj/storage/filestore.(*blobStore).Stat:103\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).pieceSizes:239\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).Delete:220\n\tstorj.io/storj/storagenode/pieces.(*Store).Delete:299\n\tstorj.io/storj/storagenode/collector.(*Service).Collect:97\n\tstorj.io/storj/storagenode/collector.(*Service).Run.func1:57\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/collector.(*Service).Run:53\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2022-02-04T16:36:53.801+0100 ERROR contact:service ping satellite failed {“Satellite ID”: “12tRQrMTWUWwzwGh18i7Fqs67kmdhH9t6aToeiwbo5mfS2rUmo”, “attempts”: 1, “error”: “ping satellite: failed to dial storage node (ID: MY ID NODE ADDRESS) at address MY IP ADDRESS.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID”, “errorVerbose”: “ping satellite: failed to dial storage node (ID: MY ID NODE ADDRESS) at address MY IP ADDRESS.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:139\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2022-02-04T16:36:53.863+0100 ERROR collector unable to delete piece {“Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Piece ID”: “AIEPRSBQQIGFDYNAZATQWEXRYQYUAO6DMUA4WFTCLJ42QEHOISIQ”, “error”: “pieces error: filestore error: file does not exist”, “errorVerbose”: “pieces error: filestore error: file does not exist\n\tstorj.io/storj/storage/filestore.(*blobStore).Stat:103\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).pieceSizes:239\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).Delete:220\n\tstorj.io/storj/storagenode/pieces.(*Store).Delete:299\n\tstorj.io/storj/storagenode/collector.(*Service).Collect:97\n\tstorj.io/storj/storagenode/collector.(*Service).Run.func1:57\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/collector.(*Service).Run:53\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\truntime/pprof.Do:40\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
2022-02-04T16:36:53.877+0100 ERROR contact:service ping satellite failed {“Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “attempts”: 1, “error”: “ping satellite: failed to dial storage node (ID: MY ID NODE ADDRESS) at address MY IP ADDRESS.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID”, “errorVerbose”: “ping satellite: failed to dial storage node (ID: MY ID NODE ADDRESS) at address MY IP ADDRESS.ddns.net:28967: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:139\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:98\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}

15

And this Storagenode-updater.log

2022-02-04T16:36:44.733+0100 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}
2022-02-04T16:36:44.733+0100 INFO Invalid configuration file key {“Key”: “operator.email”}
2022-02-04T16:36:44.733+0100 INFO Invalid configuration file key {“Key”: “contact.external-address”}
2022-02-04T16:36:44.733+0100 INFO Invalid configuration file key {“Key”: “storage.allocated-disk-space”}
2022-02-04T16:36:44.733+0100 INFO Invalid configuration file key {“Key”: “server.private-address”}
2022-02-04T16:36:44.733+0100 INFO Invalid configuration file key {“Key”: “operator.wallet”}
2022-02-04T16:36:44.733+0100 INFO Invalid configuration file key {“Key”: “storage.allocated-bandwidth”}
2022-02-04T16:36:44.733+0100 INFO Invalid configuration file key {“Key”: “server.address”}
2022-02-04T16:36:44.733+0100 INFO Invalid configuration file key {“Key”: “storage.path”}
2022-02-04T16:36:44.733+0100 INFO Invalid configuration file value for key {“Key”: “log.output”}
2022-02-04T16:36:44.733+0100 INFO Invalid configuration file value for key {“Key”: “log.encoding”}
2022-02-04T16:36:44.734+0100 INFO Running on version {“Service”: “storagenode-updater”, “Version”: “v1.47.3”}
2022-02-04T16:36:44.734+0100 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}
2022-02-04T16:36:45.336+0100 INFO Current binary version {“Service”: “storagenode”, “Version”: “v1.47.3”}
2022-02-04T16:36:45.336+0100 INFO Version is up to date {“Service”: “storagenode”}
2022-02-04T16:36:45.409+0100 INFO Current binary version {“Service”: “storagenode-updater”, “Version”: “v1.47.3”}
2022-02-04T16:36:45.409+0100 INFO Version is up to date {“Service”: “storagenode-updater”}
2022-02-04T16:38:38.938+0100 INFO Stop/Shutdown request received.

16

Hi, I have tried to change ALL the files in the Identity folder for the BackUp I did when I created the node and this from the other two posts is what I got.

That backUp is the correct one for that node, I have checked it several times.

No matter how hard I try, it doesn’t work.

DNS configuration problem, Router, Ports and others is not, since I have another node in the same network and using the same router and it works perfectly.

What else could I do?

I don’t want to format the RAID on this node and start from scratch.

Thanks

17

Since you have another node in this network, it’s likely uses the same external port 28967.
So, on this one you must use a different one, 28968 for example. You still can use 28967 as an internal port, if the second node on different PC or if it’s a docker container.
Make sure that the external address for this second node has the second external port, for example ADDRESS.ddns.net:28968
You also need to forward 28968 tcp/udp → 28968 to the address of the PC with storagenode.
In your docker run command it should be configured like -p 28968:28967/tcp -p 28968:28967/udp -e ADDRESS=ADDRESS.ddns.net:28968

18

FINALLY!!!

That was the problem!!!

I have opened port 28968 and I have modified it in the Config.yaml and when opening the dashboard I get Status OK and QUIC OK!!!

Thanks for everything, now I will have to wait for the node to be verified, since it is at 10.51% Online, Audit 100% and Suspension 100%

How long could it take to go up to 70% or 80%??

19

To fully recover the node should be online for the next 30 days.
Each offline event will require additional 30 days online.