Web UI Troubleshooting

The Web UI cannot connect

• Confirm that the endpoint includes http:// or https://.
• Open the node health endpoint from the same network.
• Confirm that the node's CORS allowlist contains the exact Web UI origin.
• Check for certificate warnings or mixed-content errors. An HTTPS Web UI cannot call an insecure HTTP endpoint in normal browser configurations.

The height is unknown or stops changing

The node may be unavailable, syncing, or no longer receiving committed blocks. Reconnect, then ask the network operator to check node health and consensus status if the condition persists.

Data is present but a payload is unavailable

NOOSChain separates consensus state from payload availability. The connected node may not hold the encrypted payload, or your identity may not have access. This is not necessarily a chain consistency failure.

A transaction is rejected

Review the returned error before signing again. Common causes include an invalid signature, insufficient permissions, a stale identity nonce, malformed fields, an inactive contract, or a state precondition that has changed.

A transaction remains in the mempool

Mempool acceptance is not commitment. Wait for the network to produce another block. If the transaction remains pending, contact the operator with its full identifier and the endpoint URL—never send a private key.