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 @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!

Hi @stevedennis,

Thanks for the update! I’m fine with waiting for the official release.

Hi @stevedennis,

I see, thanks for the explanation. However, based on the logs from running the retention rules in dry-run mode, it shows that foo.zip and bar.zip — which were newly uploaded to the assets directory and haven’t been downloaded yet — are marked for deletion.

Will this actually happen during the real run, or is it just a misleading result from the dry-run output?

Retention Rules Configuration:

Output logs:

Running in dry run mode...
Checking rule 1...
Only delete packages that have not been requested in the last 90 days (since 08/07/2025 14:50:16)
Finding packages that match retention rule 1...
Getting count of matching packages...
2 packages qualify for deletion under this rule.
Deleting matching packages...
Dry run mode is set; nothing will actually be deleted.
Deleting example/foo.zip ...
Deleting example/bar.zip ...
Deleted 2 packages (154347 KB total).
Done checking rule 1.

Hi @stevedennis,

Thanks for the input. I would like to understand more on what the command do. Does the command only reset the Administrator password (as the name suggests), or does it also recreate the Administrator user and reassign the Administer role/privileges if that privileges were removed? I want to be sure whether running it is safe when the privileges were deleted versus only when the password is lost.

Also — a small documentation/case-sensitivity note I ran into: the command shown in the docs appears as proget on Linux (image version 25.0.13), not ProGet.Service. Since Linux is case-sensitive, that difference matters and could confuse people following the instructions. Could the docs be updated or clarified?

Appreciate any details on the exact effects of the reset command. Thanks!

Hi ProGet team,

While configuring the retention rules to manage when files should be deleted, I noticed something that I’d like to confirm.

When using the setting Recent downloads: Never delete recently downloaded files, it appears that the rules are applied to newly created files that haven’t been downloaded yet.

If my understanding is correct, this means a local artifact that was recently created — but has not yet been downloaded — could still be deleted when the retention rules run.

Is this the expected behavior?
And is there a way to ensure that newly created files (e.g., files younger than a certain number of days) are not deleted by the retention rules?

Thanks in advance for any clarification or best practices!

Update:

I was able to restore the Administer role to the Administrator group by editing the database directly.

I’m now curious if there’s a safer way to do this, or a way to prevent accidentally removing critical roles, since currently it can happen without any warning.

Hi ProGet team,

I accidentally removed the Administer rights for the Administrator group, and now it no longer has the permissions to manage the instance.

Environment:

• ProGet version: 25.0.12; container

Is there any way to restore the admin rights without reinstalling or resetting the entire system?

Any help or guidance would be greatly appreciated!

Thanks in advance.