Both nodes are marked with "STATUS Offline" and "QUIC Misconfigured"

Node Operators troubleshooting
,
1

I have two storj nodes

Both nodes are marked with “STATUS Offline” and “QUIC Misconfigured”

What could be the problem?

These errors appear in the log:

2025-03-06T22:47:30+01:00 ERROR contact:service ping satellite failed {Satellite ID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, attempts: 1, error: ping satellite: context canceled, errorVerbose: ping satellite: context canceled\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:210\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}
2025-03-06T22:48:46+01:00 ERROR contact:service ping satellite failed {Satellite ID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, attempts: 2, error: ping satellite: context canceled, errorVerbose: ping satellite: context canceled\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:210\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}
2025-03-06T22:48:58+01:00 WARN console:service unable to get Satellite URL {Satellite ID: 118UWpMCHzs6CvSgWd9BfFVjw5K9pZbJjkfZJexMtSkmKxvvAW, error: console: trust: satellite is untrusted, errorVerbose: console: trust: satellite is untrusted\n\tstorj.io/storj/storagenode/trust.init:29\n\truntime.doInit:6527\n\truntime.doInit:6504\n\truntime.doInit:6504\n\truntime.doInit:6504\n\truntime.doInit:6504\n\truntime.doInit:6504\n\truntime.main:233}
2025-03-06T22:49:20+01:00 ERROR contact:service ping satellite failed {Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, attempts: 1, error: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.45.53.42:28967: connect: connection timed out, errorVerbose: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.45.53.42:28967: connect: connection timed out\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:216\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}
2025-03-06T22:49:21+01:00 ERROR contact:service ping satellite failed {Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, attempts: 1, error: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.45.53.42:28967: connect: connection timed out, errorVerbose: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.45.53.42:28967: connect: connection timed out\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:216\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}
2025-03-06T22:49:22+01:00 ERROR contact:service ping satellite failed {Satellite ID: 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE, attempts: 1, error: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.45.53.42:28967: connect: connection timed out, errorVerbose: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.45.53.42:28967: connect: connection timed out\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:216\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}
2025-03-06T22:49:38+01:00 ERROR contact:service ping satellite failed {Satellite ID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, attempts: 3, error: ping satellite: context canceled, errorVerbose: ping satellite: context canceled\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:210\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}
2025-03-06T22:50:03+01:00 ERROR contact:service ping satellite failed {Satellite ID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, attempts: 4, error: ping satellite: rpc: tcp connector failed: rpc: dial tcp 34.126.92.94:7777: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond., errorVerbose: ping satellite: rpc: tcp connector failed: rpc: dial tcp 34.126.92.94:7777: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190}
2025-03-06T22:50:09+01:00 INFO reputation:service node scores updated {Satellite ID: 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE, Total Audits: 1417540, Successful Audits: 1389454, Audit Score: 1, Online Score: 0.9189551932522501, Suspension Score: 1, Audit Score Delta: 0, Online Score Delta: 0, Suspension Score Delta: 0}
2025-03-06T22:50:31+01:00 INFO reputation:service node scores updated {Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Total Audits: 1656184, Successful Audits: 1628668, Audit Score: 1, Online Score: 0.9108568253408293, Suspension Score: 1, Audit Score Delta: 0, Online Score Delta: 0, Suspension Score Delta: 0}
2025-03-06T22:50:31+01:00 INFO reputation:service node scores updated {Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Total Audits: 2479322, Successful Audits: 2438067, Audit Score: 1, Online Score: 0.9112293976252962, Suspension Score: 1, Audit Score Delta: 0, Online Score Delta: 0, Suspension Score Delta: 0}
2025-03-06T22:50:31+01:00 ERROR reputation:chore reputation chore failed {error: reputation: rpc: tcp connector failed: rpc: dial tcp 34.126.92.94:7777: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond., errorVerbose: reputation: rpc: tcp connector failed: rpc: dial tcp 34.126.92.94:7777: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190}
2025-03-06T22:50:32+01:00 ERROR contact:service ping satellite failed {Satellite ID: 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6, attempts: 5, error: ping satellite: rpc: tcp connector failed: rpc: dial tcp 34.126.92.94:7777: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond., errorVerbose: ping satellite: rpc: tcp connector failed: rpc: dial tcp 34.126.92.94:7777: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.\n\tstorj.io/common/rpc.HybridConnector.DialContext.func1:190}
2025-03-06T22:51:31+01:00 ERROR contact:service ping satellite failed {Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, attempts: 2, error: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 79.157.87.123:28967: connect: connection timed out, errorVerbose: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 79.157.87.123:28967: connect: connection timed out\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:216\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}
2025-03-06T22:51:32+01:00 ERROR contact:service ping satellite failed {Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, attempts: 2, error: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.45.53.42:28967: connect: connection timed out, errorVerbose: ping satellite: failed to ping storage node, your node indicated error code: 0, rpc: tcp connector failed: rpc: dial tcp 83.45.53.42:28967: connect: connection timed out\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:216\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:158\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:89\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78}
2

Messages like that usually mean a satellite can’t reach in to you (like a port hasn’t been forwarded or something. You can double-check that your ports are open from several different sites (like this one)

1 Like
3

I’ve already fixed it. The local IP address of the computer has changed. That was the problem.

I’ve had the same router for years and the local IP address has never changed.

I’ve set an IP address outside the HDCP range on the computer so that it doesn’t change anymore.

2 Likes
4

You can fix it in the router by linking an IP to the PC’s MAC address, or in the PC’s network config. And reserve an IP range for fixed IP devices and an IP range for auto IP devices.
For storage nodes, mining rigs, systems that need port forwarding in general, use fixed IP.
That’s the golden rule.

3 Likes
5

Long ago I remember when our IT guys were hard-core about prod servers having static IPs that they carefully managed. Now they’re hard-core that everything is DHCP+reservations. After a couple rounds of one-company-buying-another-company-and-you-have-to-merge-networks … and having to do every change by hand… they saw the light! :wink:

1 Like
6

Static IP assignments are less desirable than dhcp reservations, for many reasons, outside of just management hurdles.

For one, without going through dhcp handshake dns server has no way to learn the hostname, so you’ll have to add that manually as well.

Curiously, some devices support “dhcp with manually specified IP” which may address both issues — ip is set on the host, and dhcp process obeys that, while still configuring everything correctly

If your dhcp server ever assigned different ip to the same host (that does not use MAC address randomization) — replace your dhcp server, it’s trash. As are most gateways on the consumer market.

Tangent comment — to talk to hosts in the local network mDNS is a way forward, where IP configuration or router quality is irrelevant because there is no requirement to have a predetermined IP.

1 Like
7

I’m having problems again. Same problem.

It tells me the node is misconfigured.
I have the IP configured manually on the computer.
The ports are open.

Do you recommend leaving the DHCP configuration enabled?
Any idea what the problem could be?

The online percentage is dropping. The lowest is 77%.

8

Have you followed this checklist ?

9

Post a screenshot. What is “Status”? is it “Online”? If so, you can ignore “QUIC”.

If status is Offline – then go through the same steps you went before. (DDNS/security/port forwarding/firewall)

1 Like
10

I checked.

It tells me the port is open

11

It appears to me like this

12

Your node is fine. Nothing to be concerned about.

13

Thank you very much.

I’ll note down the online percentage. Tomorrow I’ll see if it’s gone down or if it’s stayed the same.

14

Please make sure that you use a reliable DDNS provider like no-ip or Cloudflare.

See

15

I am now using duckdns.

16

Don’t use that - duckdns.org is definitely responsible; it’s especially bad for time-out to EU and Saltlake satellites.
Often times it can be down for hours too… because it’s an over-taxed free service amoung other things.

2 cents,
Julio

2 Likes
17

Stop immediately. Switch to something that at least has a chance of having half decent reliability at least in theory. Free service by two dudes is none of that.

https://forum.storj.io/search?context=topic&context_id=29514&q=Duckdns%20order%3Alatest&skip_context=true

1 Like
18
1 Like
19

I’ve used DuckDNS for years and haven’t had any problems.

The online percentage is getting lower and lower.

I’m going to set the IP manually for now to see if that solves the problem.

I’m going to look for another DDNS.