Hello! So, here’s the scenario: Nexus instance A (3.18.0) repo A-hosted: npm hosted repo A-group: npm group that contains A-hosted (and other things) Nexus instance B (3.18.0) repo B-proxy: npm proxy of A-group; component and metadata age set to -1; no negative cache repo B-group: npm group t…

The maximum metadata age setting in a proxy determines how often Nexus Repo will check the remote for updates to package metadata (e.g., newly available versions). By default it is 1440 minutes (24 hours). Reduce that timeout if more frequent updates are needed. Rich

@rseddon so setting it to -1 has no effect?

Setting it to -1 definitely has an effect, that makes the cache timeout infinite, so Nexus Repo will never check for updates. Set it to 0 if you want to have Nexus always check.

I still have the issue with maven snapshot proxy repo. For Maximum metadata age, tried both 1 and 0. Had to “Rebuild index” to get it to work.

[image] drodnexus: Maximum metadata age how to do that in the version Sonatype Nexus Repository ManagerOSS 3.22.0-02

Npm proxy not getting new packages

Sonatype Nexus Repository

rseddon (Rich Seddon) April 6, 2020, 7:22pm 8

Set a new value for it in the proxy repository’s configuration page.

Rich

Topic		Replies	Views
Proxy repository not refreshing metadata even with max age 0 Sonatype Nexus Repository nexus-repository	2	569	May 13, 2024
Nexus proxyrepo not syncing with remote hosted-repo Sonatype Nexus Repository	7	13262	August 20, 2019
Nexus setup as npmjs.com proxy but missing latest versions of packages Sonatype Nexus Repository	1	979	January 4, 2023
Nexus npm proxy repo can't find package Sonatype Nexus Repository	3	6009	August 2, 2019
Nexus npm Proxy Fetching Metadata Externally Despite Cached Packages Sonatype Nexus Repository help , nexus-repository , proxy , npm , metadata	1	130	March 11, 2025

Npm proxy not getting new packages

Related topics