@misael-esperanzate_5668 thanks for the reproduction details! I was ablet to reproduce this very easily and fixed it via PG-3091 - it was an ordering problem This will be in the upcoming maintenance release this Friday

Hi @misael-esperanzate_5668 , Although ProGet can handle invalid version numbers for Maven packages, this one is a extra invalid version number (it starts with a "v") and unfortunately we can't support them at this time. ProGet requires that packages follow the ~20 year Maven standard that "packages start with a letter and versions start with a number". Sadly this team didn't like those standards and opted to do their own thing. The issue comes with identifying whether com/google/apis/google-api-services-healthcare/v1-rev20240731-2.0.0 is an artifact or a version. Because ProGet is not a basic file server, things like package names and versions matter. Anyway this will require a significant and risky change to the API so we won't consider it at least for another major release. -- Dean

Hi @misael-esperanzate_5668 , That makes perfect sense; when package caching is enabled, the package files are added to the feed and stored on disk. When it's not enabled, they are simply streamed from the server. Something is interfering with your disk storage that is deleting (quarantining) files on disk. You will need to follow the troubleshooting I identified above - it's probably a security tool. Suggest using AWS Lightsail to get a test box in an environment you can control. Thanks, Steve

Hi @misael-esperanzate_5668, Currently, ProGet uses the nexus-maven-repository-index.gz file to see what artifacts are in a Maven repository, and then downloads the files based on that. So you'll need to enable that index file by doing this, I think: https://jfrog.com/help/r/jfrog-artifactory-documentation/maven-indexer This only applies to Maven indexes, and that file is only used for importing/downloading a feed into ProGet. For other feed types, a different API is used. Good news --- in an upcoming maintenance release of ProGet, we will be shifting to use the Artifactory API directly to import artifacts from a repository. Thanks, Steve