-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with MEO ISP in Portugal - 'ProtocolError('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer')) #5374
Comments
Are you using a proxy? |
Hey @andmart! This seems to be a network issue. Could you provide us with more details of how you're connecting, such as whether you're connecting through a proxy and whether your SSL version is new enough? |
I am having the same issue. To reply to your question, @pradyunsg , I am not connecting through a proxy (not that I know of) and I don't know how to check if my SSL version is recent enough. |
Update: Running the |
@crlsmnzs So it sounds like you were using ubuntu 16.04, pip 10.0.0, and python 3.5 as well in your initial test. Is that accurate? |
@sigmavirus24 no. I am not using a proxy. Using my home network. |
This error would usually happen when there's something like a proxy or a firewall blocking connections. |
I think you are right. It worked when connected in another network. But when @sigmavirus24 asked if I am using a proxy, I tried a VPN and it also did not wok. |
@sigmavirus24 I'm using Windows 10, pip 10.0.0 and Python 3.6.5. |
I'm getting the exact same issue. I'm using nextcloudpi on my RPi3 Model B. This issue started when I upgraded my internet plan and the ISP technitians switched my old router for a new one. That morning I had installed a package, but in the afternoon, after the router switch, I started getting this problem. I don't have a clue how to disable the router firewall or give it a whitelist. Guess I have some research to do. |
Same issue here, not connected through a proxy, same issues are present if connected via VPN to another network. Besides the issue is intermittent. On ubuntu 18.04 Also having the same issues under others servers provided by fastly vagrantup.com and python.org all of which have changes to the TLS forcing to TLS v1.2 The proxy is referred everywhere as possible issues, I'm not behind any corporate firewall. I'm using a simple business connection by a Portuguese ISP Haven't tested under windows to check for issues on network yet, will update. Curl also has issues with those even forcing it to tls , chrome also. So not a pip isolated problem, but rather a problem with network, just not proxy related. |
eheheh. Is it MEO? Because I just upgraded my internet and got a new MEO router (they promised the FiberGateWay, but I got a crappy one. Still trying to solve that one out) and I started having this error on my RPi. |
Yep. MEO here. |
Yes, can confirm it's MEO, we've tried a mobile hotspot from NOS and we have been able to reach vagrantup.com rubygems.org python.org pypa.io , all fastly served at tls 1.2 Failure on MEO ISP network in Coimbra Area with the following OS's: Network 1 (Business MEO ISP connection) : Network 2 (Home MEO ISP connection) : Success on NOS mobile hotspot: Haven't been able to test other ISP's. I've been able to successfully use pip without failure using Docker NAT on MEO ISP: |
Yet another strange report. When connected to MEO-WIFI ( using the same router ) i'm able to reach all above mentioned domains correctly as well as pip install. I've also edited nameservers to google without any luck, flushing cache dns etc..on the private network. |
I just moved to Coimbra. I can confirm I get the same error, only with MEO. I ask that you please update this thread if you find a solution. Is there any point in contacting MEO? I wouldn't know what to say... |
I've had this error only in Coimbra, been to Évora this past weekend without issues reaching the sites mentioned before under a Windows OS, I hadn't tried via Ubuntu (given other issues) Regarding the contacting MEO, I haven't done it also due to the same reasons, If you have a technical issue with their hardware it's already a pain to get it fixed, so I can only imagine the terrors you would go through explaining this.. :D The only NOT a real solution for now is to switch to their MEO-WIFI infra when you need it. And besides that, you can always use docker, as from what it seems under a docker container I have no issues.. That alone tilts me.. Can't figure out why yet. So you could create a volume from the container to the host to the place you wish to do the pip install, maybe some virtual environment creation with all the packages you wish to install via pip. When I get the time I'll post here that solution |
@Ilhicas thanks for sharing your findings man. I'm sticking to Vodafone for the time being, but I'll make sure to take a look at your Docker workaround and see if I can figure out the root of the issue. |
I can confirm I am having the same issue. I am also with MEO as the service provider in Viseu, Portugal. |
Confirming the same issue with MEO service provider in Porto, Portugal. |
Hello!! |
@citylife4 and everyone else here. |
If you have disabled IPv6 (I didn't try to change the IPv6 DNS, but in theory, it should also work) and changed IPv4 DNS and it still doesn't work, I don't know what you can do... UPDATE : Changing the IPv6 DNS provider does not resolve this, IPv6 needs to be disabled. Tested on Windows 10 + Debian on Rasp Pi |
Even removing MEO's DNS from their router via telnet and replacing them with my own (IPv4 and IPv6) doesn't work. Disabling IPv6 in the kernel would be even more unpratical for me than connecting to another network. Is this a problem on MEO's infrastructure(network) or router? I'm really puzzled since this doesn't work on my Linux distro or Windows 10, but works on Linux or BSD VMs... |
I have faced the same problems after @citylife4 pointed out the DNS solution. What really worked for me was use nordvpn, but I will reinforce with MEO to fix this. |
For now, my solution is temporarily disabling IPv6 on Linux with |
This issue seems to be about specific ISPs (I'm not sure, as I don't recognise the names, they are presumably local to one particular region?). If so, an someone suggest a more useful title for the issue to help anyone with a similar problem locate it? Also, I don't see anything actionable for pip here, so I suggest that the issue can be closed (which won't prevent further comments, if anyone has extra experience to add). |
Different equipment here, yet its the same brand, just an higher version from the technical details, just tested and it seemed to work now, but as mentioned previously the error occurrence is non-deterministic. Technicolor Gateway Product Name: TG784n v3 Software Release: 10.2.1.O Software Variant: DS Boot Loader Version: 1.1.2 Product Code: 3690227E Board Name: DANT-U |
With a little more searching found a tentative solution here https://www.reddit.com/r/portugal/comments/8cjj3s/developers_com_meo_em_casa_conexões_bloqueadas/ which is basically to disable ipv6 on the router/gateway telnet to router/gateway
Not sure it will last the "periodic" updates by the ISP.... |
One workaround is to disable IPv6.
|
I report that |
sudo sh -c 'echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6' |
Have this problem also, not only with pip but with many HTTPS websites mostly behind Fastly CDN. Also with MEO as my ISP. Yes disable ipv6 did the trick. Still would like to understand why this happens. I know that before disabling ipv6, if I checked my Public IP it would give an ipv6 one. Dont really Know if its an ISP problem or if many websites cant still handle well ipv6 addresses. |
Thank you so much guys, I can confirm that only disabling IPv6 works. I have tried many things before. |
It's likely somewhat obvious, but will just note that this issue also affects https://pypi.org via browsers, not just pip. |
Disabling ipv6 solved this issue for me. Still annoying though. |
Same problem for me. I am using MEO from Aveiro. |
Guys, I had same problem, using MEO ISP/Router. I solve using this command, to disable ipv6 network: sudo sh -c 'echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6' Then, i run pip and it works!!! |
I have the same issue. Since this problem is clearly related to MEO, is there a more appropriate forum to discuss this issue ? I have opened a support ticket with MEO, but I'd like to know if anyone else has done the same, and what answer did they receive. |
Hello guys, I'm from Coimbra, Portugal and had the same issue for so I tried the following and worked I just changed my IPv4 DNS to 8.8.8.8 and 8.8.4.4 (Google) If you want to keep IPv6 on, you can only disable it when you're installing something with pip. |
Reporting from Almada (MEO): Disabling IPv6 allowed me to use 'pip install package'. |
Same problem using MEO in Évora (Ubunbu 18.04). |
I am also behind MEO. My workaround was to temporarily disable IPv6 as explained How to disable IPv6 address on Ubuntu 18.04 Bionic Beaver Linux . This link also explains how to permanently disable IPv6. |
Has anyone tried this with 3rd party routers and modems? Are we sure the problem is meo's infrastructure? Or could it be the devices? |
@Zizico2 I think it was a problem with the devices because since the last firmware update, I never had any problems with IPv6. Or maybe they updated the infrastructure at the same time. Is anyone still having a problem with MEO? What version of the device are you using? (You can access http://192.168.1.254/ to find out.) My device: Technicolor TG784n v3 |
Hi folks! If you're still having issues connection to PyPI w/ MEO as your ISP, please open an issue in pypa/pypi-support using the 'Network Access Issue' template. That is a much better place for further discussion on this issue + better visibility for PyPI admins, so that they may take a look if there's anything actionable on the PSF-infra side. |
AFAICT, this is a case of an IPv6 issue with MEO; since disabling IPv6 seems to be working for some users. |
@pradyunsg the problem was identified in #5374 (comment) I believe as a result of firmware upgrades and/or changes to routing topology this particular problem should be resolved. Folks should be encouraged to retest IPv6 to see if it remains an issue for them. |
I think Fastly has fixed the issue on their side. I have the broken router and I see no issue doing PS: Linux users, with the broken router can also disable IPv6 Flow Labels instead of disabling IPv6 by changing this |
Closing this since this looks like a problem that has been resolved. :) |
Description:
I cannot install packages using pip
What I've run:
pip install cython
pip install kivy
pip install --upgrade pip
all this leads to the same error as below.
Outputs:
The text was updated successfully, but these errors were encountered: