Support

• K

  Docker Migration from Nexus – Feature Not Working
  • koksime.yap_5909  

  9
  0
  Votes
  9
  Posts
  35
  Views

  K

  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.
• 

  Create API Key for all feeds
  • steviecoaster  

  2
  0
  Votes
  2
  Posts
  5
  Views

  

  Hi @steviecoaster , Nice suggestion; I made a small change and you can now do pgutil apikeys create feed --feed=* to create such a key. Thanks, Alana
• 

  Documentation discrepancy
  • steviecoaster  

  4
  0
  Votes
  4
  Posts
  11
  Views

  

  Hi @steviecoaster , FYI - I just a note to the license restriction page; it looks like we don't mention the restrictions on other APIs (delete, scan, etc), but it's something we'll consider next round of docs refactoring. I know we do call it out on the main documentation pages though.
• R

  Using pgutil, unable to set debian component when uploading a package
  • rhowell_8827  

  1
  0
  Votes
  1
  Posts
  3
  Views

  No one has replied

• S

  [ProGet] Feature Request: Visual Studio Code - private Extension Gallery
  • sebastian.lieschke_5424  

  10
  0
  Votes
  10
  Posts
  35
  Views

  

  Hi @fbiryukov_8162, I did a quick read of the content, and based on this statement ... "Private Marketplace is available to GitHub Enterprise customers. VS Code users must sign in with a GitHub Enterprise or Copilot Business or Enterprise account to access." sounds to me like a closed ecosystem And these technical instructions ... https://github.com/microsoft/vsmarketplace/blob/main/privatemarketplace/latest/README.md#5-connect-vs-code-to-the-private-marketplace ... this is a locked-down / closed ecosystem. There's no published API/specs and no still no support in VSCode for private galleries. They're just "hacking" internal settings to get VSCode to use a different service URL, which they also control. Obviously this is not something we could/would want to reverse engineer and then support. If the VSCode team adds support for private repository/galleries (and a public/documented API), and there's some degree of stability to that, we'll consider it. But until then, not much we can do. Best, Alex
• U

  v2025 npm package not saved on server
  • udi.moshe_0021  

  5
  0
  Votes
  5
  Posts
  9
  Views

  U

  @atripp Hi, thank you very much.
• J

  KeyNotFoundException The given key was not present in the dictionary with specific npm packages
  • jonathan.erlich_0694  

  2
  0
  Votes
  2
  Posts
  9
  Views

  

  Hi @jonathan-erlich_0694 , Based on the stack trace, there's something wrong with the data being returned via the API from the remote connector. Specifically, one/more of the version objects being returned is missing a name or version property, Based on the URL, the invalid data is at the {repository-root-url}/browser-sync. Here's what it's supposed to look like, based on the public repository at least: https://registry.npmjs.org/browser-sync Thanks, Alana
• P

  Connector for accessing Jfrog pypi feed
  • pmsensi  

  9
  0
  Votes
  9
  Posts
  25
  Views

  P

  @atripp now is working :) Thank you!
• P

  Timeout while fetching Packages
  • parthu.reddy  

  2
  0
  Votes
  2
  Posts
  10
  Views

  

  Hi @parthu-reddy , This can particular occur when there are some issues with the database, such as outdated statistics or highly-fragmented indexes. This script should help fix this: https://proget.inedo.com/endpoints/Public/content/DefragmentIndexesWithRowCount.sql It coudl be something else, but the query that page uses seems to be mostly effected by those. Thanks, Alana
• P

  Timeout while searching in powershell gallary for packages that are not cached
  • parthu.reddy  

  2
  0
  Votes
  2
  Posts
  8
  Views

  

  Hi @parthu-reddy , This error means that PowerShellGallery.com is taking too long to respond to that query. You can try increasing the connector timeout; it's 10 seconds by default. Maybe try 20 or 30 seconds? Just a guess. Unfortunately the PowerShellGallery seems to be in a state of abandonment these days and it performs really poorly. It's pretty buggy too. I would consider using a multi-feed, package-approval process to pull packages so you don't have to rely on the gallery's API. Cheers, Alana
