No routing or no internet access

Use one test device and change one layer at a time. This keeps a failed check useful instead of creating several interacting variables.

Protect the management path

Keep one device on a normal, unisolated LAN path. Do not enable strict kill-switch protection or move the only management device into a test rule until you have another way to reach the router.

1. Confirm service status

Open the SoloIP status page and wait for running. If the service is starting, restoring, or showing an error, collect the visible message before changing routing rules.

2. Confirm that a rule matches

Check the test device address, rule enabled state, target, and rule order. Start with one specific IP rule. Remove a duplicate or broad rule that could take precedence during the test.

3. Confirm that the node is usable

Run the node check. Inspect the selected node or group member, the outbound interface, and any relay node. A node that is saved but fails diagnostics cannot carry the rule.

4. Reproduce with one device

Disconnect and reconnect the test device if its address changed. Test one public IP endpoint and one ordinary website. Do not expand the rule to a subnet until this single-device path works.

5. Return to the last known-good state

Disable the newest rule or restore the last configuration backup. Verify local direct access, then add back one change and test again.

Information to send support

Include the router model, iKuai version, SoloIP version, service status, rule target, node diagnostic result, test device IP, public result, and the time of the failure. Do not include node passwords, API tokens, or private configuration backups.