Aspera

 View Only

 ascp suddenly fails with failed to authenticate – worked before with same setup

zhilin wang's profile image
zhilin wang posted 05/19/26 04:28 AM

Hi Community,
I have been using ascp to download SRA data from EBI without any issues until recently. Starting from March 2026, the same command began failing with an authentication error.

Command that worked before (March 2026):
    ascp -Q -l 300m -P 33001 -k 1 -i /path/to/asperaweb_id_dsa.openssh era-fasp@fasp.sra.ebi.ac.uk:/vol1/fastq/SRR165/002/SRR1658702/SRR1658702_2.fastq.gz /target/dir

Current error:
    ascp: failed to authenticate, exiting.
    Session Stop  (Error: failed to authenticate)

What I have confirmed:
    The private key file (asperaweb_id_dsa.openssh) has not changed.
    ascp version is 4.0.0.
    I tried installing the latest Aspera Connect, but it fails due to low GLIBC version on the server.

My question:
Is there any way to resolve this authentication issue without upgrading ascp or system libraries? For example, can I force the client to use older encryption protocols or adjust settings to restore compatibility with EBI servers?

Any insights would be greatly appreciated.

Best regards,

BEN FORSYTH's profile image
BEN FORSYTH

See posting here with similar question

https://community.ibm.com/community/user/question/ena-aspera-download-fails-with-repeated-password-prompt