# Autoblock status not resolved for proxied repo

**URL:** <https://community.sonatype.com/t/autoblock-status-not-resolved-for-proxied-repo/8354>\
**Category:** Sonatype Nexus Repository\
**Tags:** nexus-repository\
**Created:** [March 8, 2022, 5:58pm UTC](https://community.sonatype.com/t/autoblock-status-not-resolved-for-proxied-repo/8354 "2022-03-08T17:58:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![david.welch](https://avatars.discourse-cdn.com/v4/letter/d/8491ac/32.png) [@david.welch](https://community.sonatype.com/u/david.welch)\
**Post date:** [March 8, 2022, 5:58pm UTC](https://community.sonatype.com/t/autoblock-status-not-resolved-for-proxied-repo/8354/1 "2022-03-08T17:58:02Z")

</div>

We are proxying Maven and Grails repos and see cases where they become auto blocked and do not resolve even though the upstream is available. I am trying to understand what the underlying reason is.

Our hypothesis is that the build process is trying to pull packages that do not exist in the proxied repos and it keeps re-triggering auto block. Our build process iterates through repos and pulls packages from proxied repos as well as internal repos. I see logs messages like:

> 2022-03-07 09:09:08,636-0600 INFO [Check Status [https://repo.grails.org](https://repo.grails.org)] \*UNKNOWN org.sonatype.nexus.repository.httpclient.internal.HttpClientFacetImpl - R  
> epository status for _REPO\_NAME_ continued as AUTO\_BLOCKED\_UNAVAILABLE until 2022-03-07T09:12:28.635-06:00 - reason Internal Server Error for [https://repo.gr](https://repo.gr)  
> [ails.org](http://ails.org) (previous reason was Internal Server Error for [https://repo.grails.org](https://repo.grails.org))

Is there any way to mitigate the issue? I do not think setting up a group repo will work for our use case.

We are running Nexus 3.37.3.

Thanks,  
Dave

---

<div class="post-metadata">

**Author:** ![mmartz](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@mmartz](https://community.sonatype.com/u/mmartz)\
**Post date:** [March 8, 2022, 6:34pm UTC](https://community.sonatype.com/t/autoblock-status-not-resolved-for-proxied-repo/8354/2 "2022-03-08T18:34:58Z")

</div>

The problem you are running into is that JFrog Artifactory repositories return a 5xx error response when it _should_ be returning a 4xx response for missing content. I’m asking around to see if we identified a workaround but the problem is that Repository Manager can’t tell the difference between a broken server and a JFrog Artifactory server.

---

<div class="post-metadata">

**Author:** ![mmartz](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@mmartz](https://community.sonatype.com/u/mmartz)\
**Post date:** [March 8, 2022, 6:37pm UTC](https://community.sonatype.com/t/autoblock-status-not-resolved-for-proxied-repo/8354/3 "2022-03-08T18:37:38Z")

</div>

I guess the only real workaround is to disable the auto-blocking functionality for that repository. Sadly, this means if Artifactory goes offline the repository won’t block itself.