Hi Mike, 
I just started a brand new instance with an account that is different from the one used to create required AWS components and Cloudman came up just fine, having started all of the required services.
Not that it should matter much, but are you instantiating a brand new instance or recovering an existing one?
Are you able to ssh into the instance? If yes, Cloudman log is accessible from /mnt/cm/paster.log so it should be possible to see what's going on.


On Thu, Jun 2, 2011 at 3:02 PM, Mike Dufault <dufaultm@yahoo.com> wrote:
Hello Galaxy Team,
Does anyone know if there is a problem with the most recent release of Galaxy Cloudman? I have launched several instances and when I try to access them using the Public DNS, it will not connect. I have given the AWS servers up to 30mins to establish the DNS web page, but it still does not work.
I have used Cloudman extensively, and my key-pair, security groups, etc have not changed. I even set up new ones in case that was an issue, but no luck.  I don't think the problem is on my end.
Any help would be appreciated.

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:


To manage your subscriptions to this and other Galaxy lists,
please use the interface at: