CDS API requests could sometimes fail because it does not pick up the right proxy when the client script comes to download the data.

An option is to manually set HTTP_PROXY/HTTPS_PROXY explicitly with the port number used and then re-running the script.

Here an example:

The users system were only set to:

export HTTP_PROXY=http://useraddress

export HTTPS_PROXY=http://useraddress

This was resolved by explicitly specifing the port on the proxy to use at the user's site for port 80/8080 connections:

export HTTP_PROXY=http://useraddress:userport/

export HTTPS_PROXY=http://useraddress:userport/

Note that you are also able to download the datafile using wget.