Merge pull request #176 from DigiNode-Tools/develop

v0.11.3 Release

Author: saltedlolly

diginode-help.json

@@ -11,8 +11,8 @@
     },
    	"diginodehelp3": {
         "title": "DigiNode Tip!",
-        "content": "To view a global map of DigiByte Nodes, visit this website: https://digibyte.io/nodes",
-        "url": "https://digibyte.io/nodes"
+        "content": "To view a global map of DigiByte Nodes, visit this website: https://opennodes.digibyte.link/",
+        "url": "https://opennodes.digibyte.link/"
     },
    	"diginodehelp4": {
         "title": "DigiNode Tip!",
@@ -23,5 +23,25 @@
         "title": "Need DigiAsset Support?",
         "content": "For help with creating DigiAssets, a good place to start is the DigiAssetX Telegram group here: https://t.me/digiassetX",
         "url": "https://t.me/digiassetX"
+    },
+    "diginodehelp6": {
+        "title": "DigiNode Tip!",
+        "content": "Are you having issues with DigiNode Dashboard? No colors? Flickering display? Misalligned borders? This is likely caused by the Terminal software you are using. For best results, use Windows Terminal (https://aka.ms/terminal) or iTerm 2 on macOS (https://iterm2.com).",
+        "url": "https://iterm2.com"
+    },
+    "diginodehelp7": {
+        "title": "DigiNode Tip!",
+        "content": "Are you interested to know what new features have been added to DigiNode Tools recently? You can view the release notes here: https://diginode.tools/release-notes/",
+        "url": "https://diginode.tools/release-notes/"
+    },
+    "diginodehelp8": {
+        "title": "DigiNode Tip!",
+        "content": "Do you also run a DigiByte node on your Mac or Windows PC? If so, you can test it using the same DigiByte port tester built into the DigiNode Dashboard. Find it here: https://diginode.tools/digibyte-port-tester/",
+        "url": "https://diginode.tools/digibyte-port-tester/"
+    },
+    "diginodehelp8": {
+        "title": "DigiNode Tip!",
+        "content": "DigiNode Tools can be used almost anywhere - install it on a Raspberry Pi on your local network, or on a VPS on the the other side of the world. DigiNode Tools makes it easy to install, monitor and manage a DigiByte Node wherever you need one. Learn more: https://diginode.tools",
+        "url": "https://diginode.tools"
     }
 }

diginode-setup.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 #
-#           Name:  DigiNode Setup v0.11.2
+#           Name:  DigiNode Setup v0.11.3
 #
 #        Purpose:  Install and manage a DigiByte Node and DigiAsset Node via the linux command line.
 #          
@@ -16,8 +16,8 @@
 #
 # -----------------------------------------------------------------------------------------------------
 
-DGNT_VER_LIVE=0.11.2
-# Last Updated: 2025-04-21
+DGNT_VER_LIVE=0.11.3
+# Last Updated: 2025-04-22
 
 # Convert to a fixed width string of 9 characters to display in the script
 DGNT_VER_LIVE_FW=$(printf "%-9s" "v$DGNT_VER_LIVE")
@@ -18799,7 +18799,7 @@ if [ "$ARGONFAN_INSTALL_TYPE" = "new" ]; then
     # Cloning from GitHub
     str="Cloning Argon One Daemon from Github repository..."
     printf "%b %s" "${INFO}" "${str}"
-    sudo -u $USER_ACCOUNT git clone --depth 1 --quiet https://github.com/iandark/argon-one-daemon $USER_HOME/argon-one-daemon 2>/dev/null
+    sudo -u $USER_ACCOUNT git clone --depth 1 --quiet https://github.com/kowalski7cc/argon-one-daemon $USER_HOME/argon-one-daemon 2>/dev/null
 
     # If the command completed without error, then assume IPFS downloaded correctly
     if [ $? -eq 0 ]; then

diginode.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 #
-#           Name:  DigiNode Dashboard v0.11.2
+#           Name:  DigiNode Dashboard v0.11.3
 #
 #        Purpose:  Monitor and manage the status of you DigiByte Node and DigiAsset Node.
 #          
@@ -47,8 +47,8 @@
 # The version number should be three numbers seperated by a period
 # Do not change this number or the mechanism for installing updates may no longer work.
 
