If your Mysterium node is having network connection issues of any kind, we’ll point you to the best solution for the specific type of connection issue you’re experiencing.
Important! Before you begin troubleshooting your connection, make sure that your node version is up to date. If not, follow our instructions to update it.
Network connection issues generally fall into one of three categories:
Can’t connect: The peer can't establish a connection, or can’t connect to the service. Most likely, you are behind Strict or Symmetric NAT. In such case, service provider's status will be marked as "Monitoring failed".
Can connect but unable to browse the internet: Although the peer is able to connect and establish a peer-to-peer communication channel, it's not possible to browse the internet due to DNS or firewall configuration issues. In such scenario, the service provider's status will be marked as "Monitoring failed" too.
Poor connection quality (low quality rate): Although the peer is able to connect, there are connection quality issues, such as poor streaming quality, random disconnects, or slow performance.
To begin troubleshooting, find the section below that best describes the type of connection issue you’re experiencing, then follow the steps provided:
MystNodes connection test
To trigger a connection check manually, log in to your Mystnodes.com account, go to your node's dashboard where you will find the three dots button next to each provider identity. Clicking the button and selecting "Test node" will force our monitoring agent to connect to your active node service. You may also use this feature to check and verify your node's connectivity after configuration changes. The monitoring agent should connect to your node within a few minutes of clicking the "Test node" button.
There are no strict limits for how many times you can perform this check (1 check per 10 minutes is allowed), however manually triggered connection checks do not perform data transfers.
If the connection test is successful, a new session with a few megabytes of data transferred should appear on your NodeUI dashboard. After a short period of time, your node status should switch to Online. If the connection test is not successful, there will be no earnings and no significant data transferred displayed in UI. In such case, node status won't change and will keep "Monitoring fail" status.
Testing your NAT type
Your NAT type affects your ability to connect with other peers in Mysterium Network. Run NAT behaviour probing test inside docker:
docker run -it --rm yarmak/natdisco
It will check your NAT type or after you’ve adjusted something on your home network. Run this utility after each troubleshooting step you try to see if it results in a Moderate or Open NAT type, which would resolve your issue.
Troubleshooting "Monitoring failed"
(Note: Do not use a combination of UPnP, port forwarding, or DMZ when configuring your Mysterium node connectivity. Make sure these are all disabled before moving forward.)
Enabling UPnP
UPnP is what your host device uses to set up your router for peer-to-peer communication. Make sure that your router has the latest manufacturer update. If you want to enable UPnP on your router, the setup process is simple. Steps will vary between router models, though we've provided a general guideline of what to follow.
Just follow these steps:
Navigate to your router login page. (For more details on logging in to your router, search online for guides related to your specific model.)
Log in to your router using the required credentials.
Navigate to the UPnP menu on your router. (This action once again varies between models (NAT settings, Advanced settings), so search for specifics on your router.).
Enable UPnP.
Save your changes.
Open the NodeUI dashboard.
Click the Settings > Avanced tab.
Under NAT traversal order, drag items to reorder based on your configuration. Saves changes. Restart node service.
Open the mystnodes.com dashboard and "Test node" again. If the connection test is successful, a new session with a few megabytes of data transferred should appear on your NodeUI dashboard. After a short period of time, your node status should switch to Online.
If the above steps didn't work or UPnP isn’t supported on your gateway/router, you can also try using the router’s DMZ or Port Forwarding features.
Setting up port forwarding
These steps will guide you through the process of configuring port forwarding, though exact steps may vary between router models and manufacturers.
Note down the IP address of your host machine running the node.
Navigate to your router login page. (For more details on logging into your router, search online for guides related to your specific model.)
Navigate to the port forwarding section on your router.
Manually assign an IP address to your host machine running the Mysterium node using the previously fetched IP.
Enter the range of UDP ports: 56000-56100. Save changes.
Open the NodeUI dashboard.
Click the Settings > Avanced tab.
Under NAT traversal order, drag items to reorder based on your configuration. Saves changes. Restart node service.
Open the mystnodes.com dashboard and "Test node" again. If the connection test is successful, a new session with a few megabytes of data transferred should appear on your NodeUI dashboard. After a short period of time, your node status should switch to Online.
If you still experience issues, we recommend setting up the DMZ.
Setting up DMZ
With most modern routers, setting up the DMZ is relatively simple. Although steps will vary between router models, we've wrapped up a general guideline of what to expect.
Follow the steps below to set up DMZ:
Note the IP address of your host machine running the Mysterium node.
Navigate to your router login page. (For more details on logging into your router, search online for guides related to your specific model.)
Manually assign an IP address to your host machine running the Mysterium node using the previously fetched IP.
Navigate to the DMZ menu on your router. Enable it.
Enter your host device assigned IP address to place the console in the DMZ.
Note! The DMZ can have a major impact on security if not protected properly. In the event that a hacker gains entry to a file server in the DMZ, they may be able to access and download sensitive data and trading partner files that were placed there. Even encrypted files can be at risk to high-grade attackers if keys or passwords are compromised. There’s also a strong likelihood that any user credentials, certificates, or whatever else is needed for authentication could be maintained in the DMZ, increasing vulnerability. Use it at your own risk!