-
Notifications
You must be signed in to change notification settings - Fork 73
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
edgedl.me.gvt1.com is not working properly as of 7:40am GMT #60
Comments
In our company we have same problems. We can reach |
this is similar. Infact even some of our AWS EC2 servers can connect. Server A will connect, Server B cannot connect. Both are 100% open to the public on AWS Firewalls, both have identical Network and VPC setups. It's very strange... We have had to move all dockers that use this to another EC2 cluster which seems to ping, but this has only broken this morning... It's been fine for.. a very long time! |
@vekien are there any ongoing AWS incidents? we are also able to connect from our networks. |
It seems to be ipv6 issue, puppeteer/puppeteer#11060 (comment) With curl use |
We had issues even forcing ipv4 as well as disabling ipv6 completely. Wonder if it's slightly separate issue or something along the routing with that url.
No incident but from experience AWS rarely tell us. In typical fashion after moving all the dockers to working servers it seems to be now working in all servers where it was previously failing, so it seemed to be short lived issue... I noticed So it now works fine! I will keep monitoring over the day, maybe it was some routing issue on AWS end.
|
Since Chrome dev downloads moved to edgedl.me.gvt1.com, there have been constant connection problems. In most cases the problem seems to be that TLS negotiation fails after "Client Hello". From the downloader perspective, it seems that edgedl service has backends that behave differently than others and when connection initiation starts on a problematic service node it fails.
|
Got:
For VIVO ISP at south Brazil, this is weird, when connected to a USA VPN it worked, not blocked anymore. |
Hello,
Not sure if this is the right place but it's the place that is Chrome For Testing.
We noticed this morning that downloads from edgedl.me.gvt1.com are no longer working on a range of EC2 servers this morning. We have hundreds of servers, all configured identical and about half of them cannot connect to edgedl.me.gvt1.com
Has something changed with
edgedl.me.gvt1.com
? or are there any mirrors?The text was updated successfully, but these errors were encountered: