Caching Unity packages

[MrMatthias]

The documentation says that it’s possible to cache the unity packages via a custom package registry.
How would i do that?

Some organizations work inside a closed network, which makes it difficult to access Unity’s own package registry. In these cases, the organization can set up their own package registry on a server inside their closed network. The network administrators can then periodically synchronize with Unity’s package registry to make sure the scoped registry has the latest set of packages available.

I set up a verdaccio npm registry with an uplink to https://packages.unity.com

uplinks:
  upm:
    url: https://packages.unity.com
    cache: true

the package manifest looks like this

“scopedRegistries”: [
{
“name”: “local”,
“url”: “http://127.0.0.1”,
“scopes”: [
“com”
]
}
],

This is the log:

warn — Verdaccio started
warn — Plugin successfully loaded: verdaccio-htpasswd
warn — Plugin successfully loaded: verdaccio-audit
warn — http address - http://0.0.0.0:80/ - verdaccio/4.8.1
http ← 404, user: null(127.0.0.1), req: ‘GET /-/v1/search?text=com&from=0&size=250’, error: File not found
http ← 404, user: null(127.0.0.1), req: ‘GET /com.unity.package-manager.metadata’, error: no such package available
http ← 404, user: null(127.0.0.1), req: ‘GET /com.unity.collab-proxy’, error: no such package available
http ← 404, user: null(127.0.0.1), req: ‘GET /com.unity.ide.vscode’, error: no such package available
http ← 404, user: null(127.0.0.1), req: ‘GET /com.unity.test-framework’, error: no such package available
http ← 404, user: null(127.0.0.1), req: ‘GET /com.unity.ide.rider’, error: no such package available
http ← 404, user: null(127.0.0.1), req: ‘GET /com.unity.textmeshpro’, error: no such package available
http ← 404, user: null(127.0.0.1), req: ‘GET /com.unity.timeline’, error: no such package available
http ← 404, user: null(127.0.0.1), req: ‘GET /com.unity.ext.nunit’, error: no such package available
error— uplink error: bad status code 404 from uplink
http ← 200, user: null(127.0.0.1), req: ‘GET /-/all’, bytes: 0/227

[Adrian]

Did you add a packages entries that specifies the uplink with proxy? I don’t think just adding the uplink on its own does anything, it needs to be used in a packages directive.

See here: Package Access | Verdaccio

e.g.

packages:
  '**':
    access: $all
    proxy: upm

[MrMatthias]

@Adrian

Did you add a packages entries that specifies the uplink with proxy? I don’t think just adding the uplink on its own does anything, it needs to be used in a packages directive.

See here: https://verdaccio.org/docs/en/packages

e.g.

packages:
  '**':
    access: $all
    proxy: upm

Yes, thank you, it was still referring to the npmjs uplink.
Would it be possible to redirect https://packages.unity.com from all workstations to the local server behind nginx?
In previous unity manual versions it was said that:

Unity Package Manager’s underlying HTTPS layer rejects these self-signed certificates because it does not recognize them, and treats the connection as a possible man-in-the-middle attack

Is it now possible to add a CA?

[Adrian]

Yes, look at the manual: Unity - Manual: Solving network issues