Date: Tue, 10 Dec 2013 07:10:00 -0600 From: David Noel <david.i.noel@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: FreeBSD on EC2 Message-ID: <CAHAXwYCiMHOerFYghUYOOD8mLorv5hEmj-M2oGASYhnz1CvOtw@mail.gmail.com> In-Reply-To: <CAHAXwYDjyZXPO0BdzaMo_Mzt0MBCWgZnWEtot4MDfag-ADvh7w@mail.gmail.com> References: <CAHAXwYDysqHKxQXhQe6g7zRq086zGafrXcm_5ZBcCLjbcy2DUA@mail.gmail.com> <CAHAXwYCkwHfGqCHU1RRnkmsi26DmaFui5X9vaf=ZRL7Uj%2BPx5Q@mail.gmail.com> <CAHAXwYDjyZXPO0BdzaMo_Mzt0MBCWgZnWEtot4MDfag-ADvh7w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
No luck with "ami-12576757". Am I the only one having trouble with EC2? It's free to launch a micro instance. Can anyone else try this and verify that the AMI's aren't working? On 12/9/13, David Noel <david.i.noel@gmail.com> wrote: >> On 12/7/13, David Noel <david.i.noel@gmail.com> wrote: >>> I started a 10-BETA4 ami on us-west and tried ssh'ing in but had no >>> success. "Operation timed out" is the output. Does anyone know why >>> this might be? The default security group policies default to allowing >>> connections on port 22 from any IP address so I'm confused why ssh >>> isn't working. >>> >> On 12/8/13, David Noel <david.i.noel@gmail.com> wrote: >> Forgot to update firewall rules to allow outbound ssh. That should fix >> it. > > No, that's not it. Something else is wrong. I spun up "ami-2ebfda1e" > on a free micro instance and tried to ssh in. No luck. I spun up a > RHEL instance and ssh'd in just fine. Is anyone able to log in to the > FreeBSD ami's? If so, which one/s did you use? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHAXwYCiMHOerFYghUYOOD8mLorv5hEmj-M2oGASYhnz1CvOtw>