Sonatype Nexus Repository Manager OSS 3.37.1-01

We have created a proxy to maven central (Central Repository:) and for last 2 days we are experiencing random status going to Remote Auto Blocked. Question is does Maven central repo black lists an IP ? As this issue start to surface since 2 days and that is also a random issue. Central Repository: if browsed through a different public IP responds so it wasn’t the case that repo was down. If blacklisting happens what is the way to whitelist an IP?
Thanks,
Sidd

We had same problem last year. The problem was, that some people in the company wasn’t use the Nexus but directly Central Repo with http instead https. In this case our IP was blocked reglary. After the co-workers switched to Nexus all works fine.

Regards,
Rafal

1 Like

Thanks for the response. Do you happen to know, if even on https an IP can be blocked if there are several requests hitting central repository?

Please create an issue using this link:

https://issues.sonatype.org/secure/CreateIssue.jspa?issuetype=17&pid=10302

and we can help track down what’s going on.

Thanks Joel. Before I create a ticket and I just want to confirm again below-

We noticed below message in the logs of Sonatype Nexus Repository ManagerOSS 3.37.1-01. During this time, we were not able to download any artifact from repo and all our builds were stuck. Was there really any issue for repo1.maven.org or was my company’s public IP blocked temporarily? This happened multiple times on 19th and 20th Jan. But after that everything is working fine and I do not see any more log like this. I am afraid this may happen again and want to ensure that my builds are not impacted randomly.

2022-01-20 14:27:24,377+0530 INFO [Check Status *UNKNOWN org.sonatype.nexus.repository.httpclient.internal.HttpClientFacetImpl - Repository status for maven-central continued as AUTO_BLOCKED_UNAVAILABLE until 2022-01-20T14:30:44.377+05:30 - reason javax.net.ssl.SSLException: Read timed out for [https://repo1.maven.org]