Does ProGet support creating and managing local groups for users authenticated via LDAP i.e. LDAP-authenticated users, but groups defined and managed locally in the system?

Is it possible to disable import or syncing of LDAP groups when integrating with an LDAP directory?

When trying to resolve a Maven package using Gradle through a Maven feed that’s configured with a third-party registry, e.g. public Maven or internal Maven via a connector, the server responds with a 500 Internal Server Error with message: Value cannot be null. (Parameter 's')

Additional context:

• We did not enable Local Indexing
• We did not pre-download the packages to the feed
• The Maven feed only has a connector setup to a remote repository, no locally cached artifacts

How can we resolve or work around this issue?

System information:

Web UI Version: 2025.5 (Build 16)
Database Schema Version: 25.0.5.16
SQL Server Version: PostgreSQL 17.5 (Debian 17.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
db_owner: True
Database Name: proget
Database Collation: C (UTF8)
Database Recovery Model: Default (1)
Database Read Committed Snapshot: True
Database Auto Update Stats: True

Hi ProGet team,

I was reading through the backup documentation and saw this statement:

"For smaller, single-server installations, you may find it easiest to simply take a snapshot of the Virtual Machine the product is running on. As long as all components are hosted on a single virtual machine, this will sufficiently backup the product."

Just wanted to clarify how this works in a restore scenario.

If the VM containing the ProGet docker deployment is backed up or snapshotted and later restored into a different cluster (with different underlying hardware), will ProGet work simply by starting the container services? Or are licenses tied to hardware-specific identifiers (CPU, MAC, etc.) that could cause issues after restoring the VM elsewhere?

Basically trying to confirm whether a full VM restore is enough, or if there are licensing steps needed after moving the VM.

Thank you.

Hi @rhessinger ,

Thanks for your help! I’m fine waiting until the release next Friday.

Hi @rhessinger,

I don’t think the reverse proxy strips the component API. In the configuration of the reverse proxy, we map a URL to a port, so when a client accesses the server using a specific URL, the request is routed to the corresponding listening port.

Thanks.

Hi @rhessinger ,

The pseudo-group/subgrouping/groups are just arbitrary name for possible parent groups.

This is a screenshot of the layout when the image are published to Nexus.

Thanks.

Hi @rhessinger,

Thanks for the reply. I am running Nexus 3.76.1.

Here's the response from the API:

{
  "items" : [ {
    "id" : "<obfuscated>",
    "repository" : "docker",
    "format" : "docker",
    "group" : "",
    "name" : "pseudo-group/subgrouping/groups/individual/project/image",
    "version" : "stable",
    "assets" : [ {
      "downloadUrl" : "https://my-nexus-server.foo.bar.com/repository/docker/v2/pseudo-group/subgrouping/groups/individual/project/image/manifests/stable",
      "path" : "/v2/pseudo-group/subgrouping/groups/individual/project/image/manifests/stable",
      "id" : "<obfuscated>",
      "repository" : "docker",
      "format" : "docker",
      "checksum" : {
        "sha256" : "<obfuscated>",
        "sha1" : "<obfuscated>"
      },
      "contentType" : "application/vnd.docker.distribution.manifest.v2+json",
      "lastModified" : "2025-12-02T12:15:33.452+00:00",
      "lastDownloaded" : null,
      "uploader" : "<obfuscated>",
      "uploaderIp" : "<obfuscated>",
      "fileSize" : <obfuscated>,
      "blobCreated" : "2025-12-02T12:15:33.454+00:00",
      "blobStoreName" : null,
      "docker" : { }
    } ]
  } ],
  "continuationToken" : null
}

The Docker API Override URL is set to https://nexus-registry.foo.bar.baz.com/v2/ which is the URL returned by the docker client.

Here's the outputs when running the migration:

info: System.Net.Http.HttpClient.Default.LogicalHandler[100]
      Start processing HTTP request GET https://nexus-registry.foo.bar.baz.com/v2/ouping/groups/individual/project/image/manifests/stable
info: System.Net.Http.HttpClient.Default.ClientHandler[100]
      Sending HTTP request GET https://nexus-registry.foo.bar.baz.com/v2/ouping/groups/individual/project/image/manifests/stable

Hope the info above is helpful. Thanks!

Hi ProGet team,

Thanks for adding support to override the Docker API URL. However, during my testing, it doesn’t seem to work as expected.

For Docker images with long paths, based on the logs, it appears that the requested URL path is truncated. I’m not sure if this is just a visual effect in the logs or if the actual request is being truncated. For example, the URL should be:

https://nexus-registry.example/v2/my-example/subgroup/container/project/subname/image/manifests/stable

but the log shows:

https://nexus-registry.example/v2/group/container/project/subname/image/manifests/stable

and it returns a 404, even though I can access the original URL directly in the browser.

Furthermore, with shorter image paths, e.g.:

https://nexus-registry.example/v2/python/manifests/3.11.2-bullseye

I don’t see the request in the log, and it fails with the following error message:

Error: Unhandled exception: System.ArgumentOutOfRangeException: startIndex cannot be larger than length of string. (Parameter 'startIndex')
   at System.String.ThrowSubstringArgumentOutOfRange(Int32 startIndex, Int32 length)
   at System.String.Substring(Int32 startIndex, Int32 length)

I would appreciate any guidance on this matter.

Thank you for your support!

Hi @rhessinger,

Our Nexus docker repository is configured to use specific port (e.g. port 8080), but this port is not exposed externally. Here's an example response returned by the Nexus endpoint:

{
  "name" : "example",
  "url" : "https://nexus-example/repository/example",
  "online" : true,
...
  "docker" : {
    "v1Enabled" : false,
    "forceBasicAuth" : true,
    "httpPort" : 8080,
    "httpsPort" : null,
    "subdomain" : null
  },
...
  "format" : "docker",
  "type" : "hosted"
}

Instead, we have a proxy server that maps a custom URL (e.g., https://nexus-docker/) to the internal Nexus port.

All Docker operations (push/pull) work correctly through this custom URL.

Could this proxy-based URL mapping affect the Docker migration feature, or is there a way to specify the external (proxy) URL for migration?

Thanks.

Hi ProGet team,

I’m trying to use the Docker migration feature in ProGet to import images from a Sonatype Nexus repository, but it doesn’t seem to be working as expected with the following error.

ERROR: Unhandled exception: System.Net.Http.HttpRequestException: Response status code does not indicate success: 404 (Not Found).

The Nexus docker repository can be found in the selection of the import dialog.

Before I proceed further, I’d like to confirm whether there are any specific requirements or limitations for this migration feature.

In our setup:

• The Nexus Docker repository is configured using a port connector.
• We have a proxy server that maps this port to a different external URL.

Would this configuration affect or break the migration process?
If so, is there a recommended way to handle such setups?

Any clarification or documentation on the expected configuration for Docker migration from Nexus would be greatly appreciated.

Thanks.

Hi @atripp,

Thanks for the reply.

Could you elaborate more on the data deduplication you mentioned?

Additionally, is there any documentation or guide on how to configure or enable this?

Thanks in advance for your help.

Hi ProGet team,

I came across the blog post mentioning that high traffic from around 50 or more users on a single-server ProGet instance can lead to issues such as HTTP request timeouts, unhandled exceptions, and temporary service unavailability.

I’d like to understand more about the performance capacity of a single ProGet instance, particularly when running the official Docker image with the embedded PostgreSQL server.

The documentation lists the recommended container sizes (up to 4 vCPU and 8 GB RAM for “Large”), but I’m wondering:

• What kind of workload or number of concurrent requests the “Large” configuration is expected to handle reliably
• Whether scaling resources beyond that point would improve performance
• Or if it’s generally more effective to move to an external PostgreSQL setup or a load-balanced configuration instead

Any guidance, documentation, or internal benchmarks on this would be greatly appreciated.

Thanks!