This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(297.6, 1%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Hello, Starting today all my container apps are not available, I get timeout errors with "stream timeout" message displayed (http 504). The revisions are in failure state. My app is a simple docker image using apache web server and PHP single page. I can successfully connect to the console log stream, with logs from the container saying the app started ok. But I cannot navigate to the web url properly. Did something changed with Ingress for container apps? My app expose port 80 by default. Thanks.
Ok after some investigation, if I create a new container app on a new environment, it works. But if I create a new app in an existing environment, it fails. Keep investigating...
Well, today I found the containers working again. No explanation from Microsoft, no clue of what happened. I have opened a ticket to the support, I'll share the details if they are able to give some explanations.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 87%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMU%3C/text%3E%3C/svg%3E)
Hi @Sylvain - I didn't see any platform issue based on the timeframe you reported the issue occurred. I'll continue to check and get in touch with the engineer assigned to your case.
Upon further investigation, we confirmed that this was an issue caused by regression affecting limited regions. @Sylvain has confirmed via support case that they're no longer experiencing the issue.
Here are some of the related threads affected by the same issue: