⛰️Troubleshoot EdgePointDown Message
Resolve IPv6-related Connection Issues on Your Validator Node
🧠 Understanding the Issue
The EdgePointDown
status typically indicates a failure in establishing communication between your node and the network’s edge points.
A known root cause is the system resolving outbound connections using IPv6 instead of IPv4, which can happen in scenarios such as:
The cloud provider defaults to IPv6 or uses IPv6-to-IPv4 translation
The network infrastructure between your VPS and Constellation’s edge points mishandles IPv6
DNS resolution or routing forces IPv6 where IPv4 is required for compatibility
⚠️ This guide addresses IPv6-related causes only.
As new root causes are discovered, this document will be updated.
♻️Backup/Restore a P12 KeyStore
Check IPv6 Status
sudo nodectl ipv6 status
Expected output:
--------- * IPV6 STATUS * ---------
Interface found ................... eth0
IPv6 sysctl Status IPv6 GRUB Status
enabled enabled
If you find IPv6
is disabled, you do not need to continue this troubleshooting guide. Please contact an administrator.
Disable IPv6 with sysctl
To restrict the system to use IPv4-only routing:
sudo nodectl ipv6 disable --ni --sysctl
This updates the system configuration to disable IPv6 via sysctl
.
⚠️ If either status is already disabled
, your issue is not IPv6-related.
Stop here and seek assistance from a Team Lead via the Constellation Network Official Discord.
Check IPv6 Status
⚠️ If either status is already
disabled
, your issue is not IPv6-related. Stop here and seek assistance from a Team Lead via the Constellation Network Official Discord.
Restart Auto Restart (Optional)
To ensure the monitoring service is in sync with the updated configuration:
sudo nodectl auto_restart restart
Conclusion
✅ Your node should now resume connection attempts using IPv4.
If the EdgePointDown
issue was caused by IPv6, it should be resolved.
If problems persist, please reach out to the Constellation Network support team or a Team Lead in Discord.
Last updated
Was this helpful?