Feat: (Health check) Check alt_ip if web domain is not accessible

[graycraft]

Task check list

• Test cases passed
• Verbose logging ([Feat] Add "Verbose logging in Console" in developer mode #867): Make “Status updated” at the debug level, everything else at info

Task description

To test this complex algorithm clearly, in the src/config/development.json leave only one list with one entry.
There are 3 possible cases, let's take a look at the example of ADAMANT nodes:

1. Domain is available, use domain.

{
  "adm": {
    "nodes": {
      "list":[
        {
          "url": "https://debate.adamant.im",
          "alt_ip": "http://95.216.161.113:36666"
        }
      ]
    }
  }
}

2. Domain is unavailable, try to use IP.

{
  "adm": {
    "nodes": {
      "list":[
        {
          "url": "https://abc.adamant.im",
          "alt_ip": "http://95.216.161.113:36666"
        }
      ]
    }
  }
}

3. Domain is unavailable, IP is unavailable.

{
  "adm": {
    "nodes": {
      "list":[
        {
          "url": "https://abc.adamant.im",
          "alt_ip": "http://123.123.123.123:36666"
        }
      ]
    }
  }
}

Remember to filter out log messages and leave only console.info

Test cases

url: tauri.adm.im
alt_ip: 154.26.159.245:36666

The application tries a health check (api/node/status) on the domain tauri.adm.im.

a) Domain is accessible

• Save this state, and all subsequent requests (both health checks and data requests) go to tauri.adm.im.
• The "by domain" status is kept until the page is reloaded or the checkbox is toggled.
• If later a health check request fails, the node is considered (temporarily) offline, but health checks continue as before.
  This is not a node ban — the node may be temporarily offline.

b) Domain is not accessible

• The application tries a health check (api/node/status) on IP 154.26.159.245:36666.
• If the IP is accessible, save this state and all subsequent requests go to 154.26.159.245:36666.
• The "by IP" status is kept until the page is reloaded or the checkbox is toggled.
• If later a health check request fails, the node is considered (temporarily) offline, but health checks continue as before.
  This is not a node ban — the node may be temporarily offline.

c) Neither domain nor IP is accessible

• We cannot be sure the node is unavailable. It may be a temporary node or internet failure.
• There will be no "by domain" or "by IP" status.
• Start again from step 1.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
adamant-im	Ready	Preview, Comment	Feb 20, 2026 11:16am

[github-actions]

Deployed to https://msg-adamant-pr-768.surge.sh 🚀

[graycraft]

Feat: (Health check) Check alt_ip if web domain is not accessible

[dvelikiy]

The logic becomes more complex, it'd be good to write tests for different use-cases.

[adamantmm]

@S-FrontendDev @bludnic
Please review

[metalisk]

Connection selection and persistence rules (for nodes with url + alt_ip):

1. Start by checking the domain (url).
2. If the domain check succeeds first, lock the connection type to DOMAIN for the current session.
3. If the domain check fails, immediately try alt_ip in the same health-check cycle.
4. If the alt_ip check succeeds first, lock the connection type to IP for the current session.
5. Once the connection type is determined (DOMAIN or IP), do not switch it during the session.
6. If later requests/health checks fail after the type is determined, keep retrying the same determined type and treat the node as temporarily offline when checks fail.
7. If neither domain nor alt_ip is reachable while the type is still not determined, keep retrying both in this order on each cycle: DOMAIN -> IP, until one succeeds.

Session scope: keep the selected type until page reload or until the node is toggled off/on by the user.

[Copilot]

Pull request overview

Copilot reviewed 97 out of 98 changed files in this pull request and generated 9 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[al-onyxprotocol]

@cursor review

[Copilot]

Pull request overview

Copilot reviewed 101 out of 102 changed files in this pull request and generated 5 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Successfully tore down https://msg-adamant-pr-768.surge.sh 🥲