Trying to curl to my deployed container app. As far as I see the container started successfully and the listener port is running evidently by running netstat -an within the container. But a curl to the health check endpoint fails. Host: automatoraca-app.wittymeadow-****.azurecontainerapps.io user-agent: curl/7.78.0 accept: / STATE: DO => DID handle 0x80007eec8; line 2068 (connection #0) multi changed, check CONNECT_PEND queue! STATE: DID => PERFORMING handle 0x80007eec8; line 2187 (connection #0) HTTP/2 found, allow multiplexing < HTTP/2 502 < content-length: 110 < content-type: text/plain < date: Fri, 31 Mar 2023 17:43:41 GMT < nread == 0, stream closed, bailing STATE: PERFORMING => DONE handle 0x80007eec8; line 2386 (connection #0) multi_done Connection #0 to host automatoraca-app.wittymeadow-4cc63852.southcentralus.azurecontainerapps.io left intact Expire cleared (transfer 0x80007eec8) upstream connect error or disconnect/reset before headers. retried and the latest reset reason: protocol error

Hello, @Andy Kepr - Sorry for the late reply. The error message "upstream connect error or disconnect/reset before headers" indicates that the connection between the client and the server was closed before the server could send a response. The error message "protocol error" indicates that there was an issue with the protocol used to communicate between the client and the server for the health check endpoint. This could be caused by a number of issues, such as a misconfigured firewall (if any), a network issue, or a problem with the server itself. Generally speaking, to troubleshoot this issue, you can try the following steps: Check the firewall settings to ensure that the port used by the container app is open. Check the network settings to ensure that there are no issues with the network. Check the logs of the container app to see if there are any errors or issues that could be causing the problem. Try accessing the container app from a different network or location to see if the issue is specific to your current network. If the issue persists, we'll likely need to work with you on a 1:1 setting and take a closer look. In such a case, does your subscription carry a support plan? If not, let me know and I can help open one free of charge for resolving this issue.

Come on Microsoft. @Mike Urnun any news on that? Do you actually even care about this problem? It's really a big blocker.

The problem has not been resolved.

The same here. I have my app at: https://sevigo.eu . The scenario is: first enter to the site - 502 error refresh page: upstream connect error or disconnect/reset before headers. retried and the latest reset reason: connection failure, transport failure reason: delayed connect error: 111 refresh page: page is loaded. This is Azure Container Application on Consumption plan with scale rule setting set to 0 - 10 Because of that error this app is completely unusable. Why is that?

Even i am also facing similar error. May i know what could be the possible troubleshooting steps shall i take to resolve it? upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: delayed connect error: 111

upstream connect error or disconnect/reset before headers. retried and the latest reset reason: protocol error

Andy Kepr 60

Trying to curl to my deployed container app. As far as I see the container started successfully and the listener port is running evidently by running netstat -an within the container. But a curl to the health check endpoint fails.

Host: automatoraca-app.wittymeadow-****.azurecontainerapps.io

user-agent: curl/7.78.0

accept: /

STATE: DO => DID handle 0x80007eec8; line 2068 (connection #0)
multi changed, check CONNECT_PEND queue!
STATE: DID => PERFORMING handle 0x80007eec8; line 2187 (connection #0)
HTTP/2 found, allow multiplexing

< HTTP/2 502

< content-length: 110

< content-type: text/plain

< date: Fri, 31 Mar 2023 17:43:41 GMT

nread == 0, stream closed, bailing
STATE: PERFORMING => DONE handle 0x80007eec8; line 2386 (connection #0)
multi_done
Connection #0 to host automatoraca-app.wittymeadow-4cc63852.southcentralus.azurecontainerapps.io left intact
Expire cleared (transfer 0x80007eec8)

upstream connect error or disconnect/reset before headers. retried and the latest reset reason: protocol error

Anne Hughes 35 Reputation points

2023-11-03T08:38:32.64+00:00

My problem with logging into my e-mail account started shortly after Microsoft Edge updated this morning. Believe problem is probably linked to the update. No problem prior to this. Have tried troubleshooting. Problem does not appear to be with my laptop.
Natalie Semmes 55 Reputation points

2023-11-07T19:04:31.62+00:00

I am also having problems logging into my google email account and am getting that same upstream connect error message. This was never a problem until yesterday (November 6, 2023).
Jake H 50 Reputation points

2023-12-01T16:25:30.5466667+00:00

This is now happenign to me following update this morning 1st Dec
Jake H 50 Reputation points

2023-12-01T16:25:46.2933333+00:00

@microsoft any ideas please????
sambay 35 Reputation points

2023-12-07T00:52:50.68+00:00

Can’t login to my gmail account through outlook. Fix please
Gareth Thomas 0 Reputation points

2023-12-08T11:30:35.5633333+00:00

Can’t login to gmail via outlook app on iPhone. Please help.
Karlheinz Rettig 5 Reputation points

2023-12-08T12:02:02.0266667+00:00

Same error happened to me since yesterday.
Ep 25 Reputation points

2023-12-08T16:10:33.06+00:00

Hey guys, I got this error too with Gmail account trying to login in Outlook. I was able to fix it by switching browser to Firefox. Just copied the login URL that Outlook window lead me to in Chrome and pasted in Firefox. I think it's some sort of cache issue since in Chrome it didn't ask me to verify login with authenticator but in Firefox it did.
Sewa Prakash 5 Reputation points

2023-12-08T17:40:01.81+00:00

@EP thanks for the solution it worked for me.
Marjukka Kähönen 5 Reputation points

2023-12-11T08:57:43.5733333+00:00

Thank you @Ep, it worked for me as well!
Philippe Delsart 0 Reputation points

2023-12-15T13:41:14.5866667+00:00

@EP Thanks alot, it's worked for me too!
نواف الصالح 0 Reputation points

2023-12-18T22:04:44.9233333+00:00

نعم اريد الدخول إلى الحساب
Eder F Bolaño R 0 Reputation points

2024-02-21T23:43:34.02+00:00

If you are using container apps, please review ingress configuration port and your app development port configuration must be same port

11 answers

Mike Urnun 9,811 Reputation points Microsoft Employee

2023-04-12T17:50:43.9+00:00
Hello, @Andy Kepr - Sorry for the late reply. The error message "upstream connect error or disconnect/reset before headers" indicates that the connection between the client and the server was closed before the server could send a response. The error message "protocol error" indicates that there was an issue with the protocol used to communicate between the client and the server for the health check endpoint.

This could be caused by a number of issues, such as a misconfigured firewall (if any), a network issue, or a problem with the server itself.

Generally speaking, to troubleshoot this issue, you can try the following steps:

Check the firewall settings to ensure that the port used by the container app is open.

Check the network settings to ensure that there are no issues with the network.

Check the logs of the container app to see if there are any errors or issues that could be causing the problem.

Try accessing the container app from a different network or location to see if the issue is specific to your current network.

If the issue persists, we'll likely need to work with you on a 1:1 setting and take a closer look. In such a case, does your subscription carry a support plan? If not, let me know and I can help open one free of charge for resolving this issue.
Please sign in to rate this answer.

4 people found this answer helpful.
Andy Kepr 60 Reputation points

2023-08-06T01:14:21.28+00:00

The problem persists. It seems the container cannot communicate with the app running. When I enable healthcheck to the valid healthcheck endpoint no healthchecks are going through either.

Mike Urnun 9,811 Reputation points Microsoft Employee

2023-08-21T17:30:54.7366667+00:00

Hello, @Andy Kepr - I'm sorry to hear that the issue is still impacting your ACA workflow. As the next step, we'd like to work with you in 1:1 via a direct support channel. If your subscription already carries a support plan, it'd be best to open a support case yourself. If not, please contact us at azcommunity at microsoft dotcom with the subject line "attn:murnun", and the following info included in your email:

Subscription ID

URL of this thread

Once we receive your email, we'll grant your Subscription with a one-time free-of-charge support case for resolving this particular issue.

Beard 0 Reputation points

2023-09-29T18:41:44.0233333+00:00

I was able to resolve my issue with this by updating Chrome. Might not work for everyone, but I went to Help > About Google Chrome and I had an update waiting for me.

Anne Hughes 35 Reputation points

2023-11-03T08:41:21.62+00:00

My problem only started after Microsoft Edge updated this morning. Connection had been fine prior to that.

Sewa Prakash 5 Reputation points

2023-12-07T19:56:30.66+00:00

I am having this issue from today. Can't login in my outlook. Need support

书芮吴 0 Reputation points

2024-02-26T06:51:57.13+00:00

Come on Microsoft. @Mike Urnun any news on that? Do you actually even care about this problem? It's really a big blocker.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Adam Jachocki 46 Reputation points

2023-09-08T08:51:23.62+00:00

Come on Microsoft. @Mike Urnun any news on that? Do you actually even care about this problem? It's really a big blocker.
Please sign in to rate this answer.

4 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Andy Kepr 60 Reputation points

2023-08-06T01:05:28.82+00:00

The problem has not been resolved.
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Adam Jachocki 46 Reputation points

2023-08-24T16:35:31.55+00:00
The same here. I have my app at: https://sevigo.eu. The scenario is:

first enter to the site - 502 error

refresh page:

upstream connect error or disconnect/reset before headers. retried and the latest reset reason: connection failure, transport failure reason: delayed connect error: 111

refresh page: page is loaded.

This is Azure Container Application on Consumption plan with scale rule setting set to 0 - 10

Because of that error this app is completely unusable. Why is that?
Please sign in to rate this answer.

2 people found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Gole, Pankaj 10 Reputation points

2023-08-26T07:29:44.3466667+00:00
Even i am also facing similar error.

May i know what could be the possible troubleshooting steps shall i take to resolve it?

upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: delayed connect error: 111
Please sign in to rate this answer.

2 people found this answer helpful.
Mat y Mónica 0 Reputation points

2023-12-06T08:48:43.48+00:00

Hello. I get this message using Outlook on my Android phone after not being able to sign in to my gmail account. My Google home and minis also stopped working, which could be a coincidence . I have reinstalled Outlook and now it works normally. I am in the process of resetting all my google homes and minis as nothing else works. Is this the way they say the future's meant to feel?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

upstream connect error or disconnect/reset before headers. retried and the latest reset reason: protocol error

11 answers

Your answer