Fail to connect with AWS EC2

Forums / NoMachine for Linux / Fail to connect with AWS EC2

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #36706
    JoeW
    Participant

    I’ve been using NoMachine to connect to my AWS EC2 Ubuntu system for a while but recently I cannot do so.

    Now the error is shown as:

    “A connection timeout has occurred while trying to connect to ‘ec2-xx-xxx-xxx-xx.us-east-2.compute.amazonaws.com’ on port ‘4000’. The issue could either be caused by a networking problem, by a firewall or NAT blocking incoming traffic or by a wrong server address. Please verify your configuration and try again.”

    Does anyone know where the potential issue is? from the NoMachine or AWS. I did not make any changes on both sides and the connection works fine a few weeks ago.

    Thanks!

    #36743
    Tom
    Participant

    Hello,
    check with the Security Group if there is a rule to open port 4000 and SSH port.

    Perhaps you deleted it by accident.

    Are you connecting to NoMachine through the NX protocol or the SSH protocol?

    Check Nomachine status  with command „/ usr / NX / bin / nxserver –status” 

    You should see

    NX> 111 New connections to NoMachine server are enabled.

    NX> 161 Enabled service: nxserver.

    NX> 161 Enabled service: nxnode.

    NX> 161 Enabled service: nxd.

    I understand this is a VM which has been working for a while and was previously accessed via NoMachine?

    Regards,
    Tom

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

This topic was marked as closed, you can't post.