• J

  ProGet 2025.14: Vulnerability Database Updater causes duplicates in PackageNameIds
  • jw  

  7
  0
  Votes
  7
  Posts
  35
  Views

  J

  However, as you noticed, the name is overwritten when a package is added to a feed. So, if jquery is the package name stored in the database, that record will be updated to jQuery upon upload of a package. This was a pretty good hint. So far I've only been hitting the "Download Package" button, which puts the package in the cache, but apparently does not update the name in PackageNameIds. "Pull to ProGet" however seems to update that table and I can fix the old names in the database. Thank you!
• J

  ProGet 2025.10: License Update API Issues
  • jw  

  13
  0
  Votes
  13
  Posts
  78
  Views

  J

  Tested in 2025.15, working as expected now - Thank you!
• S

  Rocky Linux rpm feed not working
  • Sigve.opedal_6476  

  6
  0
  Votes
  6
  Posts
  31
  Views

  S

  Upgraded to version 25.0.15, and it's working. Thanks.
• D

  PHP Composer feed connect to vcs type repository or how to upload
  • dubrsl_1715  

  9
  0
  Votes
  9
  Posts
  30
  Views

  

  Hi @dubrsl_1715 I was sure that you must be interested in creating a product that would solve real tasks. Not really :) As a products company, we solve problems that a sufficient number of users would be willing to pay for and that aligns with our overall strategic vision. We also do User-Driven Development, which means we prioritize helping our existing users/customers solve problems instead of adapting the product for nonusers/evaluators like you guys. We don't consider packagist a competitor nor are we currently marketing users to switich; our solution is similar but not an analog. It requires a change to your workflow. The PHP/Composer market is already hyper-niche and I'm not convinced there's enough demand to develop a "versionless" package format (i.e. where a version number cannot be discovered in the manifest file or the package file name) format just for this particular use case (i.e. alternate workflow / simpler migration from packagist). None of the other feed types have this requirement, and it'd be nontrivial to modify our model to support this unique requirement. It would have downstream impacts to features like replication, disk-importing, reindexing, etc. Thanks, Alex
• F

  Known licenses are shown as unknown
  • frank.b  

  8
  0
  Votes
  8
  Posts
  32
  Views

  

  Hi @frank-benson_4606 , Thanks for clarifying, that makes sense. I'm afraid that ProGet does not "crawl" the parent artifacts for metadata; we had considered it, but it's rather challenging to do from an engineering standpoint, difficult to present crawler errors, and fairly uncommon. Thanks, Steve
• S

  ProGet encryption key decryption failure
  • sneh.patel_0294  

  7
  0
  Votes
  7
  Posts
  9
  Views

  S

  Thanks! I think the restart of IIS App Pool might have helped. I don't see that failure anymore.
• F

  How to create a license attribution report?
  • frank.b  

  3
  0
  Votes
  3
  Posts
  15
  Views

  F

  Hi Steve, I will look at an audit report to see if this can be used. Thanks, Frank
• K

  'Usage & Statistics' info missing
  • k.lis_1147  

  6
  0
  Votes
  6
  Posts
  46
  Views

  

  Hi @k-lis_1147, Sorry on the slow reply; we did not get a chance to investigate in last release, but it was on the list this week. That being said, it was also an easy fix (didn't anticipate it to be a copy/paste fix)-- and we'll get it via PG-3160 in this week's mainteancne release. Thanks, Steve
• J

  Packages with Noncanonical Names errors on internalized packages
  feed-health noncanonical package-name • • jfullmer_7346  

  19
  0
  Votes
  19
  Posts
  72
  Views

  J

  Things appear to be normal now, feed integrity checks didn't throw the errors after doing the thorough delete and then re-uploading those packages. Granted the powershell module is no longer getting updates to have parity with the version of winscp and that probably helps too.
• 

  Debian feed broken after upgrade to 2025.14
  • felfert  

  8
  0
  Votes
  8
  Posts
  36
  Views

  

  @gdivis Too bad I already changed all my keys and updated a lot of Test-VM-Instances in an internal OpenStack. Would have been be MUCH less work. Oh well. Thanks anyway for the info -Fritz