You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- [x ] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
Minimal steps to reproduce
I deployed to code to Azure
Ran the node.js app by clicking on its FQDN
Click the button run the dotnet app/container
Any log messages given by the failure
upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: delayed connect error: 111
Expected/desired behavior
I expected to get a response from the dotnet app container
OS and Version?
Container instance is running on linux
Versions
Mention any other details that might be useful
Thanks! We'll be in touch soon.
The text was updated successfully, but these errors were encountered:
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: delayed connect error: 111
Expected/desired behavior
I expected to get a response from the dotnet app container
OS and Version?
Container instance is running on linux
Versions
Mention any other details that might be useful
The text was updated successfully, but these errors were encountered: