Hi ALl. Our sysadmins recently put aws behind a proxy and they will never allow us to access aws from the server 💀 💀 💀 💀 Now, I cannot use tools like

nf-core  pipelines list

or

igenomes

ProxyError: HTTPSConnectionPool(host='<http://nf-co.re|nf-co.re>', port=443): Max retries exceeded with url: /pipelines.json (Caused by ProxyError('Unable to connect to proxy', OSError('Tunnel connection failed: 
403 Forbidden')))

I don't know much aws but as far as I understand there are two ways to access aws : 'path' and 'host' , and I think 'host' would be less problematic than the 'path' mode on our side (?). Would it be a problem to change the mode(?) of those resources (Sorry, I don't have any idea if nf-core uses this 'path' mode and if changing the way it works is an easy/feasable task ). PL

Not just AWS, also https://nf-co.re apparently

@Phil Ewels ok, for nf-co.re ✅

Do you have a longer traceback that identifies where in the code this error comes from?

@Phil Ewels just to be clear. The error with nf-cor.re is fixed. Our proxy was enabled for this host. I first thought it was the very same problem than with aws/iGenome . But for aws/iGenome, the proxy will never be open on our side unlesss the mode of access is 'mode' instead of 'path' (see above)

ok - is there a different error message for that?

@Phil Ewels something like:

WARN: Unable to get file attributes file:
<s3://ngi-igenomes/igenomes/Homo_sapiens/NCBI/GRCh38/Sequence/WholeGenomeFasta/genome.fa>
-- Cause: software.amazon.awssdk.services.s3.model.S3Exception:
(Service: S3, Status Code: 403, Request ID: null) (SDK Attempt Count: 1)
WARN: Unable to get file attributes file:
<s3://ngi-igenomes/igenomes/Homo_sapiens/NCBI/GRCh38/Sequence/BismarkIndex>
-- Cause: software.amazon.awssdk.services.s3.model.S3Exception:
(Service: S3, Status Code: 403, Request ID: null) (SDK Attempt Count: 1)
ERROR ~ Error executing process >
'NFCORE_METHYLSEQ:METHYLSEQ:FASTQ_ALIGN_DEDUP_BISMARK:BISMARK_ALIGN (1)'

Right, that's when running a pipeline though right? Not when running the #CE5LG7WMB

nf-core

CLI?