How to fix "The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable."

Question

How to fix "The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable."

Krishna Moniz 5

I have an Azure web app running a docker container from an Azure Container registry.

The web app has been running fine for months, but all the sudden (I have made no changes), the app became unresponsive.

When accessing the app, I get a 504.0 GatewayTimeout error.
I tried restarting the instance (see health check image). The problem persists.

I tried replacing the instance (see diagnostic image). The problem persists.

The ssh is not accessible.

The activity log shows a "Get Zipped Container Logs" (see activity log image) not found error.

What is the problem?
How do I get my app accessible again?

screenshots

Aditya N 3,810 Reputation points Microsoft External Staff Moderator

2026-06-16T16:44:38.66+00:00

Hello @Krishna Moniz

Thank you for reaching out Microsoft Q&A. Please could you provide the name of web app over private message.
Krishna Moniz 5 Reputation points

2026-06-17T14:07:54.2133333+00:00

Hello,

I provided the name of the web app over private message. I didn't get any response, but it works now...
Maybe you guys fixed. Maybe it fixed itself. I don't know...

I would appreciate an explanation of what went wrong, but I'll take the issue magically disappearing.

Consider this issue resolved.
Aditya N 3,810 Reputation points Microsoft External Staff Moderator

2026-06-17T15:42:20.5366667+00:00

Hello @Krishna Moniz

Thank you for letting us know that your issue is resolved. When checked it looks like there are container timeout issues. The default timeout is 230 seconds.

1 answer

Your answer

Aditya N 3,810 Reputation points Microsoft External Staff Moderator

2026-06-16T16:44:38.66+00:00

Hello @Krishna Moniz

Thank you for reaching out Microsoft Q&A. Please could you provide the name of web app over private message.
Krishna Moniz 5 Reputation points

2026-06-17T14:07:54.2133333+00:00

Hello,

I provided the name of the web app over private message. I didn't get any response, but it works now...
Maybe you guys fixed. Maybe it fixed itself. I don't know...

I would appreciate an explanation of what went wrong, but I'll take the issue magically disappearing.

Consider this issue resolved.
Aditya N 3,810 Reputation points Microsoft External Staff Moderator

2026-06-17T15:42:20.5366667+00:00

Hello @Krishna Moniz

Thank you for letting us know that your issue is resolved. When checked it looks like there are container timeout issues. The default timeout is 230 seconds.

Answer 1

Hi @Krishna Moniz

Thank you for the update — I’m really glad to hear your web app is accessible again!

Based on the screenshots you shared earlier, the key message was that the container “did not start within the expected time limit of 230 seconds.” This isn’t usually the root cause itself, but a symptom that the container took longer than expected to initialize and respond to Azure’s internal health check. The platform automatically retried and eventually recovered the instance — which is why it started working again without any changes from our side.

To help prevent this from recurring, here are a few targeted recommendations:

Increase container startup timeout Add the application setting WEBSITES_CONTAINER_START_TIME_LIMIT with a value of 600 (or up to 1800 seconds). This gives your container more time to start.

Reference : https://learn.microsoft.com/en-us/azure/app-service/reference-app-settings?tabs=kudu%2Cdotnet

Verify port configuration Ensure your app is listening on the correct port (default 80) or set WEBSITES_PORT if using a different one.

Reference : https://learn.microsoft.com/en-us/azure/app-service/configure-custom-container?tabs=debian&pivots=container-linux

Enable detailed logging Turn on Application logging (Filesystem) under Monitoring > App Service logs for better startup visibility next time.

Since the application is now working as expected, we can consider this issue resolved. However, if the problem returns or you’d like me to review the latest logs/diagnostics, just let me know the web app name and I’ll take a look.

Thank you again for your patience and cooperation!

If the answer(explanation) is helpful, Please do click "Accept the answer” and Yes, this can be beneficial to other community members.

If you have any other questions, let me know in the "comments" and I would be happy to help you