I currently live in Russia and I would like to know if there is any penalty for nodes in this region, because I have my node well configured with port forwarding correctly and it still tells me that QUIC is misconfigured with port 28967
Hi @dcripto
Welcome to the Forum !
There is no penalty.
I’ve forwarded this to the team for support.
There is no restrictions specifically to UDP.
You just need to configure it: QUIC requirements | Storj Docs
Can I put my node check here?
It should be done on your side. The satellite only report - can it contact your node or not. And you can see that in your logs.
If you node is showed as offline, I would recommend to check all points from
If you use Windows GUI:
Please also check your identity.
The problem is the following, it tells me that it is disconnected because QUIC is misconfigured and I have to redirect port 28967, but when I check all the ports in ubuntu I have that port open in both TCP and UDP, so I don’t understand what is happening
docker-pr 2102547 root 4u IPv4 54630495 0t0 TCP *:8016 (LISTEN)
docker-pr 2102555 root 4u IPv6 54627959 0t0 TCP *:8016 (LISTEN)
docker-pr 2102569 root 4u IPv4 54630502 0t0 TCP *:1932 (LISTEN)
docker-pr 2102577 root 4u IPv6 54629440 0t0 TCP *:1932 (LISTEN)
cupsd 2123309 root 6u IPv6 54830562 0t0 TCP [::1]:631 (LISTEN)
cupsd 2123309 root 7u IPv4 54830563 0t0 TCP 127.0.0.1:631 (LISTEN)
cups-brow 2123310 root 7u IPv4 54830615 0t0 UDP *:631
docker-pr 2376409 root 4u IPv4 57295990 0t0 TCP *:28967 (LISTEN)
docker-pr 2376416 root 4u IPv6 57297971 0t0 TCP *:28967 (LISTEN)
docker-pr 2376430 root 4u IPv4 57295993 0t0 UDP *:28967
docker-pr 2376437 root 4u IPv6 57297988 0t0 UDP *:28967
docker-pr 2376450 root 4u IPv4 57295527 0t0 TCP 127.0.0.1:14002 (LISTEN)
I copied the identity folder and pasted it in another place and that was the address I put, does it have something to do with it?
I just checked the identity and it gave me the correct results, but that address was not the one I put in how do I stop docker and restart the node with the correct address?
I hope you mean the ADDRESS option.
The email address doesn’t matter. It can be used only to notify you about suspension or disqualification (usually when it’s too late).
Please also check your logs: How do I check my logs? | Storj Docs
Is it a second node? If so - please immediately stop the cloned one, otherwise both nodes will be disqualified within a hour.
Each node must have an own unique generated identity.
1 Like
2022-07-25T18:50:12.073Z ERROR contact:service ping satellite failed {“Process”: “storagenode”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “attempts”: 8, “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:99\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}
It’s a single node, I don’t have two storj nodes
1 Like
This error is a consequence of not responding node. Please search for a previous error.
like which? the list is too long
ERROR contact:service ping satellite failed but doesn’t contain check-in ratelimit.
It won’t let me reply within 23 hours, I’m going to send you here other errors
2022-07-25 18:47:54,505 INFO supervisord started with pid 1
2022-07-25 18:47:55,507 INFO spawned: ‘processes-exit-eventlistener’ with pid 57
2022-07-25 18:47:55,508 INFO spawned: ‘storagenode’ with pid 58
2022-07-25 18:47:55,509 INFO spawned: ‘storagenode-updater’ with pid 59
2022-07-25T18:47:55.516Z INFO Configuration loaded {“Process”: “storagenode-updater”, “Location”: “/app/config/config.yaml”}
2022-07-25T18:47:55.516Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.email”}
2022-07-25T18:47:55.516Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.private-address”}
2022-07-25T18:47:55.516Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet”}
2022-07-25T18:47:55.516Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “server.address”}
2022-07-25T18:47:55.516Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “console.address”}
2022-07-25T18:47:55.516Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-bandwidth”}
2022-07-25T18:47:55.516Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “storage.allocated-disk-space”}
2022-07-25T18:47:55.516Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “contact.external-address”}
2022-07-25T18:47:55.516Z INFO Invalid configuration file key {“Process”: “storagenode-updater”, “Key”: “operator.wallet-features”}
2022-07-25T18:47:55.516Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.caller”}
2022-07-25T18:47:55.516Z INFO Invalid configuration file value for key {“Process”: “storagenode-updater”, “Key”: “log.level”}
2022-07-25T18:47:55.516Z INFO Running on version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.59.1”}
2022-07-25T18:47:55.516Z INFO Downloading versions. {“Process”: “storagenode-updater”, “Server Address”: “https://version.storj.io”}
2022-07-25T18:47:55.531Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2022-07-25T18:47:55.531Z INFO Operator email {“Process”: “storagenode”, “Address”: “dcriptocuba92@gmail.com”}
2022-07-25T18:47:55.531Z INFO Operator wallet {“Process”: “storagenode”, “Address”: “0xD360e2f9b6ed98C4d40ed36fc30b70d66DCb3d63”}
2022-07-25T18:47:55.957Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode”, “Version”: “v1.59.1”}
2022-07-25T18:47:55.957Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode”}
2022-07-25T18:47:55.962Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.59.1”}
2022-07-25T18:47:55.962Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”}
2022-07-25T18:47:56.620Z INFO Telemetry enabled {“Process”: “storagenode”, “instance ID”: “12dQqAuRRHQY3QnzCozVFev7sD9BnVay33z5HKr364rsxjqApdK”}
2022-07-25 18:47:56,621 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-07-25 18:47:56,621 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-07-25 18:47:56,621 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-07-25T18:47:56.630Z INFO db.migration Database Version {“Process”: “storagenode”, “version”: 53}
2022-07-25T18:47:57.414Z INFO preflight:localtime start checking local system clock with trusted satellites’ system clock. {“Process”: “storagenode”}
2022-07-25T18:47:58.231Z INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock. {“Process”: “storagenode”}
2022-07-25T18:47:58.231Z INFO Node 12dQqAuRRHQY3QnzCozVFev7sD9BnVay33z5HKr364rsxjqApdK started{“Process”: “storagenode”}
2022-07-25T18:47:58.231Z INFO Public server started on [::]:28967 {“Process”: “storagenode”}
2022-07-25T18:47:58.231Z INFO Private server started on 127.0.0.1:7778 {“Process”: “storagenode”}
2022-07-25T18:47:58.231Z INFO failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See UDP Receive Buffer Size · lucas-clemente/quic-go Wiki · GitHub for details. {“Process”: “storagenode”}
2022-07-25T18:47:58.785Z WARN contact:service failed PingMe request to satellite {“Process”: “storagenode”, “Satellite ID”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”, “error”: “ping satellite: check-in network: IP address not allowed: 192.168.0.200:28967”, “errorVerbose”: “ping satellite: check-in network: IP address not allowed: 192.168.0.200:28967\n\tstorj.io/storj/storagenode/contact.(*Service).requestPingMeOnce:194\n\tstorj.io/storj/storagenode/contact.(*Service).RequestPingMeQUIC:167\n\tstorj.io/storj/storagenode.(*Peer).addConsoleService:845\n\tstorj.io/storj/storagenode.(*Peer).Run:884\n\tmain.cmdRun:251\n\tstorj.io/private/process.cleanup.func1.4:372\n\tstorj.io/private/process.cleanup.func1:390\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.ExecWithCustomConfigAndLogger:93\n\tmain.main:479\n\truntime.main:255”}
You should use your external IP in the ADDRESS parameter.
2 Likes