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

Bug Report 🐞kubernetes - upstream connect error or disconnect/reset before headers. reset reason: connection failure #1

Open
JV-conseil opened this issue Feb 24, 2023 · 0 comments
Assignees
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@JV-conseil
Copy link
Owner

JV-conseil commented Feb 24, 2023

upstream connect error or disconnect:reset before headers  reset reason connection failure

kubernetes - upstream connect error or disconnect/reset before headers. reset reason: connection failure 👀

I solved it. In my case the yaml file was wrong. I reviewed it and the problem now is solved. Thank you – stackoverflow.com

Describe the bug 🐛

UCloud public link does not connect with a running Django app 🐍

When visiting the page https://app-githubbing.cloud.sdu.dk we got an error message 🙅‍♂️

upstream connect error or disconnect/reset before headers. reset reason: connection failure

Configuration ⚙️

nginx
Python 3.11.0
PostgreSQL Server 14.5
Django version 4.1.2

Expected behavior

Display a 🚀 when visiting https://app-githubbing.cloud.sdu.dk

Documentation 📚

UCloud utilizes Kubernetes for Container orchestration. This is used both for the deployment of UCloud and scheduling of user jobs. — UCloud 3rd party dependencies

Diagnosis attempts 🩺

curl request

curl "https://app-githubbing.cloud.sdu.dk" --verbose👇

Connection state changed (MAX_CONCURRENT_STREAMS == 128)!

*   Trying 130.225.164.100:443...
* Connected to app-githubbing.cloud.sdu.dk (130.225.164.100) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
*  subject: C=DK; ST=Syddanmark; O=Syddansk Universitet; CN=*.cloud.sdu.dk
*  start date: Aug  8 00:00:00 2022 GMT
*  expire date: Aug  8 23:59:59 2023 GMT
*  subjectAltName: host "app-githubbing.cloud.sdu.dk" matched cert "*.cloud.sdu.dk"
*  issuer: C=NL; O=GEANT Vereniging; CN=GEANT OV RSA CA 4
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* h2h3 [:method: GET]
* h2h3 [:path: /]
* h2h3 [:scheme: https]
* h2h3 [:authority: app-githubbing.cloud.sdu.dk]
* h2h3 [user-agent: curl/7.85.0]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x558727b789b0)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> GET / HTTP/2
> Host: app-githubbing.cloud.sdu.dk
> user-agent: curl/7.85.0
> accept: */*
> 
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)! 👈 👀 
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
< HTTP/2 404 
< server: nginx
< date: Fri, 24 Feb 2023 00:35:55 GMT
< content-length: 0
< vary: Origin
< x-envoy-upstream-service-time: 0
< referrer-policy: same-origin
< strict-transport-security: max-age=15768000; includeSubDomains
< x-xss-protection: 1; mode=block
< x-content-type-options: nosniff
< x-frame-options: SAMEORIGIN
< job-id: 8139b0e2ada0597194f6965a8b90bf64
< 
* Connection #0 to host app-githubbing.cloud.sdu.dk left intact
@JV-conseil JV-conseil added the bug Something isn't working label Feb 24, 2023
@JV-conseil JV-conseil changed the title UCloud public link does not connect with running Django app kubernetes - upstream connect error or disconnect/reset before headers. reset reason: connection failure Feb 25, 2023
@JV-conseil JV-conseil added the good first issue Good for newcomers label Feb 25, 2023
@JV-conseil JV-conseil added this to the UCloud Web Qualification milestone Mar 13, 2023
@JV-conseil JV-conseil reopened this Mar 18, 2023
@JV-conseil JV-conseil self-assigned this Mar 19, 2023
@JV-conseil JV-conseil changed the title kubernetes - upstream connect error or disconnect/reset before headers. reset reason: connection failure Bug Report 🐞kubernetes - upstream connect error or disconnect/reset before headers. reset reason: connection failure Mar 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant