Forum Replies Created
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.
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.
Hello once again. You wrote that you can ssh to the remote machine with these keys which means that .ssh directory must be there.
Once you are connected to EC2 Ubuntu via ssh, you can use ls -la to list all directories (including hidden) and then navigate to .ssh or use cd /home/YOURUSERNAME/.ssh command. It will take you directly to .ssh directory. Then try to proceed all the steps from tutorial.
What version of NoMachine are you using?
using the same steps in the tutorial, we tried to replicate your problem and were able to connect to an AWS EC2 instance (Ubuntu 16.04).
After installation of NoMachine on Ubuntu, I did have to create the .nx directory since it was not created automatically. So, after you connect to your instance via ssh and install NoMachine, you might need to do the following:
– create .nx directory manually (mkdir .nx)
– create config directory inside .nx (mkdir config)
– create file authorized.crt (touch authorized.crt)
– view content of directory .ssh/authorized_keys and append it to .nx/config/authorized.crt (cat ~/.ssh/authorized_keys >> ~/.nx/config/authorized.crt)
After you do this and follow the rest of instructions from tutorial you should be okay and able to connect. Let us know if it worked for you. Good luck.
GreetingsAugust 18, 2017 at 11:42 in reply to: Connecting to a NoMachine server that is under a VPN #15543
It looks more like a matter of VPN settings than NoMachine configuration. You wrote that when the server machine is off the VPN, you can connect properly and you have issues only when VPN is used.
Please explain what exactly happens. You have your Dell machine connected via VPN and when you are trying to connect from your Mac to Dell, NoMachine refuses connection? Or you are connected from Mac to Dell and then, when you connect Dell to VPN connection between Mac and Dell breaks down? When your Dell connects via VPN it recieves a new IP address and this migh be a reason. Also, do you establish connection to Dell machine with ethernet or WIFI? First thing you might want to do is try to use ifconfig and check IP before you use VPN and after you do it. You can also try to ping Dell’s IP from your Mac before and after switching VPN on.
We tested both options (UEFI and BIOS) in our lab finding no serious differences in terms of speed and quality of work. Are you sure that UEFI/BIOS is the only difference in settings between these machines? Did you try changing boot settings on the same machine to verify what happens? Assuming that neither network or server is a problem, as you have stated, it’s hard to define what affects weak performance. Please write something more about your configuration, so we can help further.