The NeXT Horizon website has just had a major facelift. We've moved to brand new forum software which will allow us to serve you better. If you are an existing user, you will need to reset your password by clicking here. Please note that if you haven't received your password reset email within a couple of minutes then you should check your spam folder as it's likely to be in there!

Hallmark Node on Amazon EC2 ?

Discussion in 'Bounties And Give-Aways' started by AndreasKae, Oct 6, 2014 at 12:35 AM.

  1. Anyone successful with a hallmarked node on an Amazon EC2 instance?

    Mine is running - but not visible from the outside with

    "Failed to connect to node - is NHZ running? Did you open port 7774?"

    I did exactly the same that I did for an NHZ node running successfully on a DigitalOcean droplet, but Amazon EC2 seems to be somehow different:

    It has two IP addresses, a private which is only visible within the EC2 cloud, and an external one.
    I used that external IP address to create the hallmark. I always connect to the same external IP.
    I also checked that external IP by wget -qO- http://ifconfig.me/ip

    The other thing different is Ubuntu 13.10 (at Amazon) instead of Debian7 (at DigitalOcean)

    Not sure what to do now.

    Do I perhaps need an "Elastic IP Addresses"? http://aws.amazon.com/articles/1346
    I don't think so, because I already have a public IP address ... but who knows.

    Or do I have to create a special "security group" ?

    Anyone any experience with amazon EC2 ?

  2. n00bsys0p

    n00bsys0p Administrator

    Yeah I've used EC2 loads. Their firewalls are completely restrictive. It's quite a pain in the backside getting used to it, but it's very secure. Here's Amazon's guide on how to use their insane, but pretty awesome firewall.

    An elastic IP is only useful if you're planning on upgrading the rig. The IP you currently have will only be destroyed if you terminate the instance. Elastic IP allows you to connect a given static IP to any of your EC2 instances.
    AndreasKae likes this.
  3. Yes, I had to edit the 'security group'.
    The elastic IP is useful, because it seems to stay same after rebooting.
    Thanks a lot!

Share This Page