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 have a couple of questions regarding the self-connector configuration in ProGet.

1. When setting up a self-connector, should the connector URL point to the instance's external URL (e.g. https://proget.example.com) or is it acceptable/preferable to use localhost e.g. http://localhost since it connects back to the same instance?
2. Regarding how feeds with self-connectors handle the package storage - does ProGet store multiple copies of the same package in different feeds with self-connector, or does it simply reference and serve the package from original feed?

I am trying to confirm the best practice for configuration and understand whether there's any unnecessary duplication or storage overhead when using self-connectors.

Thanks in advance for your clarification.

Hi ProGet team,

I’ve encountered an issue when uploading Maven packages to ProGet that use non-standard version strings starting with a character.

Example:

• Package name: package-alpha-0.1.pom
• Version: alpha-0.1

When I upload this package and then try to access the .pom file directly from the feed, instead of downloading the file as usual, the browser is redirected to a page ending with / (e.g., .../package-alpha-0.1/), rather than returning the file contents.

However, this behavior does not occur when the non-standard version starts with a number.
For example:

• 0.1_a-l-p-h-a works correctly — the .pom file is downloaded normally.

Steps to Reproduce:

1. Upload a Maven package with a non-standard version starting with a letter (e.g. alpha-0.1).
2. Attempt to access the .pom file directly from the feed URL.
3. Observe that the request is redirected to a URL ending in / instead of downloading the file.

Expected Behavior:
Accessing the .pom file should return the file contents directly, similar to when using a numeric-starting version.

Actual Behavior:
Accessing the .pom file with a version starting with a character causes a redirect, preventing the file from being downloaded.

Questions:

• Is this the expected behavior in ProGet for non-standard Maven versions?
• If not, how can I configure ProGet or the Maven feed so that files with such versions are handled correctly (i.e., downloaded instead of redirected)?

Environment:

• ProGet version: 25.0.12; container
• Feed type: Maven
• Client: Browser / curl

Thanks for your help!

Hi @atripp,

Just to confirm — with the naming, the feed will first retrieve content from 10-nuget.org, and only then from 20-abc.net, correct?

Thanks.

Hi ProGet team,

We use multiple connectors to proxy external sources and would like certain packages to be retrieved from preferred sources first.

Does ProGet support ordering or precedence for connectors? If not, are there any recommended workarounds?

Thanks!

Hi ProGet Support Team,

I’m exploring migration options for different package types in ProGet. It’s great that ProGet provides built-in support to import PyPi, NPM, and Maven packages from external sources such as Nexus.

However, I noticed that Container Images and Assets package types do not currently have similar migration support.

I’d like to ask:

• Are there any plans to provide built-in migration support for these package types in the future?
• Alternatively, does ProGet provide any scripts or recommended methods for migrating Container Images or Assets packages?

Any guidance or suggestions would be greatly appreciated.

Thanks in advance!

Hi @stevedennis, thanks for the reply. According to the documentation, the URL needed to create self-connector can be found on the "Feed Overview" page - however, I'm not sure how to navigate to that page from the UI, and I am also unable to find anything similar to the URL mentioned. Would you be able to point me in the right direction? Thanks.

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?

In Nexus, multiple repositories of the same type can be grouped virtually and exposed through a single endpoint, allowing clients to resolve packages across multiple sources seamlessly.

Does ProGet support grouping multiple feeds into a single endpoint? If not, is there a recommended workaround to achieve similar behavior?

From the UI it seems like the Maven feed only support standard file types such as .jar, .war, and .ear. However for our use case, we need to publish and resolve artifacts that use custom file extensions, such as .zip, .module, etc., while still maintaining the Maven2 layout.

Is there a way to configure the Maven feed to accept and serve artifacts with non-standard extensions?

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