#Status: Waiting-For-Network issue
43 messages · Page 1 of 1 (latest)
I have the same problem
i see this error while i did not stop the node it stoped with error;"Node exited with the following message:
invoke-exit: In apoptosizeSelf. Apoptosized within fetchLatestRecord() => src/p2p/CycleCreator.ts exitUncleanly"
is it uptodate?
Sphinx 1.10.0 faced performance issues with many failed transactions. The team has identified the issue and preparing for a smooth update to Sphinx 1.10.1 to improve network performance and stability.
More info: #📢・announcements message
I am facing the same issue "Status: waiting-for-network"
CLI/GUI Running Version: 1.2.1 / 1.2.0
CLI/GUI Latest Version: 1.2.1 / 1.2.0
Validator Running Version: 1.10.2
Active Network Version: 1.10.2
Validator Minimum Version: 1.10.2
what can be done to fix it ?
After some time the node stopped with below error:
Node exited with the following message:
Unable to access external or internal ports. Please provide proper port access to the external and internal ports of shardeum (9001 / 10001 are the defaults)
I have changed the ports in the settings as per the youtube video, should they be reverted back to 9001 and 10001
I am facing the same issue "Status: waiting-for-network"
CLI/GUI Running Version: 1.2.1 / 1.2.0
CLI/GUI Latest Version: 1.2.1 / 1.2.0
Validator Running Version: 1.10.2
Active Network Version: 1.10.2
Validator Minimum Version: 1.10.2
I have tried several resets and unfortunately still nothing..Have you managed to solve the problem?
No, its not fixed
I have stopped the instance, since this issue is not fixed.
@visual bramble Any remedy to this issue ?
Stop your node and start it again. You can also reinstall your node. Please note: 1.10.3 will be launching soon and will fix all current issues.
Restarted the node and now have new issue https://discord.com/channels/933959587462254612/1221188618811609109
Let me check.
@visual bramble Did you find anything ?. I am planning to stop the instance since its clocking the usage.
I have replied here: #1221188618811609109 message
@visual bramble Back to square one: "Node exited with the following message:
Unable to access external or internal ports. Please provide proper port access to the external and internal ports of shardeum (9001 / 10001 are the defaults)".
Do I need to wait for the release of the new version 1.10.3 ?.
Please wait for the new update release.
ok
Should I stop the instance until then to stop the usage clock ?.
should I remove the staking before closing the instance ?.
If your node is not working properly, you can stop your instance and wait for the next update to fix the issues.
@visual bramble Node restarted and added stake again today but still the same issue. Node exited with the following message:
Unable to access external or internal ports. Please provide proper port access to the external and internal ports of shardeum (9001 / 10001 are the defaults)
should the port number changes in spheron be reverted back to 9001 / 10001 ?.
CLI/GUI Running Version: 1.2.1 / 1.2.0
CLI/GUI Latest Version: 1.2.1 / 1.2.0
Validator Running Version: 1.10.3
Active Network Version: 1.10.3
Validator Minimum Version: 1.10.3
Check if port 9001 is open on your node by accessing http://<your-node-ip>:9001/nodeinfo from an external network. If you can't access it, your port might be closed. Ensure your firewall allows traffic on port 9001 and your router is configured to forward this port to your node.
@visual bramble Node exited with the following message:
Unable to access external or internal ports. Please provide proper port access to the external and internal ports of shardeum (9001 / 10001 are the defaults)
I have changed these ports in the spheron settings to the port numbers as shown in the youtube video, but why this error coming ?.
Tell me why I can’t connect the shardeum sphinx 1.X network to OKX WALLET?
That network is closed. Import your wallet to metamask and Add Atomium network from our Website.
Add network guide: #💬・itn-discussion message
why?
in the faucet similar