-DGNT_VER_LOCAL=0.11.2
-# Last Updated: 2025-04-21
+DGNT_VER_LOCAL=0.11.3
+# Last Updated: 2025-04-22
 
 # Convert to a fixed width string of 9 characters to display in the script
 DGNT_VER_LOCAL_FW=$(printf "%-9s" "v$DGNT_VER_LOCAL")
@@ -3672,15 +3672,15 @@ if [ $TIME_DIF_10SEC -ge 10 ]; then
             TROUBLESHOOTING_MSG="10sec: startingup > running"
             DGB_STATUS="running"
 
-            # Get current listening port
-            DGB_LISTEN_PORT=$($DGB_CLI getnetworkinfo 2>/dev/null | jq .localaddresses[0].port)
-
             # scrape digibyte.conf
             scrape_digibyte_conf
 
             # query for digibyte network
             query_digibyte_chain
 
+            # query for digibyte listening port
+            query_digibyte_port
+
             # update max connections
             query_digibyte_maxconnections
 
@@ -3791,20 +3791,25 @@ if [ $TIME_DIF_10SEC -ge 10 ]; then
                 DGB2_TROUBLESHOOTING_MSG="10sec: startingup > running"
                 DGB2_STATUS="running"
 
-                # Get current listening port
-                DGB2_LISTEN_PORT=$($DGB_CLI -testnet getnetworkinfo 2>/dev/null | jq .localaddresses[0].port)
+                # if the primary node is running, we have just run all these checks so we don't need to do it again in the same loop
+                if [ "$DGB_STATUS" != "running" ] && [ "$DGB_STATUS" != "startingup" ]; then
 
-                # scrape digibyte.conf
-                scrape_digibyte_conf
+                    # scrape digibyte.conf
+                    scrape_digibyte_conf
 
-                # query for digibyte network
-                query_digibyte_chain
+                    # query for digibyte network
+                    query_digibyte_chain
 
-                # update max connections
-                query_digibyte_maxconnections
+                    # query for digibyte listening port
+                    query_digibyte_port
 
-                # update rpc credentials
-                query_digibyte_rpc
+                    # update max connections
+                    query_digibyte_maxconnections
+
+                    # update rpc credentials
+                    query_digibyte_rpc
+
+                fi
 
             fi
 
@@ -4011,8 +4016,8 @@ if [ $TIME_DIF_1MIN -ge 60 ]; then
     # Update primary DigiByte Node sync progress every minute, if it is running
     if [ "$DGB_STATUS" = "running" ]; then
 
-        # Get current listening port
-        DGB_LISTEN_PORT=$($DGB_CLI getnetworkinfo 2>/dev/null | jq .localaddresses[0].port)
+        # query for digibyte listening port
+        query_digibyte_port
 
         # Lookup sync progress value from debug.log. Use previous saved value if no value is found.
         if [ "$DGB_BLOCKSYNC_PROGRESS" = "synced" ]; then
@@ -4065,8 +4070,11 @@ if [ $TIME_DIF_1MIN -ge 60 ]; then
     # Update secondary DigiByte Node sync progress every minute, if it is running
     if [ "$DGB2_STATUS" = "running" ] && [ "$DGB_DUAL_NODE" = "YES" ]; then
 
-        # Get current listening port
-        DGB2_LISTEN_PORT=$($DGB_CLI -testnet getnetworkinfo 2>/dev/null | jq .localaddresses[0].port)
+        # if the primary node is running, we have just run all this checks so we don't need to do it again in the same loop
+        if [ "$DGB_STATUS" != "running" ]; then
+            # query for digibyte listening port
+            query_digibyte_port
+        fi
 
         # Lookup sync progress value from debug.log. Use previous saved value if no value is found.
         if [ "$DGB2_BLOCKSYNC_PROGRESS" = "synced" ]; then

docs/release_notes.md

@@ -1,5 +1,10 @@
 ## DigiNode Tools Release Notes
 
+DigiNode Tools v0.11.3 - 2025-04-30
+- New: Add a few more DigiNode tips.
+- Fix: Argon fan software should now install correctly.
+- Fix: Listening port should no longer display as "null" when the digibyte node itself is not self-reporting its local addresses and port. (It now reverts to getting this from digibyte.conf)
+
 DigiNode Tools v0.11.2 - 2025-04-22
 - Change: The Port Tester now gets re-enabled automatically 24 hours after the test was last successfully passed.
 - Fix: Hopefully the startup error that is occasionally been seen is now fixed.