Page History
Before trying anything else check you are:
using Python 3
using the most up to date version of the CDS API
These 2 things cause 90% of issues experienced so we recommend to double check both these factors first
If you
...
are still experiencing
...
issues it's time to look at the error messages.
WARNING Recovering from connection error [HTTPSConnectionPool(host='cds.climate.copernicus.eu', port=443): |
|---|
What type of error are you seeing?
'Timed out' or ‘Proxy’
If you're seeing an error message which mentions 'timed out' like the example below:Timed Out
WARNING Recovering from connection error [HTTPSConnectionPool(host='cds.climate.copernicus.eu', port=443):
Max retries exceeded with url: /api/v2/tasks/7b4e735b-5a79-4913-bbcb-cebc0c65b420 (Caused by ConnectTimeoutError(<urllib3.connection.VerifiedHTTPSConnection object at
...
0x7f81056e8940>, 'Connection to cds.climate.copernicus.eu timed out. (connect timeout=60)'))], attempts 12 of 500
Diagnosis: This is likely due to network issues causing delays in the communication between the your system and the CDS.
Solution: The best way round this is to add the "timeout=600" (or longer) option for the timeout duration in seconds, to your CDS API request :
c =cdsapi.Client(timeout=600,quiet=False,debug=True) |
If the message mentions ‘Cannot connect to proxy’
WARNING Recovering from connection error [HTTPSConnectionPool(host='cds.climate.copernicus.eu', port=443): Max retries exceeded with url: /api/v2/resources/cems-fire-historical (Caused by ProxyError('Cannot connect to proxy.', timeout('_ssl.c:835: The handshake operation timed out',)))], attempts 0of 500 |
Diagnosis: This could also be due to the network issues causing delays in the communication between the your system and the CDS. Therefore we recommend to try this solution first
...