I am re-deploying with a minor change, a docker container, Azure WebApp. The container runs locally without any issues.

docker buildx build --platform linux/amd64,linux/arm64 -t myregistrybasic.azurecr.io/myapp-api-test:v5 --push .

The container builds, I restart my webapp but I only get ":( Application Error". In the logs I only see

Connected! :( Application ErrorIf you are the application administrator, you can access the <a style="color: grey"href=";>diagnostic resources.

I tried re-starting with another container from the registry which runs without issues on another webapp, same result. I tried creating a new webapp, same result. I can't ssh to the contaniner cause or open Kudu cause I get a 503. Not sure what else I can do.

I am re-deploying with a minor change, a docker container, Azure WebApp. The container runs locally without any issues.

docker buildx build --platform linux/amd64,linux/arm64 -t myregistrybasic.azurecr.io/myapp-api-test:v5 --push .

The container builds, I restart my webapp but I only get ":( Application Error". In the logs I only see

Connected! :( Application ErrorIf you are the application administrator, you can access the <a style="color: grey"href="https://myapp-test-2.scm.azurewebsites/detectors">diagnostic resources.

I tried re-starting with another container from the registry which runs without issues on another webapp, same result. I tried creating a new webapp, same result. I can't ssh to the contaniner cause or open Kudu cause I get a 503. Not sure what else I can do.

• azure
• azure-web-app-service

1 Answer 1

I ended up scaling up the app service plan and scale back and now everything works. Doesn't seem like an ideal solution. I was inspired by this: Why the Kudu site for my app service is showing 503 Service Unavailable