Update:

ProFTP gives as an answer to passive mode the INTERNAL IP to connect which makes FileZilla break the connection.

Indeed adding MasqueradeAddress <EXTERNAL_IP> in the config file, it works.

Where is the proftp config file being created in cloudman? How can this be added dynamically?

Best, Alexander

2015-09-01 18:19 GMT-05:00 Alexander Vowinkel vowinkel.alexander@gmail.com :

Hi,

I get the error "Could not read from socket: ECONNRESET - Connection reset by peer" when connecting with FileZilla to the Cloud Instance. Using launch.usegalaxy.org

FileZilla Log: http://pastebin.com/zfACC6wH ProFTP Log: http://pastebin.com/T9JxKVCb

With console FTP in linux I can connect, get a listing and upload files. I tried to find out what the reason is, but no solution found. bareFTP is also not able to connect.

The ports for PassivePorts are open (checked in AWS)

Any idea on this?

Thanks, Alexander

Great! Thanks!

2015-09-02 8:47 GMT-05:00 Enis Afgan enis.afgan@irb.hr:

Thanks for reporting this (and figuring out the solution). It's been fixed with this commit https://github.com/galaxyproject/cloudman/commit/550d90cbde49f37d6d7bdbea3170e6f6085ca613 so any new cluster will work fine.

Cheers.

On Tue, Sep 1, 2015 at 7:42 PM, Alexander Vowinkel < vowinkel.alexander@gmail.com> wrote:

...

Update:

ProFTP gives as an answer to passive mode the INTERNAL IP to connect which makes FileZilla break the connection.

Indeed adding MasqueradeAddress <EXTERNAL_IP> in the config file, it works.

Where is the proftp config file being created in cloudman? How can this be added dynamically?

Best, Alexander

2015-09-01 18:19 GMT-05:00 Alexander Vowinkel < vowinkel.alexander@gmail.com>:

...

Hi,

I get the error "Could not read from socket: ECONNRESET - Connection reset by peer" when connecting with FileZilla to the Cloud Instance. Using launch.usegalaxy.org

FileZilla Log: http://pastebin.com/zfACC6wH ProFTP Log: http://pastebin.com/T9JxKVCb

With console FTP in linux I can connect, get a listing and upload files. I tried to find out what the reason is, but no solution found. bareFTP is also not able to connect.

The ports for PassivePorts are open (checked in AWS)

Any idea on this?

Thanks, Alexander