You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing packages from pypi we're seeing intermittent connection resets/failures to download or even query for packages. This seems to be happening across all our internal org when coming out of a specific location. We've done what we can to inspect the drops with our networking team but there's no indication of blocking happening at our firewalls, or issues with our provider. We do see tcp resets, seemingly initiated by the endpoint.
The specific endpoints we see lots of resets from:
104.17.254.182
104.17.255.182
151.101.192.223
151.101.0.233
162.247.243.20
And our public facing IP is:
192.149.76.131
The behavior is erratic enough that simply retrying several times can lead to eventual success, but for anything Expected behavior
pip install functions without networking failures To Reproduce
This will be very difficult to reproduce outside our networks I fear. But it's easily reproduced on our end every time we install a python package with a large list of dependencies.
My Platform
We're pretty much exclusively Linux as a source. Source python versions are 3.7 and 3.11 though we've reproduced in other versions as well. Pip versions on clients seeing this issue range from 18 to latest. Additional context
The text was updated successfully, but these errors were encountered:
Describe the bug
When installing packages from pypi we're seeing intermittent connection resets/failures to download or even query for packages. This seems to be happening across all our internal org when coming out of a specific location. We've done what we can to inspect the drops with our networking team but there's no indication of blocking happening at our firewalls, or issues with our provider. We do see tcp resets, seemingly initiated by the endpoint.
The specific endpoints we see lots of resets from:
And our public facing IP is:
The behavior is erratic enough that simply retrying several times can lead to eventual success, but for anything
Expected behavior
pip install
functions without networking failuresTo Reproduce
This will be very difficult to reproduce outside our networks I fear. But it's easily reproduced on our end every time we install a python package with a large list of dependencies.
My Platform
We're pretty much exclusively Linux as a source. Source python versions are 3.7 and 3.11 though we've reproduced in other versions as well. Pip versions on clients seeing this issue range from 18 to latest.
Additional context
The text was updated successfully, but these errors were encountered: