Unable to login into azure acr

[pravanjanrath]

I am facing 2 issues :

1. When I click on repositories in acr I get below error : "Unable to send request for fetching repositories. Click here for possible reasons." I have attached screenshot for the same.

2. When I try to login to acr using az acr login command I get below error :

C:\Users\prava>az acr login --name readitpravacr
Could not connect to the registry login server 'readitpravacr.azurecr.io'. Please verify that the registry exists and the URL 'https://readitpravacr.azurecr.io/v2/' is reachable from your environment.
Try running 'az acr check-health -n readitpravacr --yes' to diagnose this issue.

C:\Users\prava>az acr check-health -n readitpravacr --yes
Docker daemon status: available
Docker version: 'Docker version 26.0.0, build 8b79278, platform linux/amd64'
Docker pull of 'mcr.microsoft.com/mcr/hello-world:latest' : OK
Azure CLI version: 2.60.0
DNS lookup to readitpravacr.azurecr.io at IP 20.62.128.0 : OK
2024-05-18 06:54:20.208894 An error occurred: CONNECTIVITY_CHALLENGE_ERROR
Registry 'readitpravacr.azurecr.io' did not issue a challenge.

Please refer to https://aka.ms/acr/errors#connectivity_challenge_error for more information.

[cegraybl]

@pravanjanrath I'm part of the ACR team, I'm checking logs from our back end and I don't see failures around that time stamp. The result of check-health seems to indicate a connectivity issue from the client. Can you share additional details? If you run the command with the --debug option you should see the correlation-id header for the requests, we can use that to trace the call.

[cegraybl]

Similar to the errors in portal, if you open the console (F12 in most browsers) you should be able to see the call that fails/times-out, we can use the correlation id from the header to track the issue.

[johnsonshi]

Hi @pravanjanrath, have you had any updates on your authentication issue? As one of our engineers indicated in the previous comment, there were no connectivity issues on our side logged when this was investigated. Given the age of the issue, please feel free to re-open another issue if you encounter auth issues with your ACR.