Skip to main content

Connections fail or sessions dont complete

If your node receives connection attempts but sessions fail, or your node shows “Monitoring failed”, follow these steps to identify and fix the issue.

Written by Andzej Korkuz
Updated today

1. Check node version

Make sure your node is up to date.

Outdated versions can cause connection issues.

2. Identify the type of issue

Connection problems usually fall into one of these:

Can’t connect at all

  1. No sessions established

  2. Status shows Monitoring failed

  3. Often caused by Strict / Symmetric NAT

Can connect but no internet access

  1. Session starts but browsing fails

  2. Usually caused by DNS or firewall issues

Poor connection quality

  1. Slow speeds, disconnects

  2. Often network or ISP related

3. Run a connection test

From your MystNodes dashboard:

  1. Open node dashboard

  2. Click the three dots menu

  3. Select Test node

Expected:

  1. A session appears in NodeUI

  2. Status changes to Online in sometime

If not, Status remains Monitoring failed

4. Check NAT type

Run:

docker run -it --rm yarmak/natdisco

Expected: Open or Moderate NAT

If you see: Strict / Symmetric NAT → connections will fail

5. Fix NAT and connectivity

Enable UPnP

  1. Enable in router settings

  2. Restart node

Port forwarding

  1. Forward UDP ports: 56000 - 56100

  2. Assign a static IP

DMZ (last resort)

  1. Assign your node host to DMZ

  2. Use carefully (reduces network security)

6. Check firewall and system configuration

If connections are attempted but not completed, your firewall or system configuration may be blocking traffic.

  • Ensure UDP traffic is allowed

  • Ensure required ports are open

  • Check that forwarding is not restricted

For detailed steps, see:

7. Retest after changes

  1. Restart node

  2. Run Test node again

  3. Check if sessions appear


If the issue persists

Share with support:

  1. Node identity

  2. Node version

  3. Operating system

  4. Logs

Did this answer your question?