Webhooks not working East 2 data center

Bob_M 0 Reputation points
2024-06-26T20:04:12.87+00:00

Hello All,

A few weeks ago, auto deployment stopped working for Web Apps connected to an image in a container registry. This only happened for Web Apps in the East 2 data center across multiple subscriptions. Web Apps in East data center are working fine. We have tried creating new container registry and reassociating with Web app and it still fails to respond pusshing a new image to the container registry. Stopping and starting the Web Apps will pull the container properly from the container registry. (This is our work around.) Web Hooks do answer to ping. Anyone else experiencing this? Thanks

Azure App Service
Azure App Service
Azure App Service is a service used to create and deploy scalable, mission-critical web apps.
7,726 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Grmacjon-MSFT 17,886 Reputation points
    2024-07-11T20:43:24.2733333+00:00

    @Bob_M we are sorry to hear you're this issue. Are you still experiencing this issue?

    It might be an authentication issue were your Web Apps might trouble authenticating with the container registry despite successful WebHooks ping responses OR a network restriction in East 2 could be preventing Web Apps from accessing the container registry. Is the Azure Container Registry using Public Access or Private Endpoints?

    To troubleshoot: please double-check the container registry credentials used by the Web Apps. Consider using the "private registry" tab in the container settings instead of relying on ACR integration. Provide your ACR credentials directly in the Web App configuration.

    Also, explore using Azure DevOps pipelines or other CI/CD tools to automate deployments. These tools can trigger deployments based on code changes or image pushes.

    Best,

    Grace

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.