Forum Replies Created
December 3, 2018 at 09:43 in reply to: How to set NX port on pre-existing AWS EC2 Ubuntu instance? #20667
I can still log in with ssh using the same public DNS name as I’m using when trying with NX, so the address cannot have changed. I’m not sure what you mean by session file. Can you explain? Where is this file located? Thanks.November 30, 2018 at 08:34 in reply to: How to set NX port on pre-existing AWS EC2 Ubuntu instance? #20657
I initially tried it with “Source” set to “Anywhere”. I’ve also tried it set to “MyIP”. In both cases there is a timeout.November 29, 2018 at 08:52 in reply to: How to set NX port on pre-existing AWS EC2 Ubuntu instance? #20635
Following up, regarding my Ubuntu 16.04 instance… I installed the Xfce desktop as described here: https://www.nomachine.com/AR11N00908&an=ssh%20key. But the same timeout problem remains, when I try to connect using the NoMachine app.November 29, 2018 at 08:51 in reply to: How to set NX port on pre-existing AWS EC2 Ubuntu instance? #20633
Thank you. I’m fairly new to AWS and didn’t realize I could use the console to do this. I’m still having trouble however….
After adding and setting up the security group+rule as you advise, when I try to use the NoMachine app on my local machine to connect, I get a timeout message. But yet I am able to ssh in to the same machine from a terminal. Can you advise on how to troubleshoot? This only disparity from your setup instructions here
and my own configuration (that I’m aware of) is that (1) my instance is Ubuntu 16.04, and (2) I did not go through the “Getting the VM desktop environment ready” part of the linked tutorial. Is there something akin to that, that I should install for Ubuntu? I did go through the subsequent tutorial step, installing the NoMachine x86_64 .deb package found here: https://www.nomachine.com/download/linux&id=1 on the instance.