- This topic has 1 reply, 2 voices, and was last updated 6 years, 1 month ago by
.
-
Posts
-
NoMachine version 6.2.4_1
OS: AWS EC2 Ubuntu 16.04 server
GUI: Ubuntu-desktop
Client for AWS access: Windows 8.1 with NoMachine installed and updated. On Windows is giving error 138, the connection has expired.
I followed the tutorial as presented here on the NoMachine website, and I am not getting Windows access to a server with Ubuntu-desktop, in AWS.
The folder was created inside the user ubuntu .nx / config / authorized_crt – where the latter was renamed from authorized_keys from inside the .ssh folder
I need to create a desktop in the cloud within AWS to work with a pdv system, where my clients would access from their computer through the NoMachine client.
The error log displays the following errors (removed from body and attached as separate document by the Administrator)
Help.
In order to help you with your issues we replicated all steps from this tutorial: https://www.nomachine.com/accessing-your-remote-linux-desktop-on-amazon-elastic-compute-cloud-via-NoMachine and connected without any problems.
You wrote:
The folder was created inside the user ubuntu .nx / config / authorized_crt – where the latter was renamed from authorized_keys from inside the .ssh folder.
It seems that it might be a reason why your connection is not working properly. You need to make sure that there is .nx/config/authorized.crt with ssh key copied into it (cp -p .ssh/authorized_keys .nx/config/authorized.crt). Also, make sure that you added additional TCP rule for port 4000 during configuration of Security Group on AWS EC2.
Please let us know if it helped.
Greetings.
This topic was marked as solved, you can't post.