I can't connect to my system remotely. Why?

In case if you can't connect to the system there are plenty of possible reasons. With this guide we'll try to cover most common of them responsible for 90% cases in the field.
Note! This guide omits cases with incorrect credentials input. All clients return corresponding messages on such connection efforts.

Traditional port forwarding

In order to connect to Nx Media Server it's always been a connection options using TCP port forwarded with your router(or firewall settings) from you Media Server to the public web. If you can't reach Media Server with address <host_address>:<forwarded_port> please follow the steps below for the initial troubleshooting:

1. Check that Media Server Service is running. At the Server PC you can find information about that at:
   
   - Windows: traytool or Services list
   - Ubuntu: using terminal command $ps max| grep mediaserver 
   
   Please run service if necessary.
2. Check that server is running correctly:
   
   - Any OS with GUI: try to connect to Media Server Web-page from the Server PC using web-browser. For default installation url to be entered in address bar is http://localhost:7001. If browser asks the credentials -- test is passed. 
   - Headless Ubuntu Server: try to run terminal command $wget http://localhost:7001. If server is running correctly it will reply you with index.html file. In opposite case you'll get connection refusal.
3. Check that server has functioning networking. It must be reachable from your router(or any other host at the Local Network). Simple ping request is quite enough.
4. Check that your port forwarding settings are working as you expect. There are plenty on-line tools for that on the Internet now. Like ping.eu or yougetsignal.com where you can input remote address(ip or hostname) and port. If they say that port is open -- test is passed.
5. If you reached point 5 it's time to troubleshoot the client side. At first you need to check that client host has internet connection. One more thing -- firewall options must allow outgoing TCP connections to port 7001 of the remote host.
6. Check that Media Server is reachable from the client host using web-browser. If you were requested to input credentials -- all communication is processed correctly.

In case if all 6 checks are passed but you still can't connect using Nx Client -- there's likely some software issue which must be resolved by our tech guys. Feel free to assign a support ticket referring to this article.

Nx Cloud

With 3.0 version Nx team introduced new approach to reach and maintain the systems without necessity to struggle with router settings to forward ports. More information about new technology you can find at our Nx Cloud support article. But there are still points that can lead to connectivity lack:

1. Check that Media Server Service is currently running. At the Server PC you can find information about that at:
   
   - Windows: traytool or Services list
   - Ubuntu: using terminal command $ps max| grep mediaserver 
   
   Please run service if necessary.
2. Check that server is running correctly:
   
   - Any OS with GUI: try to connect to Media Server Web-page from the Server PC using web-browser. For default installation url to be entered in address bar is http://localhost:7001. If browser asks the credentials -- test is passed. 
   - Headless Ubuntu Server: try to run terminal command $wget http://localhost:7001. If server is running correctly it will reply you with index.html file. In opposite case you'll get connection refusal.
   
   
3. Check that server has functioning networking. It must be reachable from your router(or any other host at the Local Network). Simple ping request is quite enough.
4. Optional. Using another PC in the same LAN log in to Nx Cloud with Nx Client and check if your System has status "Cloud-Online"(blue cloud icon).
5. Nx Cloud requires both Media Server and Client hosts to be able to reach some ports of main Nx Cloud Portal. I.e. firewall must allow outgoing TCP and UDP connections from your server PC to nxvms.com ports(http and https to check system availability, service port to maintain Client-Server connection):
   
   - 80 -- conventional http port. Can be checked with just opening http://nxvms.com at web-browser from your server PC
   - 443 -- conventional https port. Can be checked with browser by opening: https://nxvms.com
   - 3345 -- Cloud Service port. Can be checked with any telnet client(e.g. in ubuntu terminal with command $telnet mediator.vmsproxy.com 3345). Needed only for 3.1 or older.
   
   
6. Check router NAT mode at both Server and Client hosts. Nx Cloud won't work if any of them works in Symmetric NAT mode.

See https://support.networkoptix.com/hc/en-us/articles/360010795813-Firewall-White-List as well