Question: (Closed) Unable to connect to New Galaxy Cloudman By Ftp
1
gravatar for Marco Blanchette
4.5 years ago by
United States
Marco Blanchette10 wrote:

I just fired up a new Galaxy instance on AWS using Cloudman running the AMI ami-a7dbf6ce and I am unable to connect using FTP and the email/password credential that I just created. I see several threads on the topic that seems to suggest that this has been fixed in previous ami released.

Any help/suggestions? 

Thanks

Marco

software error galaxy cloudman • 1.3k views
ADD COMMENTlink modified 4.5 years ago by Dannon Baker3.7k • written 4.5 years ago by Marco Blanchette10

Marco,

Are you seeing the same behavior as in this thread: New Cloudman instance: anonymous FTP only ?

ADD REPLYlink written 4.5 years ago by Dannon Baker3.7k

Hello mab!

Questions similar to yours can already be found at:

We have closed your question to allow us to keep similar content in the same thread.

If you disagree with this please tell us why in a reply below. We'll be happy to talk about it.

Cheers!

ADD REPLYlink written 4.5 years ago by Dannon Baker3.7k

(this didn't do exactly what I wanted.  In any event, follow the thread there and we'll get this resolved)

ADD REPLYlink written 4.5 years ago by Dannon Baker3.7k
0
gravatar for Jennifer Hillman Jackson
4.5 years ago by
United States
Jennifer Hillman Jackson25k wrote:

Hello Marco,

Yes, this should be functional. Did you set up the inbound connections outlined in step #6 on the Cloudman set-up page? https://wiki.galaxyproject.org/CloudMan/AWS/GettingStarted

Thanks! Jen, Galaxy team

ADD COMMENTlink written 4.5 years ago by Jennifer Hillman Jackson25k
0
gravatar for Marco Blanchette
4.5 years ago by
United States
Marco Blanchette10 wrote:

Yes, I believe so.

 

However, the security group match exactly what is describe in the Getting

Started.

 

BTW: I can connect to the server using the anonymous id and get directory

listing, working directory, etc, The anonymous user as no privs to upload

(Good!). Take a look:

 

mp04l1djwr:~ mab$ ftp galaxy.XXX

Connected to galaxy.XXX

220 (vsFTPd 2.3.5)

Name (galaxy.XXX:mab): anonymous

331 Please specify the password.

Password:

230 Login successful.

Remote system type is UNIX.

Using binary mode to transfer files.

ftp> passive

Passive mode: off; fallback to active mode: off.

ftp> ls

200 EPRT command successful. Consider using EPSV.

150 Here comes the directory listing.

226 Directory send OK.

ftp> pwd

Remote directory: /

ftp> put test.html

local: test.html remote: test.html

Abort trap: 6

 

 

 

 

Passive mode complains, passive ports are not open in the firewall, which

I guess is fine. So, definitely the server is running and respondingŠ

(although I¹m not sure why the connection bails on the put attemptsŠ)

 

I just can¹t do the same with the Galaxy user credentials, not sure what¹s

going on here. Take look:

 

mp04l1djwr:~ mab$ ftp galaxy

Connected to ec2-XXX.XXX.XXX.XXX.compute-1.amazonaws.com.

220 (vsFTPd 2.3.5)

Name (galaxy:mab): mab@stowers.org

331 This FTP server is anonymous only.

Password:

503 Login with USER first.

ftp: Login failed

 

BTW2: I just patched to revision 13079:7a7985a007fb, which did not solve

the problem.

ADD COMMENTlink written 4.5 years ago by Marco Blanchette10

Thanks!

 

I'm able to confirm the same thing here -- looking into the issue, and I'm going to merge these two posts.

ADD REPLYlink written 4.5 years ago by Dannon Baker3.7k
Please log in to add an answer.
The thread is closed. No new answers may be added.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 16.09
Traffic: 129 users visited in the last hour