### Codecov Output
N/A
### Expected Results
A correct login.
### Actual Results
See above.
### Additional Information
N/A
---
### Author:  [@tom](https://community.codecov.com/u/tom)
#### Post date: [November 27, 2020, 9:33pm UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/2 "2020-11-27T21:33:46Z")
Hi @sbinet, we made a fix here, are you able to try again?
---
### Author:  [@sbinet](https://community.codecov.com/u/sbinet)
#### Post date: [November 28, 2020, 1:21pm UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/3 "2020-11-28T13:21:05Z")
hi,
thanks for taking a look at this.
unfortunately, this didn’t cure the issue.
---
### Author:  [@tom](https://community.codecov.com/u/tom)
#### Post date: [November 30, 2020, 4:02am UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/4 "2020-11-30T04:02:32Z")
@sbinet, what if you go directly to [Codecov](https://codecov.io/gh) ?
---
### Author:  [@sbinet](https://community.codecov.com/u/sbinet)
#### Post date: [November 30, 2020, 5:55pm UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/5 "2020-11-30T17:55:59Z")
nope, still no luck…
(with and w/o enabling the private-repo scope)
(the only difference when disabling the private-repo scope was a final 404 for the `favicon.png`)
---
### Author:  [@tom](https://community.codecov.com/u/tom)
#### Post date: [December 7, 2020, 11:50pm UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/6 "2020-12-07T23:50:57Z")
Hi @sbinet, we made a quick change here. Could you try again? If it still doesn’t work, I’m guessing maybe it’s a problem we’re having with GitHub. Would you be able to go to the [Codecov installation](https://github.com/settings/installations) and try logging into Codecov again? Note that you will have to re-grant permissions.
---
### Author:  [@sbinet](https://community.codecov.com/u/sbinet)
#### Post date: [December 8, 2020, 8:45am UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/7 "2020-12-08T08:45:05Z")
nope.
I revoked codecov from both my personal account and the organization account, then re-added it to both (`sbinet` and `go-hep`) with access to all repositories.
I did that twice (uninstall, re-install+re-grant), and tried with Chromium and Firefox.
still no cigar, unfortunately.
I tried to login with gitlab (and then defering to github for the authorization), that worked but of course none of my github projects were available.
---
### Author:  [@tom](https://community.codecov.com/u/tom)
#### Post date: [December 8, 2020, 11:34pm UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/8 "2020-12-08T23:34:05Z")
@sbinet, I’m sorry this is happening to you. I can’t seem to find anything in our logs suggesting something fishy is going on. Just to confirm, you’re still seeing `upstream request timeout` and the network tab looks similar to the screenshot above? Does `app.codecov.io/gh` work at all?
---
### Author:  [@sbinet](https://community.codecov.com/u/sbinet)
#### Post date: [December 9, 2020, 5:48pm UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/9 "2020-12-09T17:48:38Z")
yes, I am still seeing this error message, even when I browse to `app.codecov.io/gh`.
what if I try to install codecov by hand in github apps? (ie: providing the explicit oauth callback? which is it?)
or if I try with good’ol’ `curl`?
---
### Author:  [@tom](https://community.codecov.com/u/tom)
#### Post date: [December 15, 2020, 5:21am UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/10 "2020-12-15T05:21:34Z")
@sbinet, we are really stumped on our end why this is happening. The oauth token seems to be valid, and there’s no connection issue from our end.
Just to be extra clear, can you try deleting the cookies one more time and logging in. Can you login with the network tab open and screenshot your entire window once more? Maybe we can try to track down what’s happening or if there’s a GitHub connection issue.
---
### Author:  [@sbinet](https://community.codecov.com/u/sbinet)
#### Post date: [December 15, 2020, 8:34am UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/11 "2020-12-15T08:34:45Z")
here it is.
(I also just tried in an incognito window. same outcome)
---
### Author:  [@tom](https://community.codecov.com/u/tom)
#### Post date: [December 16, 2020, 5:07am UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/12 "2020-12-16T05:07:35Z")
@sbinet, I’ll look into our logs, but is there any extension or firewall that would be preventing login? Would you be able to open up the `github?code=**` and see what the headers and request body are?
---
### Author:  [@sbinet](https://community.codecov.com/u/sbinet)
#### Post date: [December 16, 2020, 9:01am UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/13 "2020-12-16T09:01:43Z")
as I said I could login with the bitbucket credentials, so it’s probably not an artefact (network or otherwise) from my end.
replaying the `code=...` request with curl, I get:
```auto
$> curl -v 'https://codecov.io/login/github?code=' -H 'authority: codecov.io' -H 'upgrade-insecure-requests: 1' -H 'dnt: 1' -H 'user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36' -H 'accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9' -H 'sec-fetch-site: cross-site' -H 'sec-fetch-mode: navigate' -H 'sec-fetch-user: ?1' -H 'sec-fetch-dest: document' -H 'referer: https://about.codecov.io/' -H 'accept-language: en-US,en;q=0.9,de;q=0.8,fr;q=0.7' --compressed
* Trying 34.120.215.12:443...
* Connected to codecov.io (34.120.215.12) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=codecov.io
* start date: Nov 4 03:00:58 2020 GMT
* expire date: Feb 2 03:00:58 2021 GMT
* subjectAltName: host "codecov.io" matched cert's "codecov.io"
* issuer: C=US; O=Google Trust Services; CN=GTS CA 1D2
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x558ed07c3d80)
> GET /login/github?code= HTTP/2
> Host: codecov.io
> accept-encoding: deflate, gzip, zstd
> authority: codecov.io
> upgrade-insecure-requests: 1
> dnt: 1
> user-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36
> accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
> sec-fetch-site: cross-site
> sec-fetch-mode: navigate
> sec-fetch-user: ?1
> sec-fetch-dest: document
> referer: https://about.codecov.io/
> accept-language: en-US,en;q=0.9,de;q=0.8,fr;q=0.7
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 500
< server: envoy
< date: Wed, 16 Dec 2020 08:59:45 GMT
< content-type: application/json
< x-frame-options: SAMEORIGIN
< content-length: 31
< vary: Origin, Cookie
< x-envoy-upstream-service-time: 274
< via: 1.1 google
< alt-svc: clear
<
* Connection #0 to host codecov.io left intact
{"error": "Server Error (500)"}
```
---
### Author:  [@tom](https://community.codecov.com/u/tom)
#### Post date: [January 4, 2021, 9:33pm UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/14 "2021-01-04T21:33:16Z")
@sbinet, apologies this got away from me due to the holidays. Are you able to reproduce one more time and give the code?
* * *
**EDIT 2023-03-13**
This error comes up from time to time and is usually a blip on one of our servers. I would recommend waiting an hour and re-running the CI job. If you are still running into this issue, please open a new topic.
---
### Author:  [@mayank-meragi](https://community.codecov.com/u/mayank-meragi)
#### Post date: [January 31, 2023, 9:04am UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/15 "2023-01-31T09:04:24Z")
Hey I am facing the same issue as above, revoking the access and starting fresh, worked for me
---
### Author:  [@aastopher](https://community.codecov.com/u/aastopher)
#### Post date: [March 14, 2023, 11:45pm UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/16 "2023-03-14T23:45:03Z")
is this still the solution?
---
### Author:  [@tom](https://community.codecov.com/u/tom)
#### Post date: [March 15, 2023, 4:23pm UTC](https://community.codecov.com/t/login-error-upstream-request-timeout/2353/17 "2023-03-15T16:23:35Z")
@aastopher it is. If you are still getting the error, please open a new topic.