Maven Nexus V3 remote repository integration with Artifactory

I am setting up Nexus3 repository as a remote repository in Artifactory. But when I update the Nexus3 repo URL(https://domainname/repository/reponame/) & necessary credentials for authentication in the admin section, during testing i am getting,

Connection failed: Error 404.

I have tried providing the rest URL(http://domainname/service/rest/repository/browse/reponame). In this case, connection to the nexus server establishes successfully & able to see the directory structure for the remote repo in the Artifacts section , but could not find the artifacts inside & seeing below output/error,

{ “errors” : [ { “status” : 404, “message” : “Couldn’t find item: XXXX:XXXXXXX” } ]

I have tested the same with nexusV2(domainname/nexus/content/repositories/reponame), I was able to successfully authenticate to the nexusV2 server & was able to pull artifacts from Artifactory, i have issue only when i test with NexusV3 (3.16.2-01, 3.3.x)

It sounds like Artifactory has some specific handling for the HTML directory listing of Nexus Repo 2.x. The way Nexus Repo 3.x works is different, so that won’t work.

But the fact that you can’t browse the remote directory listing does not mean the proxy isn’t working. Use the regular repository URL as the remote (https://domainname/repository/reponame/) and try running a build that requests artifacts from the remote repo.

Hi, seems like issue is resolved after saving the settings with https://domainname/repository/reponame/ URL , even though testing the URL before saving it gave me Connection failed: Error 404.
After running maven build, Artifactory was able to fetch the artifacts from Nexus Remote Repo

1 Like

Have you found any solution for this problem.
We have problems with teh new osgeo remote repository Repository - Nexus Repository Manager
This is also a nexus 3.x repo.
The test in Artifactory gives a 404.
The weburl of this remote repo is ok for Artifactory Index of /
But in Artifactory you get only the directory structure and not the artifacts itself.

The advice from Jfrog support was to have a virtual repo with both the url definitions.
But that is no solution for getting the right artifacts. You stil can not download for example a version directory. You have to specify the artifacts seperatly

Same issue here. Artifactory fails to fetch the artifacts.

Regards Martin

Same issue here. i am trying to create a Nexus NPM repo proxying remote repo at Artifactory. same works for Maven format. but 404 error for NPM.

It sounds like your issue is different, the others are having difficult with Artifactory fetching artifacts from Nexus, while you seem to suggest you’re having a problem with the reverse.

So, we have a workaround - use the regular repository URL and ignore error 404, but does anyone know is Sonatype going to solve this problem?

That’s exactly what resolved my issue
add the URL without testing or even browsing the repo
then building the Gradle project!
Thant you!

There isn’t a problem with Nexus Repository, this is an issue with Artifactory’s testing mechanism.