Webin-CLI 8.2.0 failed to connect to FTP server

[TSolDour]

Hi,

I am trying to submit a transcriptome assembly to ENA. Study, Samples and Reads already exist at ENA.
Here is the command line used to validate and submit my assembly:

java -jar Downloads/webin-cli-8.2.0.jar -context transcriptome -userName ### -password ### -manifest Documents/Recherche/rnasep/Valorisation/ENA/assembly_manifest.tsv -validate -submit -outputDir Documents/Recherche/rnasep/Valorisation/ENA/ -inputDir Documents/Recherche/rnasep/Valorisation/ENA/

The validation goes well, but when submission starts, I get this error :
INFO : Your application version is 8.2.0
INFO : Submission(s) validated successfully.
INFO : Creating report file: /Users/tsoldo01/Documents/Recherche/rnasep/Valorisation/ENA/./webin-cli.report
INFO : Connecting to FTP server : webin2.ebi.ac.uk
WARN : Retrying connecting to FTP server.
WARN : Retrying connecting to FTP server.
WARN : Retrying connecting to FTP server.
WARN : Retrying connecting to FTP server.
WARN : Retrying connecting to FTP server.
WARN : Retrying connecting to FTP server.
ERROR: Failed to connect to FTP server. Failed to upload files to server because of a system error.
ERROR: Some or all submissions failed. Please see application logs.

Noteworthy, when I'v loaded the raw reads using lftp webin2.ebi.ac.uk -u Webin-xxxxx there was no problem to connect...

Does anyone have any cue to fix this issue ?

Thank you very much,
Thomas.

[dovivi]

Hi,

did you manage to upload the samples? I'm facing same problem, although two samples were successfully uploaded. I've also tried with -ascp and no luck.

Thanks.

[TSolDour]

Hi dovivi,

Yes I did. The issue came from the firewall of my institution's network.
I retried at home and it eventually worked.

I don't have so much cues to share with you...

Good luck,
Thomas.

[dovivi]

Hi TSolDour,

thanks for the prompt reply. I'll try from outside my institution's network then :-)

Thanks!

[corneliusroemer]

We got the same issue at Pathoplexus and just retrying a few minutes later succeeded. Might well be ENA flakiness rather than firewall (it could be that as well but I'm sure in our case there's no firewall).

[dovivi]

Just to confirm, outside my institution's network it worked smoothly.

[corneliusroemer]

@dovivi As there was probably some delay, it's possible that it was just ENA working again and not the different network in your case. 😄

[corneliusroemer]

@axbazin made a new issue that avoids the firewall red-herring (we've seen this error and it has nothing to do with firewall): #146