Skip to content
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

Error: https fetch: Get https://dmitri.shuralyov.com/app/changes?go-get=1: dial tcp 172.93.50.41:443: i/o timeout #29

Closed
evanger24 opened this issue Sep 4, 2019 · 3 comments

Comments

@evanger24
Copy link

commented Sep 4, 2019

Similar to #23 and #25, build errors when trying to download packages from your site.

go: dmitri.shuralyov.com/app/changes@v0.0.0-20180602232624-0a106ad413e3: unrecognized import path "dmitri.shuralyov.com/app/changes" (https fetch: Get https://dmitri.shuralyov.com/app/changes?go-get=1: dial tcp 172.93.50.41:443: i/o timeout)

`curl -v https://dmitri.shuralyov.com

  • About to connect() to dmitri.shuralyov.com port 443
  • Trying 172.93.50.41... Connection timed out
  • couldn't connect to host
  • Closing connection #0
    curl: (7) couldn't connect to host`
@dmitshur

This comment has been minimized.

Copy link
Member

commented Sep 4, 2019

Thanks for reporting.

I'm not able to reproduce it from my current location:

$ curl -is https://dmitri.shuralyov.com 2>&1 | head -n 5
HTTP/2 200 
content-type: text/html; charset=utf-8
date: Wed, 04 Sep 2019 23:03:08 GMT

<html>

Is it reproducible for you right now? What part of the world are you making the HTTP request from? It might be a networking issue that affects only some IPs/locations.

@dmitshur

This comment has been minimized.

Copy link
Member

commented Sep 4, 2019

I tried a global latency testing tool at latency.apex.sh, and it's not finding availability problems from any of the locations it tests from:

https://latency.apex.sh/?url=https%3A%2F%2Fdmitri.shuralyov.com%2Fapp%2Fchanges%3Fgo-get%3D1

image

If you can provide more information, it'd be helpful in trying to diagnose this issue. Thanks.

@evanger24

This comment has been minimized.

Copy link
Author

commented Sep 5, 2019

Thank you so much for your quick response. I encountered a firewall on my end. Thank you again for looking into this.

@evanger24 evanger24 closed this Sep 5, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.