irek

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 63 total)
  • Author
    Posts
  • in reply to: How long does a UPnP port take to open? #11606
    irek
    Participant

    NoMachine Server refreshes UPnP ports every 5 minutes, so in the case where NoMachine Server started before the router, you will need to wait until the router finishes boot up, and then about 5 minutes.

    However there is a way to “force” NoMachine Server to refresh ports by hand. Open a console as Administrator, go to the installation directory of NoMachine Server and run command

    nxserver --upnpmap

    in reply to: External Port #11526
    irek
    Participant

    Hello tweedyc,

    About issue with not seeing external IP on welcome page on Windows 7

    – Please check that UPnP is enabled on nxserver.

    Check the key ‘EnableUPnP’ in server.cfg if it is set to NX, if not set it and restart nxserver.

    – Can you please turn off any firewall/security applications such as Norton and others.

    We will need debug NoMachine Cloud server logs from Windows machine to investigate further. Please follow the instructions here:

    https://www.nomachine.com/DT07M00098#1

    And then please do those steps:

    As it can take some time to reply from the router, so after nxserver starts up check both way:

    – Start nxplayer and check welcome page to see if external IP shows up, if not close nxplayer and check again after some time.

    – Open CMD as administrator and call that command inside NoMachine installation directory

    ‘ nxserver –upnpstatus ‘

    Repeat that steps few times if external IP wouldn’t shows up.

    Send them to forum[at]nomachine[dot]com

    in reply to: Nxhtd start problem #10683
    irek
    Participant

    Hello Michael,

    there are generally 3 reasons for having this error message:


    NX> 500 ERROR: Support for HTTP server is not permitted on this server.

    1. Key ‘ClientConnectionMethods’ is disabled in server.cfg.
    2. Missing ‘HTTP’ parameter in the ‘ClientConnectionMethods’ key in server.cfg.
    3. License is not Cloud Server.

    So Val is right to suggest to check ‘ClientConnectionMethods’ in server.cfg

    Please be sure that ‘ClientConnectionMethods’ key is enabled and included ‘HTTP’, for example:


    ClientConnectionMethods NX,SSH,HTTP

    in reply to: Client.CRT file #10558
    irek
    Participant

    Hello Peter,

    as we checked the logs and the client.crt looks like certificate was wrongly added in client.crt.

    Please note that if you add ServerHost in SectionSession as IP then in client.crt file
    you have to add also ‘Host:<IP>’

    Similar situation apply if you add ServerHost in SectionSession as HOSTNAME then in client.crt file
    you have to add also ‘Host:<HOSTNAME>’.

    Even if HOSTNAME and IP address point to the same machine, you have to align client.cfg and cloud.cfg.
    That’s why in client.crt you can see already duplicated certificates for IP address ‘127.0.0.1’ and HOSTNAME ‘localhost.

    in reply to: Connection to the server was shut down #10389
    irek
    Participant

    Hello Peter,

    as we checked the logs and the client.crt looks like certificate was wrongly added in client.crt.


    4276 3592 16:02:13 565.711 Encryptor/Encryptable: ERROR! Failed to authorize the server certificate.
    Error: Failed to authorize the server certificate.

    Please take a look at file client.crt:


    Host:172.16.73.203—–BEGIN CERTIFICATE—–

    the HostName and certificate should be splited into 2 separated lines, so it should looks like:


    Host:172.16.73.203
    —–BEGIN CERTIFICATE—–

    Please correct client.crt file as shown above, and now it should work.

    in reply to: Connection to the server was shut down #10208
    irek
    Participant

    Hello Peter,

    unfortunately not all logs were sent, the most important ones were: nxerror.log and nxserver.log, which were missing.

    However, looks like certificate of MAC machine was not added correctly on Windows server.
    Please try to add again certificate as described in article:

    https://www.nomachine.com/AR07K00679

    If certificate was added incorrectly in nxerror.log you will see logs similar to those below:


    1812 10092 16:51:35 674.464 Encryptor/Encryptable: ERROR! Failed to authorize the server certificate.
    Error: Failed to authorize the server certificate.
    1812 10092 16:51:35 675.465 Channel/Channel: WARNING! Runnable DaemonReader failed for FD#768.
    1812 10092 16:51:35 675.465 Channel/Channel: WARNING! Error is 13, ‘Permission denied’.

    If still you cannot connect to MAC machine using Web Player, pleease send to us logs, and please be sure that all logs are added – especially nxerror.log and nxserver.log.
    also please send to us client.crt file from Windows machine


    %PROGRAMDATA%/NoMachine/nxhtd/.nx/config/client.crt

    and certificate taken from Mac OS, which were added to client.crt on Windows:


    Konsole output
    /Applications/NoMachine.app/Contents/Frameworks/etc/keys/host/nx_host_rsa_key.crt

    Send them to forum[at]nomachine[dot]com

    in reply to: Connection to the server was shut down #10185
    irek
    Participant

    Hello Peter,

    We will need debug NoMachine Cloud server logs from Windows machine to investigate further. Please follow the instructions here:

    https://www.nomachine.com/DT07M00098#1

    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:

    SessionLogLevel 7

    Send them to forum[at]nomachine[dot]com

    in reply to: Can NoMachine be restricted to ports 80 and 443? #9987
    irek
    Participant

    Hello Scott,

    I meant using the NoMachine Player (the native client) instead of the Web Player (the web application), regardless of what products you decide to install on client or server side. To use that, you would need to try the suggestion in that post.

    Regarding the further problem with the spinning connection, we will need debug NoMachine Cloud server logs to investigate further. Please follow the instructions here:

    https://www.nomachine.com/DT07M00098#1

    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:

    SessionLogLevel 7

    Send them to forum[at]nomachine[dot]com

    • This reply was modified 8 years, 1 month ago by irek.
    in reply to: Can NoMachine be restricted to ports 80 and 443? #9960
    irek
    Participant

    You can change the port where the Cloud Server is listening on from the Services panel in the Server preferences GUI:

    https://www.nomachine.com/DT11M00107#2

    You can also edit directly the configuration files. Assuming you want to change the default ports from 4080/4443 to 80/443:

    1. shutdown nxhtd

    #nxserver –stop nxhtd

    2. change configuration files:

    in htd.cfg:

    replace


    Listen 0.0.0.0:4080
    Listen 0.0.0.0:4443 https

    with


    Listen 0.0.0.0:80
    Listen 0.0.0.0:443 https

    – in cloud.inc


    <VirtualHost 0.0.0.0:4443>

    with


    <VirtualHost 0.0.0.0:443>

    and


    <VirtualHost _default_:*>
    RewriteEngine on

    ReWriteCond %{SERVER_PORT} !^4443$
    RewriteRule ^/(.*) https://%{SERVER_ADDR}:4443/nxwebplayer [R,L]
    </VirtualHost>

    with

    <VirtualHost _default_:*>
    RewriteEngine on

    ReWriteCond %{SERVER_PORT} !^443$
    RewriteRule ^/(.*) https://%{SERVER_ADDR}:443/nxwebplayer [R,L]
    </VirtualHost>

    3. start nxhtd

    #nxserver –start nxhtd

    Alternatively, you can use the NoMachine native client in that configuration by following the suggestion in this post:

    https://www.nomachine.com/forums/topic/changing-nx-port-number-from-4000-to-80#post-3616

    in reply to: Cloud Server reports "please connect to a Cloud Server" #9953
    irek
    Participant

    Hello Eliot,

    as we found in cloud.cfg, you added ‘NoMachine Terminal Server Node’ as a section”. You’ve added for example:


    SectionSession “Login Node 1″

    ServerHost 10.0.255.32
    ConnectionMethod NX
    ConnectionPort 4000
    ServerPath /etc/NX/nxserver

    EndSection

    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:


    SectionSession “Localhost”

    ServerHost localhost
    ConnectionMethod NX
    ConnectionPort 4000
    ServerPath /etc/NX/nxserver

    EndSection

    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.

    in reply to: Cloud Server reports "please connect to a Cloud Server" #9939
    irek
    Participant

    Hello eshelman,

    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:

    https://www.nomachine.com/DT07M00098#1

    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:

    SessionLogLevel 7

    Send them to forum[at]nomachine[dot]com

    • This reply was modified 8 years, 1 month ago by irek.
    in reply to: Cloud Server reports "please connect to a Cloud Server" #9917
    irek
    Participant

    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:

    https://www.nomachine.com/adding-nodes-to-enterprise-and-cloud-server-via-the-gui

    Did you follow these instructions to add your nodes?

    in reply to: 500 Internal Server Error #9547
    irek
    Participant

    Hello 00,

    We will need debug NoMachine server logs to investigate further. Please follow the instructions here:

    https://www.nomachine.com/AR07K00677
    Send them to forum[at]nomachine[dot]com

    Could you try to explain what issue do you have exactly, are you unable to connect to that server using Web Player, and what error do you have displayed in browser?

    Can you please check if nxhtd is running, by executing:
    ‘nxserver –status’ and provide the full output.

    Is it possible to connect/start WebPlayer on the server machine [connecting using  localhost/127.0.0.1 ]

    in reply to: Local works, but no Public/External IP #8746
    irek
    Participant

    Hello jvanc.

    Currently NoMachine tries to configure automatically a router to allow incoming connections. If it is successful, details of an IP and a port to use to connect are available in the Player GUI.

    Routers supporting UPnP or NAT-PMP are configured automatically to pass connections to NoMachine and all required informations are displayed at initial screen (Welcome to NoMachine).
    Routers not supporting UPnP or NAT-PMP and Firewalls have to be configured manually to pass traffic to port 4000 (NX protocol), 22 (SSH protocol on Linux/MacOSX) or (4022) (SSH protocol on Windows).

    Please check if both routers have enabled UPnP or NAT-PMP in case routers supports this, and enable it.
    In case it still doesn’t help, please provide information about model/type of each router to which host machine is connected.
    Can you also send us the logs from host/server machine: https://www.nomachine.com/AR10K00697 ?

    in reply to: Local works, but no Public/External IP #8302
    irek
    Participant

    It’s difficult to see where the problem might be, so to help us would you be interested in installing a debug package so that we can get detailed logs?Please send an email to forum[at]nomachine[dot]com and let us know. We will then send you instructions.

    Can you also send us the logs from host/server machine ? https://www.nomachine.com/AR10K00697
    and information about model/type of router to which host machine is connected.

Viewing 15 posts - 46 through 60 (of 63 total)