Hi Lilach, It seems you ran into a bug that was introduced in the most recent CloudMan update. It's been fixed now.
If you still have your instance up, the way to get around the issue is to simply strip off '/cloud' part of the URL and you'll get to Galaxy. Any new instances will work fine.
Thanks for reporting this issue,
Enis
On Thu, Jun 14, 2012 at 7:49 AM, Lilach Friedman
<lilachfr@gmail.com> wrote:
and I terminated a created from the beginning new instanced for the last several hours (at least 5 different instances). All don't work.
Lilach
2012/6/14 Lilach Friedman
<lilachfr@gmail.com>
Hi,
Can somebody please help me?
I'm trying for hours to connect to Galaxy on Amazon EC2. I did everything according the instructions, but did not succeed.
The "Access Galaxy" button in the instance remains grey out.
I copied the screen print and the log to the attached file.
Can anyone help me please?
and another questions: I want to use it to analyze MiSeq results (to align to the human genome). 100 Gb EBS and a large machine are enough? too much?
Many thanks,
Lilach.
___________________________________________________________
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org. Please keep all replies on the list by
using "reply all" in your mail client. For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:
http://lists.bx.psu.edu/listinfo/galaxy-dev
To manage your subscriptions to this and other Galaxy lists,
please use the interface at:
http://lists.bx.psu.edu/