Put nxhtd (HTTPS server) on a distinct machine ?

[Steve92]

Hello,

For Enterprise Desktop, would it be possible to put nxhtd (HTTPS server) on a distinct machine ?

[ VM_A : nxhtd ] <==== NX ====> [VM_B : nxd]

Is there a config file for nxhtd where I can add a line to make it point to VM_B:4000 ?

..or nxhtd and nxd must be on the same machine ?

Thanks!

Regards,

Steve.

 

[Steve92]

I found these 2 very interesting links :

NoMachine – How To Configure A NoMachine Server V. 6 Or Later To Connect Web Sessions On Localhost Or On Different Hosts – Knowledge Base

NoMachine – Use Your Own Apache Web Server To Run NoMachine Sessions On The Web – Knowledge Base

but I had a quick look (too quick?) at this guide

NoMachine – NoMachine Enterprise Desktop – Installation And Configuration Guide – Knowledge Base

and I didn’t find a way to install only nxhtd on VM_A and only nxd on VM_B.

How can we proceed ? Is there an installer allowing to choose what component we need to install on each machine ?

Thank!

 

Steve.

 

[Steve92]

Hello,

I read again the page “Use Your Own Apache Web Server…”.

If I well understand the chain of components is:
[ Browser ] <= HTTPS => [ nxhtd ] <= ? => [ nxwebplayer ] <= NX/SSH => [ nxserver ]
Is it correct ? If not, what is the right one ?

How [ nxhtd ], the web server, communicates (protocol, port) with [ nxwebplayer ], the web app. ?

Must [ nxhtd ] and [ nxwebplayer ] be on the same machine ?

Thanks,

Regards.

Steve.

[Britgirl]

 

Hi,

there are currently no options to install “only nxhtd” or “only nxd”, but putting the NoMachine Web server on a different machine is definitely possible by design. Simply install the NoMachine package you’re interested in adopting which includes the web server (e.g., Enterprise Desktop, Workstation, any other Enterprise-oriented product etc) on both machines [VM_A, VM_B].

Then, configure VM_A according to the instructions in the NoMachine guide:

“How to configure a NoMachine server to connect web sessions on localhost or on different hosts”
https://kb.nomachine.com/AR06P00984

The Webplayer on VM_A will connect exclusively to the nxserver [on nxd port ] on VM_B.

Additionally, you can limit nxserver on that host to allow only HTTP  connections, which will disable NXD and SSH connections, preventing the NXD process from starting.

To do that, modify the “server.cfg” file:

”
ClientConnectionMethods HTTP
”

To prevent “nxnode” from starting on that server, modify the “server.cfg” file:

”
AvailableSessionTypes “”
“

[Irek]

Hello Steve92,

1) the flow would be like:

[ Browser/JS ] <= HTTPS => [ nxhtd / nxwebplayer ] <= nxd => [ nxserver ]

2) NX WebPlayer is a CGI

3) Yes, nxhtd and nxwebplayer have to be on the same machines.
If you replace nxhtd with “Your Own Apache Web Server” it still have to be on the same machine as nxwebplayer.

[Author]

Posts