• I have activated the browser Private mode to evaluate if the error still happens.
• I have turn-off any extension on my browser like adblock that may interfere with the app behaviour.
• I have searched the issues of this repo and believe that this is not a duplicate.
• If an exception occurs when executing a command, I execute it again in debug mode (DEBUF = True in settings).

Describe the bug 🐛

Status 503 Service Unavailable

Public Links run only once when connected to a Django job, then fail when launch a second time displaying the error message 👉 upstream connect error or disconnect reset before headers reset reason connection failure

To Reproduce 🔂

1. Create a Public Links.
2. Waiting for Ingress status to be Ingress is now ready.
3. Connect the newly created Public Link to a Django job.
4. Click on Submit to launch the Django job.
5. Click on Open interface does open a browser window displaying the newly created Public Link in the navigation bar.
6. Click on Stop application to terminate the running Django job.
7. Click on Run application again to launch the Django job with the same parameters.
8. Click on Submit to launch the Django job.
9. Click on Open interface does open a browser window displaying the same Public Link as first run in the navigation bar, this time displaying the error message: upstream connect error or disconnect/reset before headers. reset reason: connection termination.

Configuration ⚙️

• Python 3.11.0
• PostgreSQL Server 14.5
• Django version 4.1.2

Expected behavior 🚀

app-mission-ocean.cloud.sdu.dk running in DEBUG=False with cache and collectstatic.

Additional context 🌍

When conducting searches on "kubernetes" "ingress" "upstream connect error or disconnect/reset before headers. reset reason: connection failure" on google.com, we note a lot of chatters around that issue, notably that one 👇

For some time, our users reported seeing upstream connect errors and 503s like ”upstream connect error or disconnect/reset before headers. reset reason: connection termination“. This issue goes away if we refresh our browser page. However, it was very difficult to reproduce this error. -- Puzzling 503s and Istio

Notes 📝

• Kubernetes Documentation > Ingress Controllers.
• "kubernetes" "ingress" "upstream connect error or disconnect/reset before headers. reset reason: connection failure" search on google.com.
• Bug Report 🐞kubernetes - upstream connect error or disconnect/reset before headers. reset reason: connection failure #1
• UCloud ticket 🎫 https://jira.cloud.sdu.dk/servicedesk/customer/portal/43/TICKET-1847

Public Links  🔗