How to configure Galaxy to fix the error: fastq-dump-paired tool can't fetch SRA file from accession number?
There are some issues with Galaxy Main at http://usegalaxy.org. Please follow here for details and updates: https://biostar.usegalaxy.org/p/20698/
This error may have been due to recent server issues. Once resolved, rerun the job to eliminate that cause. If it fails again, we can help examine job inputs what the root cause is (malformed accession number or a true tool problem). Start with sharing the accession number as directly entered on the tool form (or share a screenshot of the form filled in). We may ask for a bug report to be send in, but the inputs can be examined and server issues fixed first.
Should you be working on a different server, I can let you know that the tool Get Data: EBI SRA is known to fail at times due to connection issues with the data provider (unrelated to Galaxy, and to my knowledge occurs across all deployment types - public server, personal/shared local and/or cloud, custom docker builds - all). Sometimes it takes a few tries to exact certain datasets. The tools that extract data from NCBI can be an alternative - unless these are the tools in use? If so and working at Galaxy Main, the server issues are almost certainly a factor.
Thanks for posting about the problem, Jen, Galaxy team