Support

• P

  ProGet 2025 issues
  about 19 hours ago • petter.jacobsen_7171   about 5 hours ago

  3
  0
  Votes
  3
  Posts
  15
  Views

  about 5 hours ago

  Hi @petter-jacobsen_7171, I took a look through these and I have some more answers for you: Looks like you added the package string to the license. You will need to navigate to Reporting & SCA -> Licenses -> manager license types & rules, then find that license, edit it, and remove the package string under the PUrls tab. This looks to have been fixed in ProGet 2025.1 that released last night. You can block a specific package on the Set Package Status page. There does look to be an issue in policies, but I will need to dig into this further to determine exactly what the issue is. I will be looking into this more tomorrow. I was unable to recreate this issue. It may have been fixed in 2025.1 or it may have been related to something else. Please note that if the package is in a connector, then the package will show in your feed once you delete it as a remote package. This may be related to the issue in 4, I will update on this once i have dug in further. Again, this looks to be related to an issue in policies. I addressed this in my previous comment, but just wanted to call it out for completeness sake. I should have an update tomorrow for you with more specifics around the blocking issues. Please let me know if you have any questions regarding my responses! Thanks, Rich
• R

  Rust - invalid gzip header
  17 days ago • rel_0477   about 8 hours ago

  9
  0
  Votes
  9
  Posts
  25
  Views

  about 8 hours ago

  Hi @rel_0477, I just happen to check right when this came in. Glad to hear it is working again! Was it the local cache? Cargo has a pretty aggressive cache for both good and bad packages. Thanks, Rich
• K

  Publishing NPM Packages - Assigning Tasks/Permissions
  about 14 hours ago • kc_2466   about 10 hours ago

  6
  0
  Votes
  6
  Posts
  8
  Views

  about 10 hours ago

  Hi @kc_2466 , The message "Feed-scoped Privileges are not available in ProGet Free Edition. You can still add them, but they will apply to all feeds." should be displayed when you add a privilege, but it's probably easy to miss. I'm not sure if we show it after that. As for Personal API Keys, you can create them as an admin, but non-admin users can't create their own. It's a different page. Cheers, Steve
• K

  Proget: The SSL connection could not be established for NPM Feed
  about 12 hours ago • kc_2466   about 11 hours ago

  4
  0
  Votes
  4
  Posts
  4
  Views

  about 11 hours ago

  Hi @kc_2466, I see - so they are "self-connectors", and ProGet is effectively connecting to itself. In that case, then the ProGet server is not "trusting" your in-house certificates. You'll need tot add a self-signed CA to Docker configuration. See the self-signed-ca option: https://docs.inedo.com/docs/installation/linux/docker-guide Cheers, Steve
• D

  Proget 2024.37(8) to 2025 Fails to Upgrade
  a day ago • darren.sloper_5044   about 13 hours ago

  8
  0
  Votes
  8
  Posts
  25
  Views

  about 13 hours ago

  Hi @darren-sloper_5044, Great! Glad to hear you are up and running again! Thanks, Rich
• R

  ProGet Docker Compose Upgrade Issues
  2 days ago • rel_0477   about 23 hours ago

  2
  3
  Votes
  2
  Posts
  20
  Views

  about 23 hours ago

  There was in issue with Docker container initialization due to some of the updated startup code in ProGet 2025 - it's now been resolved, and if you pull the proget:25.0.1 it should work. Hope this helps!
• C

  Scaling Proget as an Azure Container Web App, what about the SQL DB?
  7 May 2024, 06:29 • carl.westman_8110   2 days ago

  5
  0
  Votes
  5
  Posts
  29
  Views

  J 2 days ago

  Hi Carl, Would you mind sharing the startup command that you're using? Can't get it to work properly. Ty, Jeremy
