February 2, 2016 at 08:47 #9910
I have fresh installs of Cloud Server and Terminal Server Node that I’m trying to get connected. I’m able to add the Terminal Server Node to the Cloud Server (via the GUI), and I think the authentication/certificates look good. However, I’m not able to create a desktop session on the Terminal Server Node. A diagram of the network setup is shown in the attached image.
I am able to open the Cloud Server interface via a web browser. When I select the Terminal Server Node and click Connect, I see the following error:
To access desktops by web, please be sure you are connecting to a NoMachine Enterprise Server, to a Cloud Server or to a Quick Server.
Both servers are running CentOS 7 Linux with all the latest updates. NX server versions are:
Version 5.0.63 – NoMachine Cloud Server Subscription
Version 5.0.63 – NoMachine Terminal Server Node Subscription
The local client (running the web browser) is 64-bit Ubuntu 14.04LTS Linux using Google Chrome web browser Version 47.0.2526.106 (64-bit).
Cloud Server IP is 10.0.254.1
Terminal Server Node IP is 10.0.255.32
It is perhaps worth mentioning that the same error occurs when trying to connect to systems running NoMachine Enterprise Desktop (on Windows 8.1 with all updates). My understanding is that a Cloud Server should be able to stand in front of Enterprise Desktop systems and broker those connections.
Attachments:February 2, 2016 at 13:40 #9917
We understand that you have added multiple server hosts to the Cloud Server in the cloud.cfg. Can we see your cloud.cfg?
The message you got is the expected behaviour when you are trying to connect directly to the node rather than go via the Cloud.
Provided the nodes have been added correctly and you’re using the Cloud Server’s IP/hostname in the browser, you should see the nodes in the node list and then be able to connect.
To add them as nodes you should proceed with:
Did you follow these instructions to add your nodes?February 3, 2016 at 09:38 #9923
Yes, the Terminal Server Node was added as described in the NoMachine documentation. I have attached the cloud.cfg
Here are some additional details from the Cloud Server:
[root@nxcloud log]# /etc/NX/nxserver –nodelist
NX> 167 Node list:
Status Connection Node Type LB MS Weight Limit Label
——- ———- —————- —- — — —— —– —————-
running encrypted 10.0.255.32:4000 NX yes yes Login%20Node%201
running encrypted localhost:4000 NX yes yes
[root@nxcloud log]# ip a
3: ens4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 02:00:0a:00:fe:01 brd ff:ff:ff:ff:ff:ff
inet 10.0.254.1/16 brd 10.0.255.255 scope global ens4
valid_lft forever preferred_lft forever
inet6 fe80::aff:fe00:fe01/64 scope link
valid_lft forever preferred_lft foreverFebruary 3, 2016 at 14:45 #9939
from what you’e written it seems that you have added everything correctly. Send us the cloud.cfg to forum[at]nomahchine.com alon with the logs.
We will need debug NoMachine Cloud server logs to investigate further. Please follow the instructions here:
especially point 1.3:
1.3. If you have a Cloud Server installed and the problem affects sessions by the web:
Edit the /usr/NX/etc/cloud.cfg file. Uncomment and set the following:
Send them to forum[at]nomachine[dot]com
February 4, 2016 at 12:37 #9953
- This reply was modified 5 years, 1 month ago by irek.
as we found in cloud.cfg, you added ‘NoMachine Terminal Server Node’ as a section”. You’ve added for example:
SectionSession “Login Node 1″
Perhaps our documentation needs to clarify better that adding Sections to the cloud.cfg is not for the adding of nodes, but rather adding of
servers only, ie. you can redirect the session requests to other servers to which you have added nodes.
Take a look at the diagram here: https://www.nomachine.com/DT07M00096
To add nodes to your Cloud Server, you don’t need to change the Sections in the cloud.cfg. So please remove all of the sections, and leave only one – the default one:
Also, in logs we can see that you are accessing node ‘10.0.255.32’ from section “Login Node 1″ directly:
2016-02-02 04:23:09 186.977 31408 NXWEBPLAYER Create a new connection to [10.0.255.32:4000]
2016-02-02 04:23:09 886.724 31408 NXWEBPLAYER Parsing nxserver data [HELLO NXSERVER – Version 5.0.63 – NoMachine Terminal Server Node Subscription\nNX> 105 ]
2016-02-02 04:23:09 886.925 31408 NXWEBPLAYER Checking NoMachine Server license type: [NoMachine Terminal Server Node Subscription]
2016-02-02 04:23:09 887.999 31408 NXWEBPLAYER Sending to browser on FD#14: ERROR,To access desktops by web, please be sure you are connecting to a NoMachine Enterprise Server,.
Once you’ve corrected cloud.cfg as above, you will be able to login directly to NoMachine Cloud Server, and then [depending on nxserver configuration] when starting a new session you will be able to choose a node.February 5, 2016 at 12:08 #9959
Thank you for the kind assistance! Yes, you are correct that I misunderstood the instructions.
I will remove all other sections from the cloud.cfg (leaving only localhost).
This topic was marked as solved, you can't post.