Any pip install XXX failed with ReadTimeoutError/HTTPSConnectionPool errors

[liron50]

Any package I'm trying to install I'm getting the same error.

For example:
pip install flask (tried also pip3 instead)

WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/flask/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/flask/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/flask/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/flask/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='pypi.org', port=443): Read timed out. (read timeout=15)")': /simple/flask/
ERROR: Could not find a version that satisfies the requirement flask (from versions: none)
ERROR: No matching distribution found for flask

I was using python 3.7.X and was able to install packages before (~year ago), but today start getting those errors. I tried uninstall python and install again, therefore now I have the latest versions:

Python 3.9.1

pip 20.2.3

(window 8.1)

I checked the connection by running "$ curl https://pypi.org" and doesn't see any error.
Tried to set timeout of 60 seconds but same error.
I'm not using proxy.

What else I could check?

[ichard26]

This is likely a transient network issue with your system/network. Closing as there isn't anything actionable for us here. We do want to improve the error messaging here, however (see also PR #12818).