Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

  • 500 Error after upgrading to 6.0.8

    2
    0 Votes
    2 Posts
    15 Views
    atrippA
    Hi @albert-pender_6390 , This is an internal Windows Error, and happens when another process (usually a UI window) has an open session to hive within the Windows Registry. It's a long-standing bug/issue with COM+ services (which Active Directory uses), and is not really ProGet specific. It's a side-effect of the ProGet upgrade process, which often stops/starts Windows Services and IIS Application pools. Ultimately restarting will fix it (as you've notcied), but changing the "Load User Profile" to "true" on the application pool is also known to fix it as well. Best, Alana
  • BuildMaster Artifacts Overview Filtering

    4
    1
    0 Votes
    4 Posts
    16 Views
    atrippA
    @paul_6112 well, as it turns out... this was actually trivial to fix It will make it in 7.0.19, scheduled for Feb-25th
  • Error: HttpException Server Too Busy

    5
    0 Votes
    5 Posts
    25 Views
    atrippA
    Hi @galaxyunfold , The "Timeout expired" errors are indeed a result of database or network connectivity issues. It's possible to create connector loops (A ->B -> C -> A) that will yield this behavior as well. The "server too busy" is an internal IIS error, and it can be much more complicated. It's rarely related to load, and is more related to performing an operation during an application pool recycle. Frequently crashing application pools will see this error frequently. There are a lot of factors that determine load, and how you configure ProGet (especially with connectors and metadata caching) makes a big difference. But in general, it starts to make sense at around 50 engineers. At 250+ engineers, it makes sense not to go load-balanced / high-availability. Here is some more information: https://blog.inedo.com/proget-free-to-proget-enterprise Cheers, Alana
  • Proget feed Nuget Package unavailable

    9
    3
    1 Votes
    9 Posts
    40 Views
    N
    Hey @stevedennis , That's my bad I blurred too much. The "/feeds/" part was there too. I poked our IT team to see if there could be any weird settings on our IIS server or the network itself. Sometimes our Proget page gets super slow too and we even get 502 errors so there might be something wrong in our setup. I'll keep you updated if I find anything. Thanks again
  • Null reference exception on nuget package from connector

    11
    0 Votes
    11 Posts
    32 Views
    Dan_WoolfD
    Hi @claudio_9251, I'm not too surprised by this. NuGet has deprecated many of it's ODATA( v2) endpoints which has caused some issue within ProGet, we have documented this in our NuGet v2 troubleshooting guide. It is very possible that Telerik (Progress) has not made these changes on their end which may be causing this. This is especially true when it comes to connectors because ProGet will pass through a lot of the V2 queries the client makes to the remote endpoint. Either way, the NuGet v3 API is the proper API to use going forward and we highly suggest using that. Thanks, Dan
  • How to provide ProGet feed name in Azure DevOps Docker-Compose task?

    2
    0 Votes
    2 Posts
    9 Views
    atrippA
    Hi @dustin-davis_2758 , I'm not really sure - I'm not familiar enough with ADO Docker Compose to help :/ The error is coming because the container repository (image) name is incorrect; it should be like proget.initech.com/feedName/initech/repositoryName Generally you put this in your docker-compose.yml file, like this: https://docs.inedo.com/docs/docker-compose-installation-guide#example-docker-compose-configuration-file So that would be the first place I would look. If you have the proper image name in there, tehn I guess, ADO might be doing something different? Let us know what you find! Cheers, Alana
  • Running Proget on Preprd environment

    2
    0 Votes
    2 Posts
    5 Views
    Dan_WoolfD
    Hi @sbindra_9387, You should create a new free license for your preprod environment. Creating that new license will not affect your production activation. Just to verify, your preprod environment is pointing to a different database and different file storage than your production instance, is that correct? I know you are running an older version of ProGet, but our guide on how to migrate a server should still work for ProGet 5.1. That guide will show you what you need to do to migrate your production instance to a test server. Hope this helps! Thanks, Dan
  • 0 Votes
    5 Posts
    21 Views
    atrippA
    @araxnid_6067 thanks, gload it worked! I'll work to update the documentation about this topic :)
  • kubernetes scanner not showing results

    28
    0 Votes
    28 Posts
    70 Views
    C
    @atripp Wunderfull... Glad I could help.. Looking forward to test when it arrives :)
  • Upgrading from 5 to 6 causes API Key to stop working

    6
    0 Votes
    6 Posts
    30 Views
    NanciCaloN
    @Stephen-Schaff thanks so much Stephen, that's great! It's not so hard for us to add this api key back, but your code works just the same mostly i think! let us know... Anyway I've updated the documentation :)
  • 0 Votes
    2 Posts
    14 Views
    NanciCaloN
    Hello; Does your server have Internet access? That is an ancient version of the Inedo Hub... I would uninstall the Inedo Hub, and then download it again. Hopefully the error will be resolved then. Cheers, Nanci
  • API to apply an Alternate Tag to Docker Container Image

    4
    0 Votes
    4 Posts
    21 Views
    S
    Version 6 of ProGet removes the ability to make calls to the docker API via a ProGet API Key. As such the code posted above no longer works. I updated it to work using the Docker Token based Authentication system. I am posting it here in case someone comes along this post and wanted to use this code: function RepackageContainerImage() { param ( [string] $packageName = $(throw "-packageName is required. This is the namespace/image-name"), [string] $fromFeed = $(throw "-fromFeed is required"), [string] $toFeed = $(throw "-toFeed is required"), [string] $fromVersion = $(throw "-fromVersion is required. This is the current tag on the image in the fromFeed."), [string] $toVersion = $(throw "-toVersion is required. This is the tag to be applied after the image is promoted."), [string] $comments = "Promoted by automation", [string] $apiKey = $(throw "-apiKey is required"), [string] $progetBaseUrl = $(throw "-progetBaseUrl is required") ) # Promote the Container Image $postBody = @{ packageName="$packageName"; groupName=""; version="$fromVersion"; fromFeed="$fromFeed"; toFeed="$toFeed"; comments="$comments" } $promoteResponse = Invoke-WebRequest -Uri "$progetBaseUrl/api/promotions/promote" -Method POST -Body $postBody -Headers @{"X-ApiKey"="$apiKey"} # Retag the container image by downloading the manifest and then re-uploading it as the new version $pullToken = GetDockerToken -feed $toFeed -packageName $packageName -actionToAuthorize "pull" -apiKey $apiKey -progetBaseUrl $progetBaseUrl $manifest = Invoke-WebRequest -Uri "$progetBaseUrl/v2/$fromFeed/$packageName/manifests/$fromVersion" -Method GET -Headers @{Authorization=("Bearer {0}" -f $pullToken)} $pushToken = GetDockerToken -feed $toFeed -packageName $packageName -actionToAuthorize "push" -apiKey $apiKey -progetBaseUrl $progetBaseUrl Invoke-WebRequest -Uri "$progetBaseUrl/v2/$toFeed/$packageName/manifests/$toVersion" -Method PUT -Body $manifest.ToString() -Headers @{Authorization=("Bearer {0}" -f $pushToken)} } function GetDockerToken() { param ( [string] $packageName = $(throw "-packageName is required. This is the namespace and image name. For example: library/my-container-image"), [string] $feed = $(throw "-feed is required"), [string] $actionToAuthorize = $(throw "-action is required. This is the docker action to be authorized (pull, push, delete, etc)"), [string] $apiKey = $(throw "-apiKey is required"), [string] $progetBaseUrl = $(throw "-progetBaseUrl is required"), [string] $service ) if ($service -eq "") { $service = $progetBaseUrl.SubString(8,$progetBaseUrl.Length-8) } $base64AuthInfo = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(("{0}:{1}" -f "api","$apiKey"))) $response = Invoke-WebRequest -Uri "$progetBaseUrl/v2/_auth?service=$service&scope=repository`:$feed/$packageName`:$actionToAuthorize" -Headers @{Authorization=("Basic {0}" -f $base64AuthInfo)} if ($response.StatusDescription -eq "OK") { $token = ($response.Content | ConvertFrom-Json).token $token } }
  • 0 Votes
    4 Posts
    14 Views
    atrippA
    Thanks @mcascone , I also added this to our "Promotion / Repackaging Visibility & Permissions Rethinking" task - sounds like something we can consider :)
  • 0 Votes
    2 Posts
    7 Views
    atrippA
    Hi @mcascone , I admit this can be confusing and is unintuitive because these were added separately over time, and the weren't originally designed for how they're used today. We need to rethink/redesign this based on the use cases. I'm going to add this thread under the "promotion/repackaging workflows" topic for our next major version of ProGet. Once we know what we want to do, we can may be able to implement some changes as a preview feature in v6. FYI, this is exactly how the big API Key changes and feed/package usage instructions came about! https://forums.inedo.com/topic/3204/proget-feature-request-api-key-admin-per-user So stay tuned :)
  • 0 Votes
    7 Posts
    21 Views
    MaxCasconeM
    Hi, just wanted to say that i happened to look at the new releases available for v5, and saw that this is fixed in the latest release, 5.3.44. Awesome! Thanks!
  • Release of the ProGet 6.0.7

    6.0.7 proget releases
    3
    0 Votes
    3 Posts
    13 Views
    L
    Hello Dan, Exactly what I needed. Thank you for the prompt reply! Mikhail R.
  • Npm packages not visible when running onder IIS

    14
    0 Votes
    14 Posts
    80 Views
    L
    I can confirm that its working for us now. Thanks!
  • Marking packages as deprecated

    4
    0 Votes
    4 Posts
    28 Views
    stevedennisS
    Hi @benjamin-soddy_9591, No problem "resurrecting" topics! We definitely want to hear from users about feedback/feature requests. We still haven't had anyone else ask for deprecation since this request, but I wonder if there's a better solution to solving your challenges than this feature. It sounds like you want to increase governance of your NuGet Packages, potentially with some sort of compliance in mind. The dotnet list package --vulnerable is probably not what you want for your organization; NuGet's Built-in Vulnerability Scanning is really limited, in part because it only reports on a fraction of known package vulnerabilities (164 as of today). It also won't block packages that you deem problematic, unlike ProGet's feature. The same is true with dotnet list package --outdated -- it's probably not what you want, because it relies on developers to have to know (1) to run the command, and (2) know what to do if there's an outdated dependency. There are better ways to manage third-party packages (see How to Create a Package Approval Workflow for NuGet), and you'd better served knowing who's consuming outdated packages (see Use Package Consumers to Track Dependencies Just some thoughts; like I said, we haven't had any demand for this feature, but these are proven solutions for improving governance of packages as organizations grow/expand their NuGet usage like you are. Cheers, Steve
  • Cannot get docker connector to azurecr.io to work

    10
    0 Votes
    10 Posts
    38 Views
    Dan_WoolfD
    Hi @brett-polivka, No problem! We are expecting this fix to be released on Friday. We will let you know if anything changes! Thanks, Dan
  • Issues with changing package count view and other search issues

    3
    1
    0 Votes
    3 Posts
    11 Views
    C
    Thank you Nanci! The workaround fixed the issue and we will begin the upgrade process. Thanks!
Inedo Website HomeSupport HomeCode of ConductForums GuideDocumentation