• S

  Support for Winget feed
  features • 3 Jun 2021, 11:19 • sylvain.martel_3976   2 days ago

  19
  0
  Votes
  19
  Posts
  103
  Views

  M 2 days ago

  @apxltd Thanks for the update. I really appreciate you taking the time The reason I was looking to see if you supported winget yet is that I was replacing my own machine and I like to rebuild our developer image as I do so. I build our image from a base Windows image that has current Windows. I then run the “winget install” scripts to install the common tool chain. I understand on your side it doesn’t seem like a workable solution, but I love it. Winget works as if I downloaded and installed all the installs manually. Then I can just run “winget upgrade” to see what needs to be upgraded. The main benefit is that the upgrade check works even if a developer or I install something without using winget to install it. This is because “winget upgrade” uses Windows installed apps (as seen in appwiz.cpl) for its check. I hope they cleanup the backend so you could look at this product again.
• M

  Pulling dependencies from ProGet in gradle
  15 May 2025, 21:13 • misael.esperanzate_5668   2 days ago

  9
  0
  Votes
  9
  Posts
  32
  Views

  2 days ago

  Hi @misael-esperanzate_7550, What version of ProGet do you have installed? This may be an issue that we have already fixed. I remember this happening in some older versions of ProGet. Thanks, Dan
• L

  Arm/MacOS build of PGutil
  7 days ago • layfield_8963   2 days ago

  4
  0
  Votes
  4
  Posts
  10
  Views

  2 days ago

  Hi @layfield_8963, We've added osx-arm64 as another target, and we'll start deploying that along with the other binaries. We'll probably push out a new release today or tomorrow. Thanks!
• P

  Requests accepted by proget while using IIS
  4 days ago • parthu.reddy   3 days ago

  2
  0
  Votes
  2
  Posts
  7
  Views

  3 days ago

  Hi @parthu-reddy , First, please note that IIS is no longer recommended for ProGet 2024 and it is not supported in ProGet 2025: https://docs.inedo.com/docs/installation/windows/web#iis As for request limits, there are none. And it's not really a question that we can answer - a request can be anything from serving a cached image to doing a query with "chained connectors" that has to do a lot of network activity. It really depends on the types of feeds, configuration, etc. But a good "rule of thumb" is that 50-100 simultaneous connections will start to strain a server, and 10x that very likely be difficult to use. Hope that helps, Steve
