Can’t connect. Fails after create new message prompt

Forums / NoMachine for Linux / Can’t connect. Fails after create new message prompt

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #31300
    Avatarbobsacket
    Participant

    Installed NoMachine yesterday.  Really liked it and it worked well.  Being who I am I made a change to the display encoding to see what happened (yeah, I did cuz I could and shouldn’t).  After making changes to mjpeg I wanted to change back to VP8, but nothing happened when I clicked the “changes disabled” button.  No password box appeared. After messing around I decided to just remove and reinstall and that’s when I couldn’t log on anymore.

    I see where it says session negotiation failed.  Not sure why though. Also saw server capacity: reached for user: user1.  There are no other connection and I’ve rebooted several times both between uninstall and reinstall and after reinstall.

    I’ve read some threads but they mostly talk about Wayland and I don’t think thats an issue with my install, but I never heard the term until I started reading on here.

    Any thoughts?  You probably want more info and I’m happy to provide it as long as I know what it is.  Thanks

    The server end I’m running Lubuntu based on Ubuntu 18.04.5 DE: LXDE WM: OpenBox

    and connecting from Mint 19.3 Tricia. DE: MATE 1.22.2 WM: Metacity  I’ve also tried connecting from a win10 machine.

    Here are the logs: (removed from body, attached as separate file)

    #31392
    Avatarog00r
    Contributor

    Hello,

    thank you for the feedback. Glad to know you like our product!

    Now onto your question. Yes, we do need more info, logs and command from the remote machine (Lubuntu).

    Could you send us logs from the server side and attach them here?
    Instructions on how to extract server logs are here: https://www.nomachine.com/DT10O00162#1

    Could you also paste you command DefaultDesktopCommand from /usr/NX/etc/node.cfg. ?

    Thanks!

    #31410
    Avatarbobsacket
    Participant

    Ok, hopefully these are the log files you wanted.

    #31406
    Avatarbobsacket
    Participant

    Thanks for the quick reply.  I’m about to go into a long work cycle so though I might not get the logs here quickly I will get them, Prob mon or Tues of next week if I can’t get to them today.

    One thing I did notice is that though I clicked the share at startup it does not show the desktop as shared.  I’ve restarted the service, shut it down and even rebooted.  Could that be the issue? (I will still be gathering logs)

    #31408
    Avatarbobsacket
    Participant

    Accidently closed tab so not sure if post went though.

    Busy week, I’ll try to get the logs, but I did notice that “desktop Not Shared” is on the server screen.  I’ve check the shared button, restarted the server.  No joy.  Stopped and restarted. No joy.  Looked that the server.cfg file and desktopsharing and desktopauthorizaton were disabled.  Changed them to match the server.cfg sample and restarted nomachine.  Still no joy and can’t connect.

    Probably, be Mon. or Tues. with logs if I can’t get to them today.

    Thanks for the prompt reply – I really enjoyed the short time I was using NM and would like to get it running again.

     

    #31428
    Avatarbobsacket
    Participant

    Here’s the node.cfg that I couldn’t attach.

    #31480
    Avatarog00r
    Contributor

    Could you try my solution from this post:

    Cannot get output for command: evalsha after resending

    that one with sudo /etc/NX/nxserver –updatedb
    or
    with fresh reinstall and remove /usr/NX

    If nothing helps, please let me know.

    #31511
    Avatarbobsacket
    Participant

    Solved.  While waiting for answers I uninstalled NM like before, but this time I scoured the system for directories that were not removed and deleted them.  Seems a few nx directories are left after uninstall on my system.  Then did a fresh install and all is well.

    #31570
    Avatarbobsacket
    Participant

    Thanks og00r,

    I didn’t remove the nx directories last uninstall and reinstall cycle and I think that was the problem.  Well, not what caused the issue but what kept the reinstall from correcting it.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.