Stopped working in Ubuntu after reboot

Forums / NoMachine for Linux / Stopped working in Ubuntu after reboot

Tagged: ,

  • This topic has 4 replies, 2 voices, and was last updated 3 years ago by AvatarMth.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #17221
    Avatargamaquif
    Participant

    The setup was working just fine out of the box, after rebooting the Ubuntu machine, that changed. I can’t fully successfully connect to the NoMachine server even from within the local network. When I open the NoMachine client, it finds the computer in the local network, next I click connect, then it asks me for authentication, it seems to be successful, then I get the usual menu prompts for setting the session, then just a white screen. It retries 3 times and it then eventually fails with error code “Error is 138: connection timed out”. I have the logs ready to provide them and have also attached them to this threat. Ubuntu version is 16.04 and NoMachine is on version 6.0.66. Any suggestions of where to look?

    #17270
    AvatarMth
    Contributor

    Hello.

    The first thing that comes to mind after seeing the logs is the problem with localhost entry in /etc/hosts file.

    NoMachine uses localhost to connect locally via loopback device, so please make sure the localhost entry points to a loopback address, for example the line in /etc/hosts could look like this:

    127.0.0.1  localhost

    Please let us know if this does not help. If it doesn’t, more info about your network configuration would be useful, such as content of /etc/hosts/ and output of ifconfig.

    #17282
    Avatargamaquif
    Participant

    Thank you for the response, I have checked the /etc/hosts file and the mapping looks ok. See attached. I also uninstalled and reinstalled NoMachine and the issue persists.

    Attachments:
    #17284
    Avatargamaquif
    Participant

    See attached the output of ifconfig.

    #17303
    AvatarMth
    Contributor

    Hello

    Thank you for cooperation in this matter. Can you please try attaching from the problematic machine to itself using nxplayer?

    Please use the ‘NX’ protocol and ‘localhost’ as the host name in nxplayer application.

    Please check if something changes in those circumstances and send us the logs from after this attempt as you did in your first post.

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

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.