I last used cloud launch a year ago with this account. I may have used biocloudcentral though at that point. Is there a work around I can do in the meantime, or should I wait for your fix? On Mon, Dec 16, 2013 at 10:34 AM, Dannon Baker <dannon.baker@gmail.com> wrote:

Have you previously used cloudlaunch with success with this account? If not, is this a new account created after 12-04-2013?

AWS now defaults new accounts to using EC2-VPC (and it doesn't look like there's any way to switch back to EC2 classic) and this unfortunately conflicts with cloudman's security groups -- a known issue that I'm working on a fix for.

-Dannon

On Mon, Dec 16, 2013 at 10:20 AM, greg <margeemail@gmail.com> wrote:

...

Hi guys,

I just did a cloud launch of MSG by going here: https://usegalaxy.org/cloudlaunch

I downloaded the pem file as instructed and I can access the galaxy admin page now.

However when I try to ssh into it:

$ ssh -i Downloads/cloudman_keypair.pem ubuntu@ec2-54-196-189-227.compute-1.amazonaws.com ssh: connect to host ec2-54-196-189-227.compute-1.amazonaws.com port 22: Operation timed out

And the same problem when I use the IP address.

I also can't ping the above address nor the IP address. It just says request time out.

Thanks,

Greg ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/

I'm still timing out. I wonder if there's a network or firewall type issue. I'll try again tomorrow from another location and report back. On Mon, Dec 16, 2013 at 11:00 AM, Dannon Baker <dannon.baker@gmail.com> wrote:

If this is an older account then it shouldn't be the VPC issue. I just attempted to ssh to it and it does respond fine for me -- what are the permissions for the cloudman_keypair.pem? `chmod 700 ~/Downloads/cloudman_keypair.pem` and try again. If that doesn't work, you may want to try using something like `ssh -vvv ~/Downloads/cloudman_keypair.pem ubuntu@<instance>` to get more verbose logging.

On Mon, Dec 16, 2013 at 10:48 AM, greg <margeemail@gmail.com> wrote:

...

I last used cloud launch a year ago with this account. I may have used biocloudcentral though at that point.

Is there a work around I can do in the meantime, or should I wait for your fix?

On Mon, Dec 16, 2013 at 10:34 AM, Dannon Baker <dannon.baker@gmail.com> wrote:

...

Have you previously used cloudlaunch with success with this account? If not, is this a new account created after 12-04-2013?

AWS now defaults new accounts to using EC2-VPC (and it doesn't look like there's any way to switch back to EC2 classic) and this unfortunately conflicts with cloudman's security groups -- a known issue that I'm working on a fix for.

-Dannon

On Mon, Dec 16, 2013 at 10:20 AM, greg <margeemail@gmail.com> wrote:

...

Hi guys,

I just did a cloud launch of MSG by going here: https://usegalaxy.org/cloudlaunch

I downloaded the pem file as instructed and I can access the galaxy admin page now.

However when I try to ssh into it:

$ ssh -i Downloads/cloudman_keypair.pem ubuntu@ec2-54-196-189-227.compute-1.amazonaws.com ssh: connect to host ec2-54-196-189-227.compute-1.amazonaws.com port 22: Operation timed out

And the same problem when I use the IP address.

I also can't ping the above address nor the IP address. It just says request time out.

Thanks,

Greg ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/