Repository navigation
Connection Timeout after installing Git-LFS #9123
Description
Describe the bug
NOTE: Not sure this is related to Git-LFS, but this started occurring right after installing it
Same as #8328 (but I'll be responsive)
gh cli worked great, until I installed Git LFS, afterwards, connection gets timed out.
Steps to reproduce the behavior
- Install git-lfs and configure a repo to use it
- Try to authenticate gh cli
Expected vs actual behavior
Timeout vs Responses from the server
Logs
gh auth login
? What account do you want to log into? GitHub.com
? What is your preferred protocol for Git operations on this host? HTTPS
? Authenticate Git with your GitHub credentials? Yes
? How would you like to authenticate GitHub CLI? Login with a web browser
! First copy your one-time code: D182-8F8C
Press Enter to open github.com in your browser...
failed to authenticate via web browser: Post "https://api.github.com/graphql": dial tcp [2a05:d014:c59:1a03:1eee:b7e:d88f:dcb9]:443: i/o timeoutWithin issue #8328 , william asked for the results of this command:
curl -vvv -L \
-H "Accept: application/vnd.github+json" \
-H "X-GitHub-Api-Version: 2022-11-28" \
https://api.github.com/The command simply times out.
* Trying [2a05:d014:c59:1a03:1eee:b7e:d88f:dcb9]:443...
* Trying 3.127.156.149:443...
* connect to 2a05:d014:c59:1a03:1eee:b7e:d88f:dcb9 port 443 failed: Operation timed out
* connect to 3.127.156.149 port 443 failed: Operation timed out
* Failed to connect to api.github.com port 443 after 75221 ms: Couldn't connect to server
* Closing connection
curl: (28) Failed to connect to api.github.com port 443 after 75221 ms: Couldn't connect to server
Activity
DeanAyalon commentedon May 28, 2024
I do not know what the problem might have been, but it seemed to have resolved itself, the requests are no longer timed out and everything is once again working.
williammartin commentedon May 28, 2024
Thanks for updating, maybe just some network blip. Reading your issue it's hard to see what
ghwould have to do with it sincecurlis failing and my minimal understanding ofgit-lfsdoesn't suggest anything either.