I’ve setup a nexus3 container running 3.82.0-08. It’s behind an apache reverse proxy that provides SSL. I’ve configured a ChocolateyInternal nuget v3 proxy pointing to our internal Chocolatey for business nexus server. I see that in the repository/ChocolateyInternal/index.json file returned it contains items like:
| resources | |
|---|---|
| 0 | |
| @id | https://PROXYURL/repository/ChocolateyInternal/v3/content/0 |
| @type | PackageBaseAddress/3.0.0 |
| @nxrmRemote | https://C4BFQDN:8443/repository/ChocolateyInternal/v3/content |
and it seems that chocolatey clients attempt to contact the C4B server directly, which I don’t want. Is it supposed to be re-writing those nxrmRemote URLs?
I also see messages like this in the downstream nexus output:
nexus3[1762]: 2025-08-14 22:56:28,667+0000 WARN [qtp622396011-2603] *UNKNOWN com.sonatype.nexu
s.repository.nuget.datastore.internal.NugetProxyDispatcherFacet - Exception java.net.SocketTimeoutException: Re
ad timed out checking remote for update, proxy repo ChocolateyInternal failed to fetch https://PROXY/repository/ChocolateyInternal/v3/content/dotnetfx/4.8.0.20220524/dotnetfx.4.8.0.20220524.nupkg, content not in cache.
I don’t understand why it appears to be attempting to fetch content from itself rather than the C4B server.