Constellation Network
IntroductionFundamentalsFor DevelopersNode Validators
  • Index
  • Validator Node Guides
    • πŸ’°Delegated Staking
      • What is delegated staking?​
      • For Node Operators
      • Understanding Delegated Staking
      • Prerequisites
      • Create Delegated Staking Configuration
      • First Time Configuration
      • Modify Existing Configuration
      • Add/Update Delegating Staking Parameters
      • Update Delegated Staking
      • Duplicate Update
      • Status Command
    • 🚧Build Your Node
      • Create Discord Account
      • πŸ—’οΈNode Operator Notes
      • βš™οΈNode Specifications
      • 🚧Generic Build a VPS Guide
      • ☁️Cloud Provider Specific
        • 🚧Build AWS EC2 Instance
        • 🚧Build DigitalOcean Droplet
        • 🚧Build Hetzner Server
      • πŸš‰First Time Connection Guide
      • πŸ’½The nodectl utility
      • Download nodectl
      • πŸ—οΈTurn your VPS into a Node
        • 🚩Node Prerequisites
        • πŸ‡Quick Install Guide
        • 🎨Normal Install Guide
        • πŸ› οΈManual Installation
      • πŸ†Authorize to Join Hypergraph or metagaph
    • πŸ’°Collateralize Your Node
    • 1️⃣First Time Cluster Connection
    • πŸ’«Enable Auto Restart
    • πŸ“‚Operational Guides
      • ♻️Restart Validator Node Guide
      • 🐎Upgrade Tessellation Quick Start
      • 🏭Upgrade Tessellation Guide
      • πŸ—οΈReinstallation Guide
      • ♻️Backup/Restore a P12 KeyStore
      • πŸš‹Migrate V1 to V2 - P12 Keystore
      • πŸ›«Upgrade nodectl Version
      • 🚨Alerting & Reporting Setup Guide
    • πŸ› οΈTroubleshooting Guides
      • πŸ—οΈTroubleshoot SSH Connection
      • πŸ’½Troubleshoot nodectl upgrade
      • ⛰️Troubleshoot EdgePointDown Message
      • 🚨Troubleshoot Node Alerting
  • πŸ‘‘MainNet
    • MainNet & IntegrationNet Quick Start Guide
    • 🚧Upgrade Tessellation to v3
    • 🦌Migrate an IntegrationNet Node to MainNet
  • πŸ₯…IntegrationNet
    • πŸ§ͺIntegrationNet Quick Start Guide
  • Metagraphs
    • πŸšͺDor metagraph
      • πŸšͺDor Validator Onboard Guide
      • πŸšͺUnderstanding Rewards
      • πŸšͺTechnical Procedures
        • πŸšͺBuild Dor Validator Node
  • πŸ“šReferences
    • πŸ“šnodectl Command Reference
    • Firewall Settings Table
    • πŸ”SSH Remote Access
      • πŸ”‘Create SSH Keys
      • πŸ“Upload SSH Public Key
      • πŸ”Securing SSH Access
      • ♻️How to SSH into VPS
    • 🍴Node Fork Types
    • πŸ—οΈP12 Keystore
    • 🏐Tarball
    • πŸ’»Virtual Private Server
  • GitHub nodectl utility
  • Lattice Dashboard
Powered by GitBook

Main

  • Website
  • Get DAG
  • Explore Projects
  • Partners

Socials

  • Telegram
  • Discord
  • X (Twitter)

Tools

  • Wallet
  • DAG Explorer
  • Coingecko

Β© 2025 CONSTELLATION NETWORK

On this page
  • Introduction
  • 🚨 Support Disclaimer
  • πŸ” Step 1: Clear the Alerting Cache
  • πŸ“¬ Step 2: Send a Test Report
  • πŸ“£ Step 3: Send a Test Alert
  • 🧾 Step 4: Review Logs
  • πŸ“₯ Step 5: Check Email Spam Filters
  • πŸ“± Step 6: Mobile SMS/MMS Alerting Considerations
  • πŸ†˜ Step 7: Seek Help (Last Resort)

Was this helpful?

Export as PDF
  1. Validator Node Guides
  2. Troubleshooting Guides

Troubleshoot Node Alerting

Diagnose Alert Delivery Issues for the Optional Alerting Extension in nodectl

Introduction

This guide provides a series of basic troubleshooting steps to help you resolve issues with the alerting module associated with the auto_restart feature in nodectl.


🚨 Support Disclaimer

Important

The alerting module is a community extension of nodectl and not officially supported.

Use at your own risk. Limited support is available, and advanced troubleshooting may not be provided.


πŸ” Step 1: Clear the Alerting Cache

Start by clearing the alerting module’s internal cache:

sudo nodectl auto_restart clear_alerts

This resets any internal flags that may be preventing alert dispatch.


πŸ“¬ Step 2: Send a Test Report

To test if the daily reporting mechanism works:

sudo nodectl auto_restart send_report

Check your inbox for the report. If not received, continue with the next steps.


πŸ“£ Step 3: Send a Test Alert

Trigger an alert manually:

sudo nodectl auto_restart alert_test

This simulates a node failure alert. Verify that the message is received by the configured email or SMS gateway.


🧾 Step 4: Review Logs

Check the nodectl logs for any errors related to alert dispatch:

sudo nodectl logs -l nodectl

Look for entries that may indicate connection failures, authentication errors, or message rejection.


πŸ“₯ Step 5: Check Email Spam Filters

If alerts are routed to a standard email inbox:

  • Check your Spam or Junk folders

  • Add the configured sender (e.g., your Gmail alert account) to your email whitelist or safe senders list

  • Create filter rules in your email settings to allow all mail from that address to reach your inbox

  • Confirm your email provider hasn’t rate-limited or blacklisted your alerting Gmail account


πŸ“± Step 6: Mobile SMS/MMS Alerting Considerations

If you’re routing alerts to a mobile number via email-to-SMS/MMS:

  • βœ… Ensure MMS is supported and enabled on your phone

  • βœ… Test sending a manual email to your mobile email address (e.g., 1234567890@vtext.com)

  • ⚠️ Contact your mobile carrier and request approval to receive messages from your node’s Gmail addressβ€”some providers block automated or high-frequency alerts

  • 🚫 Mobile providers may "black hole" repetitive or unauthenticated email messages to prevent spam


πŸ†˜ Step 7: Seek Help (Last Resort)

If you've exhausted all basic troubleshooting steps:

  • Join the Constellation Network Official Discord

  • Navigate to the appropriate validator support channel

  • Provide details such as:

    • Your nodectl version

    • Email provider used for alerts

    • Mobile provider (if applicable)

    • Relevant error logs or symptoms

PreviousTroubleshoot EdgePointDown MessageNextMainNet

Last updated 18 days ago

Was this helpful?

πŸ› οΈ
🚨