An error occurred: CONNECTIVITY_CHALLENGE_ERROR Registry '*****.azurecr.io' did not issue a challenge.

[brightonk]

has anyone faced the issue. How did you resolve

== I used the below command. The output is below the command ==

$ az acr check-health -n *******Containers --yes Docker daemon status: available Docker version: 'Docker version 20.10.8, build 75249d8, platform linux/arm64' Docker pull of 'mcr.microsoft.com/mcr/hello-world:latest' : OK Azure CLI version: 2.37.0 DNS lookup to containers.azurecr.io at IP 52.236.191.0 : OK An error occurred: CONNECTIVITY_CHALLENGE_ERROR Registry '.azurecr.io' did not issue a challenge.

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

== the link above gave the details below ==

CONNECTIVITY_CHALLENGE_ERROR This error means that the challenge endpoint of the target registry did not issue a challenge.

Potential solutions: Try again after some time. If the error persists, open an issue at https://aka.ms/acr/issues.

[hluckenbaugh]

I am having the same issue.

[northtyphoon]

@brightonk @hluckenbaugh please open the support ticket if the problem still persists. https://aka.ms/acr/support/create-ticket Azure support team will help collect the registry detail to troubleshoot.

[OlaNystein]

I have the exact same problem. It worked on friday, but error suddenly happened when trying to login to acr this monday.

[williamcollin]

I'm having the same issue.

[OlaNystein]

It fixed itself after a day, still don't know why the error occured

[marouanabbessi]

I have the same exact problem, this has persisted for many days: I am trying to login to a private ACR through a private edpoint.

[marouanabbessi]

This is very urgent and help is needed

[stevenpedroza]

I have the same error

[sajayantony]

Please open a support ticket through the portal and provide the details like region and the registry so that the issue can be routed and diagnosed.

[stevenpedroza]

I found my solution, try to put the agent inside the same subnet as the private point. If you don't have it like that, you have to create a link between the networks.

You have to check that in ACR->Networking->Private Access->Private endpoint (We click on it)

We go to DNS configuration, and copy the private ip that has the FQDN, example myacrr312.privatelink.azurecr.io = IP:10.0.0.5.

Later in the same window, in private DNS zone, you have to click on the name that appears in blue.

It has to be the Registry name and the IP 10.0.0.5 (in my case). If not, you have to add yours manually in the Record Set.

All the best.

[marouanabbessi]

I was accessing ACR through a user-assigned managed identity, it was working fine until all of the suddent , the registry no longer intitiate identity challenge which was failing the login, now I had to resort to enabling admin credentials (username and password) instead , so this does not seem to have a problem with the fact that it is accessed through a privare endpoint, verw eird situation with very cryptic error message

[terencet-dev]

Closing as this has been inactive for over two months. Please open a support ticket for additional support/guidance. Thanks

[marouanabbessi]

@terencet-dev you are quick to close this, could you offer an explanation why this error occurs ? this has occurred another time to me now, please check internally and provide an explanation for why this error occurs intermittently

[helayoty]

Issue still occurs with az version 2.49.0 @terencet-dev