• L

  'pgutil upack install' fails when feed has non semver versions
  8 days ago • lukas.christel_6718   3 days ago

  5
  0
  Votes
  5
  Posts
  14
  Views

  L 3 days ago

  The issue occurs when I try to install a package that complies with semver. The presence of a package with a non-semver version is enough to fail the installation of other packages with the same name (maybe all other packages with the same name). Installing a package from the same feed with a different name still succeeds. I manually created demo packages to reproduce the issue. I first uploaded the bad version to the proget feed (don't know if that matters) through the manual file upload in the web interface, then the good version. The issue occurs when I try to install the good version. The issue happens when pgutil tries to parse the available versions on the server (see call stack in first post) AFTER it already successfully parsed the requested version from the command. I couldn't find a general file upload. Here are the upack.json used to create the demo packages { "name" : "DEMO-5418", "version" : "1.0.0-bad_version", "createdDate" : "2025-06-16T17:17:15Z" } { "name" : "DEMO-5418", "version" : "1.0.0-good-version", "createdDate" : "2025-06-16T17:18:10Z" }
• M

  [ProGet] Composer feed: package metadata is missing vendor binaries
  6 days ago • matthias.reitinger_3646   6 days ago

  3
  0
  Votes
  3
  Posts
  9
  Views

  M 6 days ago

  Hi Rich, I really appreciate you looking into it and confirming the issue so quickly. It's great to know a ticket is already in the works. I'll keep an eye out for the fix in ProGet 2024.39. Thanks again for your help! – Matthias
• P

  The process cannot access the file
  7 days ago • parthu.reddy   7 days ago

  2
  0
  Votes
  2
  Posts
  6
  Views

  7 days ago

  Hi @parthu-reddy , Nothing to worry about - there are a few ways this can happen, and unless it's happening a lot and/or causing problems with your end-users / pipelines / etc., you can ignore the message. -- Dean
• M

  Feed Group and Feed
  11 days ago • michal.roszak_0767   7 days ago

  2
  0
  Votes
  2
  Posts
  11
  Views

  7 days ago

  Hi @michal-roszak_0767 , I'm afraid Feed Groups are not currently supported in the Feed Management API or pgutil feeds commands. We are considering rewriting/refactoring the API later this year, so I've added this to the notes to consider for that. Thanks, Steve
• D

  Incomplete proget debian connector local index file for ubuntu noble-backports dist
  24 days ago • dimas   11 days ago

  6
  0
  Votes
  6
  Posts
  15
  Views

  11 days ago

  @dimas thanks for that! We're currently studying/monitoring the performance for public mirroring, and one "concerning" thing I recently saw was a sqllite3 index file explode in file size. We don't know how that happened, but suspect it might have to do with some "aggressive" testing / request cancellation. Let us know if you spot anything: https://forums.inedo.com/topic/5410/debian-feed-mirror-performance
• S

  [ProGet] Feature Request: Visual Studio Code - private Extension Gallery
  5 Jan 2024, 13:18 • sebastian.lieschke_5424   11 days ago

  6
  0
  Votes
  6
  Posts
  19
  Views

  11 days ago

  Hey @dimas , Ah, that makes sense. Looking at the manifest files, they have the same Identity@Id (which is what ProGet uses for the Package Name) but a different Identity@TargetPlatform (which must be new-ish): <Identity Language="en-US" Id="python" Version="2025.2.0" Publisher="ms-python" TargetPlatform="win32-x64"/> <Identity Language="en-US" Id="python" Version="2025.2.0" Publisher="ms-python" TargetPlatform="linux-x64"/> We could probably figure something out in ProGet, but it's not trivial when it comes time to changing how we identify Package Names. Can you try editing the manfiest file inside the vsix archive, and seeing if that works for your use case? So basically: <Identity Language="en-US" Id="python-win32-x64" Version="2025.2.0" Publisher="ms-python" TargetPlatform="win32-x64"/> <Identity Language="en-US" Id="python-linux-x64" Version="2025.2.0" Publisher="ms-python" TargetPlatform="linux-x64"/> Not quite sure if that would work, but figure it's worth a try. Thanks, Alex
• D

  Debian feed mirror Performance
  21 days ago • dan.brown_0128   15 days ago

  3
  0
  Votes
  3
  Posts
  11
  Views

  D 15 days ago

  To share with the community some things learned from a private support ticket -- There's currently a defect in the logic where if no packages were downloaded/uploaded to a debian type feed, the in-memory cache is never started. This leads to very long runtimes when running apt update since the response times for the /Release and /InRelease endpoints (from our experience) are at best 1 minute, at worst 10 minutes. The workaround support gave was to manually download a package via http before attempting to use apt. From our experience, this doesn't persist overnight, so it would basically need done daily and truly is counterintuitive to having a package manager like apt.
• D

  Error since migrating to PostgreSQL backend.
  16 days ago • darren.sloper_5044   15 days ago

  4
  0
  Votes
  4
  Posts
  14
  Views

  D 15 days ago

  Hi @dean-houston Thank you for the ultra-quick response. Disabling that feature did indeed provide a workaround solution and currently testing is back on track. Thanks again Darren
• M

  0 byte download when using pgutil assets/packages download in github workflow
  22 Apr 2025, 17:08 • mmaharjan_0067   15 days ago

  4
  0
  Votes
  4
  Posts
  26
  Views

  15 days ago

  Hi @layfield_8963, Looks like this was just a simple bug preventing output from being written when stdout has been redirected. It's now fixed in pgutil 2.1.1. Thanks for the update! -Greg