og00r

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 52 total)
  • Author
    Posts
  • in reply to: Cannot get output for command: evalsha after resending #31267
    Avatarog00r
    Contributor

    Did you update from version 7.0.x to newest 7.0.x? Looks like some problem with update could you try make fresh install?

    1) Uninstall current NoMachine.
    2) Remove directories /usr/NX and /etc/NX
    3) Install newest NoMachine packages.

    Second point is really important.
    If for some reason reinstallation is not possible and if there exist file /usr/NX/etc/nodes.db then running command

    sudo /etc/NX/nxserver –updatedb

    could help. If there is /usr/NX/etc/nodes.db.backup instead, you could try to move file manually

    sudo mv /usr/NX/etc/nodes.db.backup /usr/NX/etc/nodes.db

    and then run

    sudo /etc/NX/nxserver –updatedb

    restart nomachine after that.

    sudo /etc/NX/nxserver –restart

    in reply to: Cannot get output for command: evalsha after resending #31226
    Avatarog00r
    Contributor

    Did you try already solutions from other manjaro topic?
    https://forums.nomachine.com/topic/connecting-to-manjaro-gnome

    I mean:
    1. Create a backup of nx PAM configuration (sudo cp -a /etc/pam.d/nx /etc/pam.d/nx.original). Then change /etc/pam.d/nx in this way:

    auth       include       system-login
    account    include       system-login
    password   include       system-login
    session    include       system-login

    2. Change DefaultDesktopCommand in /usr/NX/etc/node.cfg

    DefaultDesktopCommand “env DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus /usr/bin/startplasma-x11”

    3. Restart NoMachine:

    sudo /usr/NX/bin/nxserver –restart

     

    Point 2 is different than in mentioned topic, specially for KDE version

    If for some reason problem persist please enable debug logs, restart NoMachine (command from above point 3) and try to connect again with enabled logs. Gather logs and send them please. Article about enabling logs:
    https://www.nomachine.com/DT10O00162#1
    (Please restart NoMachine before point 2 in that article)

    in reply to: “Cannot log in with SSH” problem #31225
    Avatarog00r
    Contributor

    Please check article:
    https://www.nomachine.com/AR02L00785

    especially:

    2. You should find there the authorized.crt file. Create this file if it doesn’t exist. On Linux/Mac, this file needs to have permissions set to 0600.

    create authorized.crt file with correct permissions

    Avatarog00r
    Contributor

    Please enable the logs this way:
    https://www.nomachine.com/DT11R00182
    then restart the whole NoMachine with
    /etc/NX/nxserver --restart
    collect logs and send them (to forum[at]nomachine[dot]com, referencing the topic as subject) if the problem persists after restarting the machine.

    in reply to: AD authentication on Mac #29377
    Avatarog00r
    Contributor

    Could tell which version of Windows domain server are you using?

    And what values are set on mac osx in users and groups settings:
    Create mobile account
    Force local home directory
    ?

    Did you leave default values or did you edit them?

    in reply to: AD authentication on Mac #29217
    Avatarog00r
    Contributor

    I’m glad that it helps temporarly, but could you post your configuration that it can be reproduced and fixed correctly? What AD server is used? And is it default configuration on osx? Or something were changed?

    in reply to: NXD Service won’t start on MacOS 10.12.6 Sierra #26853
    Avatarog00r
    Contributor

    Only nxd process is affected? Are other processes running correctly?
    Could you paste output of ‘ps -ef | grep nx’?
    Also could you gather nxserver logs from the affected remote server?
    This article contains information how to do it correctly:
    https://www.nomachine.com/DT10O00163 (you can attach them here or send directly to forum[at]nomachine[dot]com).
    If possible please run nxserver –restart after enabling logs, then gather them.

    in reply to: “No available sessions on this server” on Mac #26852
    Avatarog00r
    Contributor

    one of them updated to Mac OS 10.15.4 a week ago

    Were you able to connect to that machine after system update, was any pop show up to allow nxnode process?
    The latest macOS requires some more permissions, are you able to reinstall manually NoMachine on those machines?
    Or is only ssh connection available right now? You can try do it with vnc as ” VNC is working on one of them”
    if you don’t have physical access to that machine.

    Also could you gather nxserver logs from the remote server so we can see whether the problem is with permissions on
    new macOS version or if problem is somewhere else? This article contains information how to do it correctly:
    https://www.nomachine.com/DT10O00163 (you can attach them here or send directly to forum[at]nomachine[dot]com).

    You can do it through ssh and if possible please run nxserver –restart after enabling logs.

    Could you also check if nxnode process (ps -ef | grep nxnode) is running for correct user? (by comparing user id for that process with
    logged user / root (if login window is active). Write the output here.

    in reply to: Cannot connect two machines on local network #25822
    Avatarog00r
    Contributor

    How exactly it looks? Is appear any error during connection? After or before login? Is machine available on list?

    Was machine reboot done after installation?
    Could paste here output of nxserver –status from both machines?

    We also ask to enable logs on server.cfg and node.cfg, then gather them after issue reproduction.
    For nxplayer logs please:
    click on Settings to open Player preferences and click on the Privacy tab
    select the Don’t delete log files on exit checkbox

    Here is article with details how to do it:
    https://www.nomachine.com/DT10O00163

    in reply to: Authentication failed (but only at one device) #25600
    Avatarog00r
    Contributor

    In received logs there are only logs from client side, which is not enough to proceed with problem.

    Please enable logs on server side reproduce the problem and send them if possible.
    Here is article how to do this:
    https://www.nomachine.com/DT10O00163

    At this moment all can I say, is that connection is closed after entering username to login procedure.

    Please ensure that account name is correct and user is active in system.

    in reply to: 6.9.2_1 does not seem to fix kde problem #24898
    Avatarog00r
    Contributor

    Can you try start session without dbus? Just change DefaultDesktopCommand in node.cfg to:

    DefaultDesktopCommand "/usr/bin/dbus-launch --sh-syntax /usr/bin/startplasma-x11"

    and try again

    also could you give us version of yours dbus-launch? and Manjaro version?
    Any logs in /var/log or journactl (if available)?

    in reply to: MacOS start NX server at boot time? #24347
    Avatarog00r
    Contributor

    Looks like it is a problem with the detection of the correct desktop owner on your machine, as there is no current workaround for such issue, we could prepare and send you patched package. Are you interested in receiving and testing it?

    in reply to: Login loop Ubuntu 18.04 #24305
    Avatarog00r
    Contributor

    To disable Wayland, restart of the machine is suggested.

    But can you paste output of
    /etc/NX/nxserver –version
    to ensure which version are you using?

    Also is it virtual session for that affected user? If yes can you try disabling automatic screen lock in operating system config?
    After this, creation of new virtual session will be requested.

    in reply to: MacOS start NX server at boot time? #24302
    Avatarog00r
    Contributor

    Logs don’t include the full problem (looks like could be enabled little to late), could you check next time on login window if:
    – nxserver –daemon is running (for example with ps -ef | grep nx)
    – then gather his pid and check if it is listening on localhost (command sudo lsof -p <pid of nxserver --daemon> | grep -a LISTEN)

    Also new set of logs with these informations would be needed, at the moment it looks like daemon is not running or is not accepting any connections.

    in reply to: Login loop Ubuntu 18.04 #24292
    Avatarog00r
    Contributor

    Few questions:

    – Is that login loop on ubuntu login window or do you mean login loop in nxplayer?
    – What version of NoMachine are you using?
    – Maybe session (or login window) is running on Wayland? (currently Wayland is not supported on VM)
    – Is there any information that login failed?
    – Is he trying to connect his own session or someone else’s session?

Viewing 15 posts - 1 through 15 (of 52 total)